wdi-method 0.4.6 → 0.5.0

package/kit/assets/bmad-custom/bmad-product-brief.toml

@@ -1,34 +1,34 @@
-# Class A — writes straight into the corpus.
-# Singleton: one product, one brief, across releases. A second product MUST get its own repo.
-#
-# Called through `wdi-problem`, never directly. The override here decides where the artifact
-# lands; the wrapper skill checks its content.
-
-[workflow]
-
-brief_template     = "{project-root}/.constitution/document/templates/brief.md"
-
-# run_folder_pattern MUST be constant — no {project_name}, no {date}.
-# That is what forces the singleton: every run lands in the same folder, so a second run is
-# detected as a resume/update, not a sibling folder.
-# The result is .what/_product-brief/brief.md and .what/_product-brief/addendum.md; both
-# filenames are hardcoded in SKILL.md and cannot be configured.
-brief_output_path  = "{project-root}/.what"
-run_folder_pattern = "_product-brief"
-
-# Append-only against the default `skill:bmad-review lenses=structure,prose`.
-doc_standards = ["file:{project-root}/.constitution/document/brief-guide.md"]
-
-persistent_facts = [
-  "Every memlog.py call — init, append, set, and the read on resume or intent Update — MUST use --path {project-root}/.control/memlog/brief.md. --workspace MUST NOT be used; it would place a .memlog.md inside .what/, and no memlog is allowed to live in the corpus.",
-
-  "The brief template opens with permission to drop a section that does not fit. That permission MUST NOT apply to the eight mandatory sections: The Problem, Who This Serves, Goals, Success Criteria, Scope In, Scope Out, Constraints, Assumptions — plus Prerequisites. Other template sections MAY be dropped.",
-
-  "Goals MUST be numbered BG-1, BG-2, and so on. They MUST NOT be numbered G1, G2 — G1 through G5 are the names of this method's five gates, and BG is the first link in the BG -> CAP -> FR/NFR -> UC -> Story -> Test traceability chain.",
-
-  "The Who This Serves table MUST carry exactly one row marked primary, and MUST cover every stakeholder including one who never opens the product.",
-
-  "The brief MUST NOT carry a Product Component list, and MUST NOT fill product_components or logical_components. The slicing is born at the TAIL of G2 through wdi-init intent `component`, read from the brief plus every PRD.",
-
-  "Output from research, brainstorming, forge, and PRFAQ MUST stay in _bmad-output/. It MUST NOT be folded into the brief and MUST NOT be promoted into .what/; a `DEC-` or PRD references it by path. That run folder MUST NOT be deleted — intent Update reads it back as original inputs.",
-]
+# Class A — writes straight into the corpus.
+# Singleton: one product, one brief, across releases. A second product MUST get its own repo.
+#
+# Called through `wdi-problem`, never directly. The override here decides where the artifact
+# lands; the wrapper skill checks its content.
+
+[workflow]
+
+brief_template     = "{project-root}/.constitution/method/document/templates/brief.md"
+
+# run_folder_pattern MUST be constant — no {project_name}, no {date}.
+# That is what forces the singleton: every run lands in the same folder, so a second run is
+# detected as a resume/update, not a sibling folder.
+# The result is .what/_product-brief/brief.md and .what/_product-brief/addendum.md; both
+# filenames are hardcoded in SKILL.md and cannot be configured.
+brief_output_path  = "{project-root}/.what"
+run_folder_pattern = "_product-brief"
+
+# Append-only against the default `skill:bmad-review lenses=structure,prose`.
+doc_standards = ["file:{project-root}/.constitution/method/document/brief-guide.md"]
+
+persistent_facts = [
+  "Every memlog.py call — init, append, set, and the read on resume or intent Update — MUST use --path {project-root}/.control/memlog/brief.md. --workspace MUST NOT be used; it would place a .memlog.md inside .what/, and no memlog is allowed to live in the corpus.",
+
+  "The brief template opens with permission to drop a section that does not fit. That permission MUST NOT apply to the eight mandatory sections: The Problem, Who This Serves, Goals, Success Criteria, Scope In, Scope Out, Constraints, Assumptions — plus Prerequisites. Other template sections MAY be dropped.",
+
+  "Goals MUST be numbered BG-1, BG-2, and so on. They MUST NOT be numbered G1, G2 — G1 through G5 are the names of this method's five gates, and BG is the first link in the BG -> CAP -> FR/NFR -> UC -> Story -> Test traceability chain.",
+
+  "The Who This Serves table MUST carry exactly one row marked primary, and MUST cover every stakeholder including one who never opens the product.",
+
+  "The brief MUST NOT carry a Product Component list, and MUST NOT fill product_components or logical_components. The slicing is born at the TAIL of G2 through wdi-init intent `component`, read from the brief plus every PRD.",
+
+  "Output from research, brainstorming, forge, and PRFAQ MUST stay in _bmad-output/. It MUST NOT be folded into the brief and MUST NOT be promoted into .what/; a `DEC-` or PRD references it by path. That run folder MUST NOT be deleted — intent Update reads it back as original inputs.",
+]

