wdi-method 0.4.6 → 0.5.2

package/kit/assets/bmad-custom/bmad-correct-course.toml

@@ -1,28 +1,28 @@
-# Class B — no path knob at all.
-#
-# bmad-correct-course's own default customize.toml only opens activation_steps, persistent_facts,
-# and on_complete. There is no *_output_path, so its proposal still lands at
-# _bmad-output/planning-artifacts/sprint-change-proposal-{date}.md and MUST be landed again by
-# wdi-decision as a `DEC-` of type course-correction. The `SCP-` code and the
-# .control/supplements/ folder have ALREADY BEEN RETIRED — a course correction is a decision, and
-# there is no second code naming the same thing.
-#
-# The main danger is not the path but this skill's habit of editing directly: its default is
-# "direct updates to epics, stories, or PRD sections". In this repo that MUST NOT happen —
-# document changes go through wdi-decision intent `apply`, and wave content through wdi-build.
-# That is why the prohibition is installed as a persistent fact, held from activation, rather than
-# as end-of-run polish.
-
-[workflow]
-
-persistent_facts = [
-  "file:{project-root}/.constitution/document/delivery-flow-guide.md",
-  "file:{project-root}/.constitution/document/corpus-guide.md",
-  "This skill MUST NOT write or edit anything in {project-root}/.what/ or {project-root}/.how/. Its output is a proposal; document changes are made by wdi-decision intent `apply` once the `DEC-` is accepted, and wave content by wdi-build.",
-  "epics.md and sprint-status.yaml are NOT used in this repo — we run the stories route. Neither MUST be read as a source, and neither MUST be created.",
-  "The impact scan MUST cover .what/_prd/, .what/<pc>/, .how/_platform/, .how/<pc>/, SPEC.md, .control/registry/waves.yaml, and the story files. .what/<pc>/ is unknown to this skill entirely, and without this it goes stale silently.",
-  "Every plan change that is expensive to reverse MUST become a `DEC-` through wdi-decision, not a paragraph inside the proposal. A course correction is itself one `DEC-` of type course-correction.",
-  "A correction that voids more than 30% of a wave's stories MUST NOT be handled as a patch. Say so, and let the wave be re-cut through wdi-build.",
-]
-
-on_complete = "Hand the landing to wdi-decision: the whole proposal becomes one `DEC-` of type course-correction, and its run folder MUST NOT be deleted. MUST NOT land itself, MUST NOT edit .what/ or .how/."
+# Class B — no path knob at all.
+#
+# bmad-correct-course's own default customize.toml only opens activation_steps, persistent_facts,
+# and on_complete. There is no *_output_path, so its proposal still lands at
+# _bmad-output/planning-artifacts/sprint-change-proposal-{date}.md and MUST be landed again by
+# wdi-decision as a `DEC-` of type course-correction. The `SCP-` code and the
+# .control/supplements/ folder have ALREADY BEEN RETIRED — a course correction is a decision, and
+# there is no second code naming the same thing.
+#
+# The main danger is not the path but this skill's habit of editing directly: its default is
+# "direct updates to epics, stories, or PRD sections". In this repo that MUST NOT happen —
+# document changes go through wdi-decision intent `apply`, and wave content through wdi-build.
+# That is why the prohibition is installed as a persistent fact, held from activation, rather than
+# as end-of-run polish.
+
+[workflow]
+
+persistent_facts = [
+  "file:{project-root}/.constitution/method/document/delivery-flow-guide.md",
+  "file:{project-root}/.constitution/method/document/corpus-guide.md",
+  "This skill MUST NOT write or edit anything in {project-root}/.what/ or {project-root}/.how/. Its output is a proposal; document changes are made by wdi-decision intent `apply` once the `DEC-` is accepted, and wave content by wdi-build.",
+  "epics.md and sprint-status.yaml are NOT used in this repo — we run the stories route. Neither MUST be read as a source, and neither MUST be created.",
+  "The impact scan MUST cover .what/_prd/, .what/<pc>/, .how/_platform/, .how/<pc>/, SPEC.md, .control/registry/waves.yaml, and the story files. .what/<pc>/ is unknown to this skill entirely, and without this it goes stale silently.",
+  "Every plan change that is expensive to reverse MUST become a `DEC-` through wdi-decision, not a paragraph inside the proposal. A course correction is itself one `DEC-` of type course-correction.",
+  "A correction that voids more than 30% of a wave's stories MUST NOT be handled as a patch. Say so, and let the wave be re-cut through wdi-build.",
+]
+
+on_complete = "Hand the landing to wdi-decision: the whole proposal becomes one `DEC-` of type course-correction, and its run folder MUST NOT be deleted. MUST NOT land itself, MUST NOT edit .what/ or .how/."

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

