wdi-method 0.6.7 → 0.6.15

package/README.md

@@ -29,11 +29,10 @@ page it is on.
 
 ## Install
 
-Three steps, in this order. The first is required before step 3 will run; the second can wait until
-**Both are required, and the installer refuses without either.** BMad has always been checked; the ticket
-engines are checked too, because every repo that learned they were missing learned it inside `wdi-build`
-with a spec already open. `--skip-engines-check` is the escape for the two cases that earn it: CI, and a
-repo that will never reach G5.
+Three steps, in this order, and **step 3 refuses until steps 1 and 2 are done** — through the TUI and
+through `--yes` alike. BMad has always been checked; the engines are checked too, because every repo that
+learned they were missing learned it inside `wdi-build` with a spec already open. `--skip-engines-check`
+is the escape for the two cases that earn it: CI, and a repo that will never reach G5.
 
 **1. BMad Method** — in the product repo, picking the same agents you will give this installer:
 
@@ -42,16 +41,26 @@ cd /path/to/your/product-repo
 npx bmad-method install
 ```
 
-**2. mattpocock/skills** — one of the two paths, not both (both leaves every skill twice):
+**2. mattpocock/skills** — **into this repo**, on every agent:
 
 ```bash
-# Claude Code — a managed bundle that updates when its author ships
-claude plugins install mattpocock-skills      # or, inside a session:  /plugin install mattpocock-skills
-
-# Codex, Cursor, OpenCode, other agents — copies the skills into this repo; keep setup-matt-pocock-skills selected
 npx skills@latest add mattpocock/skills
 ```
 
+Take all six the method drives: `to-spec`, `to-tickets`, `implement`, `tdd`, `code-review`, and
+`domain-modeling`. Either install mode works — "copy" or "symlink".
+
+**The Claude Code plugin is not an alternative here, and the reason is mechanical.** `to-spec`,
+`to-tickets` and `implement` ship with `disable-model-invocation: true`, so no skill can invoke them;
+nothing outside the file lifts that flag, and a plugin's files are not this repo's to edit. WDI Method
+strips it from the copies the repo owns — which is what lets `wdi-build` invoke an engine and
+`wdi-autopilot` run an iteration with nobody watching — and re-applies that on every update, because
+`npx skills update` restores the author's file. The installer refuses without the six, and
+`--skip-engines-check` is the escape for CI and for a repo that will never reach G5.
+
+If you also have the plugin installed for your user, the repo's copies are what run; removing the
+plugin keeps `/to-spec` unambiguous.
+
 **You do not need to run `/setup-matt-pocock-skills` to get started.** Step 3 seeds `docs/agents/` with
 the two answers WDI Method actually has a requirement on, so the engines are aligned from the first
 install. Run the setup skill only to *change* something — to point at GitHub or Jira instead of local
@@ -450,6 +459,24 @@ English, whatever the settings say — it travels to every repo through this pac
 
 It prints the version it replaced, what it wrote, what it kept, and what to do next.
 
+### Moving a repo from 0.6.7 or earlier to 0.6.8
+
+Four things change for a repo already running the method. The first is the only one that can stop an
+update, and all four are mechanical.
+
+| What changed | What it means for your repo |
+|---|---|
+| **The engines must be in the repo** | `install` and `update` refuse until `to-spec`, `to-tickets`, `implement`, `tdd`, `code-review` and `domain-modeling` are here — `npx skills@latest add mattpocock/skills`. The Claude Code plugin no longer counts: three of the six ship locked against skill invocation, nothing outside the file unlocks them, and a plugin's files are not yours to edit. `--skip-engines-check` still installs without them |
+| **The engines are invoked, not handed to you** | `wdi-build` calls `to-spec`, `to-tickets`, `implement`, `tdd` and `code-review` itself, so `wdi-autopilot` can finish a spec with nobody watching. Every `update` re-unlocks the repo's copies, because `npx skills update` puts the author's lock back — and `engines-invocable` in `validate.py` goes red when it has |
+| **Thirteen BMad skills are retired at G5, and now enforced** | `bmad-spec`, `bmad-build`, `bmad-build-auto`, `bmad-code-review`, `bmad-retrospective`, `bmad-agent-dev`, `bmad-create-epics-and-stories`, `bmad-create-story`, `bmad-dev-story`, `bmad-dev-auto`, `bmad-quick-dev`, `bmad-sprint-planning`, `bmad-sprint-status`. Each is locked out of model invocation and denied in `.claude/settings.json`; typing the slash command yourself still works. `bmad-skill-register.md` carries the list and the criterion — retired only where this method has a named replacement, which is why `bmad-qa-generate-e2e-tests` and `bmad-checkpoint-preview` are not on it |
+| **A spec has one predefined home** | `.scratch/<spec-id>-<slug>/`, with `SPEC.md` and `issues/<NN>-<slug>.md` inside it. Left free, that folder name gets written a different way in every repo and traces back to nothing. A row in `specs.yaml` is now what makes an effort a spec rather than ad hoc work — the path no longer says |
+
+Run the `wdi-upgrade` skill after updating: it names what is still in the old shape, including a
+`docs/agents/issue-tracker.md` that still carries `/setup-matt-pocock-skills`' own answer, and the spec
+folders that need moving. `npx wdi-method engines` reports the engine state on its own, and
+`npx wdi-method engines --fix` repairs what can be repaired without touching anything you wrote — the
+previous config is kept as `.bak`.
+
 ---
 
 ## Changing the method