package/kit/assets/bmad-custom/bmad-retrospective.toml

@@ -1,9 +1,9 @@
-# Runs in stories mode: reads SPEC.md + stories.yaml + stories/<id>-*.md, not
-# sprint-status.yaml. Its output is RETROSPECTIVE.md inside the spec folder — which is ephemeral.
-
-[workflow]
-
-persistent_facts = [
-  "This repo runs in stories mode. RETROSPECTIVE.md MUST be archived as RTR-<wave> in .control/reports/ by wdi-build before the wave closes. It is REQUIRED on a wave `L` and advisory on `S` and `M` — V19 is tied to wave size, not to `mode`, and skipping it MUST be stated rather than left silent.",
-  "Every row of the distillation table in .constitution/document/bmad-guide.md MUST be complete before a wave is declared closed.",
-]
+# Runs in stories mode: reads SPEC.md + stories.yaml + stories/<id>-*.md, not
+# sprint-status.yaml. Its output is RETROSPECTIVE.md inside the spec folder — which is ephemeral.
+
+[workflow]
+
+persistent_facts = [
+  "This repo runs in stories mode. RETROSPECTIVE.md MUST be archived as RTR-<wave> in .control/reports/ by wdi-build before the wave closes. It is REQUIRED on a wave `L` and advisory on `S` and `M` — V19 is tied to wave size, not to `mode`, and skipping it MUST be stated rather than left silent.",
+  "Every row of the distillation table in .constitution/method/document/bmad-guide.md MUST be complete before a wave is declared closed.",
+]

package/kit/assets/bmad-custom/bmad-spec.toml

@@ -1,16 +1,16 @@
-# Class C — one run per (wave x Product Component), spent once G5 closes.
-#
-# The slug decides whether a spec is ephemeral or lives on: the same slug lands in the same
-# folder and keeps its capability ID. A slug per-PC alone would turn SPEC.md into a living
-# document per PC — a direct rival to the SRS. The slug w<N>-<pc> keeps the spec ephemeral, and
-# CAP-N stays sound because it is allocated from the registry, not from BMad's own internal
-# mechanism.
-
-[workflow]
-
-persistent_facts = [
-  "A spec slug MUST take the shape w<N>-<pc>, one run per (wave x Product Component) pair.",
-  "SPEC.md MUST NOT carry anything that did not come from the SRS, SDD, or PRD. A new finding MUST be landed in the corpus by the skill that owns that layer — the ownership table in .constitution/document/corpus-guide.md — before the wave closes, never left sitting in the spec.",
-  "CAP-N MUST be allocated from {project-root}/.control/registry/requirements.yaml.",
-  "file:{project-root}/.control/product-glossary.md",
-]
+# Class C — one run per (wave x Product Component), spent once G5 closes.
+#
+# The slug decides whether a spec is ephemeral or lives on: the same slug lands in the same
+# folder and keeps its capability ID. A slug per-PC alone would turn SPEC.md into a living
+# document per PC — a direct rival to the SRS. The slug w<N>-<pc> keeps the spec ephemeral, and
+# CAP-N stays sound because it is allocated from the registry, not from BMad's own internal
+# mechanism.
+
+[workflow]
+
+persistent_facts = [
+  "A spec slug MUST take the shape w<N>-<pc>, one run per (wave x Product Component) pair.",
+  "SPEC.md MUST NOT carry anything that did not come from the SRS, SDD, or PRD. A new finding MUST be landed in the corpus by the skill that owns that layer — the ownership table in .constitution/method/document/corpus-guide.md — before the wave closes, never left sitting in the spec.",
+  "CAP-N MUST be allocated from {project-root}/.control/registry/requirements.yaml.",
+  "file:{project-root}/.control/product-glossary.md",
+]