@@ -1,42 +1,42 @@
-# Class A — writes straight into the corpus.
-#
-# One PRD per **initiative / functional area**, not per release. It is a living document:
-# a behaviour change goes through intent Update on the same PRD, never a new one.
-# A release is carried by the registry through target_release, not by the folder name.
-#
-# run_folder_pattern MUST be filled with the initiative slug and MUST NOT use {date}.
-# When a new initiative opens, TWO lines MUST change together:
-#   1. run_folder_pattern             -> the next initiative's slug
-#   2. --path .../prd-<slug>.md       -> the next initiative's memlog
-# Changing only one produces a new PRD stuck to the old memlog.
-#
-# The default value below is deliberately unusable as-is — it MUST be replaced at runbook
-# step 4. A PRD landing in a folder literally named FILL-initiative-slug is the sign that step
-# was skipped.
-
-[workflow]
-
-prd_template       = "{project-root}/.constitution/document/templates/prd.md"
-prd_output_path    = "{project-root}/.what/_prd"
-run_folder_pattern = "FILL-initiative-slug"
-
-doc_standards = ["file:{project-root}/.constitution/document/prd-guide.md"]
-
-# The facts below deliberately repeat part of prd-guide.md. The reason is timing: doc_standards
-# only activates at the Polish step, while Create-versus-Update intent detection happens at
-# activation. prd-guide.md remains authoritative; where the two disagree, the guide wins and the
-# line here MUST be fixed.
-persistent_facts = [
-  "file:{project-root}/.control/registry/requirements.yaml",
-  "file:{project-root}/.constitution/document/prd-guide.md",
-
-  "FR-N, NFR-N, UJ-N, and CAP-N MUST be allocated from requirements.yaml and MUST NOT restart from 1. The next initiative's PRD continues the previous PRD's sequence — the sequence is global, one product, one sequence.",
-
-  "This PRD is a living document. A behaviour change, a closely related feature addition, or a promise correction MUST go through intent Update on the same PRD. A new PRD MUST NOT be created just because the release changed; it is created only when the functional area is genuinely different and reads badly if merged.",
-
-  "Every intent Update run MUST add exactly one row to the PRD's Revision History table: the date, what changed in language an outside reader understands, and why. That table is for the reader; the memlog is for the audit. Neither MUST substitute for the other.",
-
-  "A release MUST NOT be stated through the PRD's folder name or its title. It is carried by the target_release field in requirements.yaml and waves.yaml. Naming a release number inside the PRD's prose MAY be done as context, but the registry remains what binds.",
-
-  "Every memlog.py call — init, append, set, and the read on resume or intent Update — MUST use --path {project-root}/.control/memlog/prd-FILL-initiative-slug.md. The slug MUST match run_folder_pattern above, and both lines MUST change together when the initiative changes. --workspace MUST NOT be used.",
-]
+# Class A — writes straight into the corpus.
+#
+# One PRD per **initiative / functional area**, not per release. It is a living document:
+# a behaviour change goes through intent Update on the same PRD, never a new one.
+# A release is carried by the registry through target_release, not by the folder name.
+#
+# run_folder_pattern MUST be filled with the initiative slug and MUST NOT use {date}.
+# When a new initiative opens, TWO lines MUST change together:
+#   1. run_folder_pattern             -> the next initiative's slug
+#   2. --path .../prd-<slug>.md       -> the next initiative's memlog
+# Changing only one produces a new PRD stuck to the old memlog.
+#
+# The default value below is deliberately unusable as-is — it MUST be replaced at runbook
+# step 4. A PRD landing in a folder literally named FILL-initiative-slug is the sign that step
+# was skipped.
+
+[workflow]
+
+prd_template       = "{project-root}/.constitution/method/document/templates/prd.md"
+prd_output_path    = "{project-root}/.what/_prd"
+run_folder_pattern = "FILL-initiative-slug"
+
+doc_standards = ["file:{project-root}/.constitution/method/document/prd-guide.md"]
+
+# The facts below deliberately repeat part of prd-guide.md. The reason is timing: doc_standards
+# only activates at the Polish step, while Create-versus-Update intent detection happens at
+# activation. prd-guide.md remains authoritative; where the two disagree, the guide wins and the
+# line here MUST be fixed.
+persistent_facts = [
+  "file:{project-root}/.control/registry/requirements.yaml",
+  "file:{project-root}/.constitution/method/document/prd-guide.md",
+
+  "FR-N, NFR-N, UJ-N, and CAP-N MUST be allocated from requirements.yaml and MUST NOT restart from 1. The next initiative's PRD continues the previous PRD's sequence — the sequence is global, one product, one sequence.",
+
+  "This PRD is a living document. A behaviour change, a closely related feature addition, or a promise correction MUST go through intent Update on the same PRD. A new PRD MUST NOT be created just because the release changed; it is created only when the functional area is genuinely different and reads badly if merged.",
+
+  "Every intent Update run MUST add exactly one row to the PRD's Revision History table: the date, what changed in language an outside reader understands, and why. That table is for the reader; the memlog is for the audit. Neither MUST substitute for the other.",
+
+  "A release MUST NOT be stated through the PRD's folder name or its title. It is carried by the target_release field in requirements.yaml and waves.yaml. Naming a release number inside the PRD's prose MAY be done as context, but the registry remains what binds.",
+
+  "Every memlog.py call — init, append, set, and the read on resume or intent Update — MUST use --path {project-root}/.control/memlog/prd-FILL-initiative-slug.md. The slug MUST match run_folder_pattern above, and both lines MUST change together when the initiative changes. --workspace MUST NOT be used.",
+]

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."