package/kit/assets/bmad-custom/bmad-ux.toml

@@ -1,19 +1,19 @@
-# Class B — the path is configurable, per-PC granularity is not.
-#
-# bmad-ux only knows {project_name} and {date}, no {slug}, so it cannot land directly into
-# .how/<pc>/. Its landing zone is made NEUTRAL in _bmad-output/ because its output splits across
-# two layers: DESIGN.md belongs to .how/, EXPERIENCE.md belongs to .what/. Landing in either one
-# first would be a layer violation that lives for the length of one run.
-
-[workflow]
-
-ux_output_path     = "{project-root}/_bmad-output/ux"
-run_folder_pattern = "ux"
-
-doc_standards = ["file:{project-root}/.constitution/document/ux-guide.md"]
-
-persistent_facts = [
-  "Every memlog.py call MUST use --path {project-root}/.control/memlog/ux.md. --workspace MUST NOT be used.",
-]
-
-on_complete = "Hand the landing to wdi-ux: DESIGN.md to .how/<pc>/01-ux/, tokens and base components to .how/_platform/design-system.md, EXPERIENCE.md to .what/<pc>/04-usecases/, every screen registered as an LC ui-screen in components.yaml. MUST NOT land itself."
+# Class B — the path is configurable, per-PC granularity is not.
+#
+# bmad-ux only knows {project_name} and {date}, no {slug}, so it cannot land directly into
+# .how/<pc>/. Its landing zone is made NEUTRAL in _bmad-output/ because its output splits across
+# two layers: DESIGN.md belongs to .how/, EXPERIENCE.md belongs to .what/. Landing in either one
+# first would be a layer violation that lives for the length of one run.
+
+[workflow]
+
+ux_output_path     = "{project-root}/_bmad-output/ux"
+run_folder_pattern = "ux"
+
+doc_standards = ["file:{project-root}/.constitution/method/document/ux-guide.md"]
+
+persistent_facts = [
+  "Every memlog.py call MUST use --path {project-root}/.control/memlog/ux.md. --workspace MUST NOT be used.",
+]
+
+on_complete = "Hand the landing to wdi-ux: DESIGN.md to .how/<pc>/01-ux/, tokens and base components to .how/_platform/design-system.md, EXPERIENCE.md to .what/<pc>/04-usecases/, every screen registered as an LC ui-screen in components.yaml. MUST NOT land itself."

package/kit/skills/wdi-blueprint/SKILL.md

@@ -32,7 +32,7 @@ of that is `wdi-component` at G4. You MUST NOT write a promise; when the bluepri
 | `.control/product-glossary.md` | Terms already fixed |
 | `.control/decisions/` | `accepted` and `applied` decisions an `AD-N` usually sits behind |
 | `src/` · `web/` | What actually runs, when this is not a new project |
-| `.constitution/document/srs-guide.md` · `architecture-guide.md` | The rules the result is checked against |
+| `.constitution/method/document/srs-guide.md` · `architecture-guide.md` | The rules the result is checked against |
 
 ## Step 1 — Position
 
@@ -65,7 +65,7 @@ whose nouns nobody defined.
 the count passes a third of a component's use cases, derive it again — `delivery-flow-guide.md` owns the rule
 and it MUST NOT be negotiated.
 
-**A method term MUST NOT be written into `.constitution/method-glossary.md`.** A product term binds one
+**A method term MUST NOT be written into `.constitution/method/method-glossary.md`.** A product term binds one
 project; a method term binds every project the method is installed in. Raise it as a proposal, state where it
 appeared and why the existing vocabulary does not cover it, and hand it to the owner.
 
@@ -152,7 +152,7 @@ copy inside any SDD.
 | State | How each is born |
 |---|---|
 | No code yet | Written as a **plan** — the tables, endpoints, and screens intended. Nothing can be derived, because there is no source |
-| Code exists | **Derived first** by `.constitution/scripts/inventory.py` — migrations for tables, route registration for endpoints, pages for screens — then compared with the plan. The difference is a **finding**, not hand work |
+| Code exists | **Derived first** by `.constitution/method/scripts/inventory.py` — migrations for tables, route registration for endpoints, pages for screens — then compared with the plan. The difference is a **finding**, not hand work |
 
 An inventory MUST NOT be assembled from a README or from route names that look plausible. Numbers are stable:
 a new row takes the next number, never a renumber.