wdi-method 0.5.13 → 0.6.0

package/scaffold/.control/registry/specs.yaml

@@ -0,0 +1,5 @@
+# specs.yaml — rencana kerja.
+#
+# `release` MUST disebut tiap spec. STATUS TIKET MUST NOT DISALIN KE SINI.
+
+specs: []

package/scaffold/.control/structure-codebase.md

@@ -1,19 +1,19 @@
----
-type: structure
-scope: codebase
-verified: null
-commit: null
----
-
-# Codebase Structure
-
-Written and refreshed only by `wdi-init` intent `structure`, never by hand. Rules live in
-`.constitution/structure-guide.md`.
-
-## Verified
-
-Not yet derived.
-
-## Top level
-
-Not yet derived. `wdi-init` intent `structure` fills this from the tree on disk.
+---
+type: structure
+scope: codebase
+verified: null
+commit: null
+---
+
+# Codebase Structure
+
+Written and refreshed only by `wdi-init` intent `structure`, never by hand. Rules live in
+`.constitution/method/structure-guide.md`.
+
+## Verified
+
+Not yet derived.
+
+## Top level
+
+Not yet derived. `wdi-init` intent `structure` fills this from the tree on disk.

package/scaffold/.control/structure-document.md

@@ -1,25 +1,25 @@
----
-type: structure
-scope: document
-verified: null
-commit: null
----
-
-# Document Structure
-
-Written and refreshed only by `wdi-init` intent `structure`, never by hand. Rules live in
-`.constitution/structure-guide.md`.
-
-## Verified
-
-Not yet derived.
-
-## Top level
-
-```text
-.constitution/                # how we work — not yet mapped
-.control/                     # what currently holds — not yet mapped
-.what/                        # what was promised — empty
-.how/                         # how it is built — empty
-_bmad-output/                 # run workspace
-```
+---
+type: structure
+scope: document
+verified: null
+commit: null
+---
+
+# Document Structure
+
+Written and refreshed only by `wdi-init` intent `structure`, never by hand. Rules live in
+`.constitution/method/structure-guide.md`.
+
+## Verified
+
+Not yet derived.
+
+## Top level
+
+```text
+.constitution/                # how we work — not yet mapped
+.control/                     # what currently holds — not yet mapped
+.what/                        # what was promised — empty
+.how/                         # how it is built — empty
+_bmad-output/                 # run workspace
+```

package/kit/.constitution/method/document/templates/rtr.md

@@ -1,61 +0,0 @@
----
-type: rtr
-id: RTR-{wave}
-wave: '{W<N>}'
-size: L                  # the wave size that made this required
-status: draft            # draft · reviewed · locked · superseded
-created: '{YYYY-MM-DD}'
----
-
-# RTR-{wave} — Retrospective, wave {W<N>}
-
-<!-- TEMPLATE GUIDE — act on these comments, then delete them.
-
-     Home: .control/reports/RTR-<wave>.md, landed by wdi-build at wave close. Its old home
-     .control/supplements/ is gone.
-
-     REQUIRED on wave `L`. Advisory on `S` and `M`, and skipping it MUST be stated rather than left
-     silent — V19 is advisory for exactly that reason. It is tied to wave SIZE, never to `mode`: depth
-     of documents and volume of work are different things.
-
-     THE SPEC FOLDER IS EPHEMERAL AND THIS IS NOT. bmad-retrospective writes RETROSPECTIVE.md inside
-     the run folder; this is the archived form, and it is the only part that survives the wave.
-
-     WRITE WHAT WAS LEARNED, NOT WHAT HAPPENED. A wave-by-wave narrative is recoverable from git; what
-     is not recoverable is what somebody now knows and would otherwise forget. Every section below is
-     one question, and a section with nothing under it MUST be cut. -->
-
-## What this wave shipped
-
-<!-- One line. Which FR, and whether the RTM rows for them are green. Not a story list. -->
-
-## What took longer than expected, and why
-
-<!-- G5's question 5. One cause, named concretely. "Underestimated" is not a cause. -->
-
-## What the corpus got wrong
-
-<!-- The section this method exists to feed. Every defect whose root_cause was `requirement` or
-     `architecture` rather than code, by BUG- id — and what in .what/ or .how/ was wrong.
-
-     This ratio is a fact about the METHOD, not about the team, and it is the only place it is
-     recorded per wave. -->
-
-| BUG- | Root cause | What was wrong upstream | Fixed where |
-| --- | --- | --- | --- |
-
-## What we would do differently
-
-<!-- Only items with an owner and a next action. An observation nobody owns is not a finding; it is a
-     feeling, and it MUST be cut rather than carried forward into the next wave's reading. -->
-
-| Change | Owner | Where it lands |
-| --- | --- | --- |
-
-<!-- `Where it lands` MUST name a file or a skill. A retrospective item that lands nowhere is why
-     retrospectives get a reputation for being theatre — and it is what makes the next one skippable. -->
-
-## What is deliberately carried forward
-
-<!-- Follow-ups accepted rather than fixed, each pointing at its OQ- or DEC-. Anything here that has
-     no id is being lost right now. -->

package/kit/assets/bmad-custom/bmad-build-auto.toml

@@ -1,10 +0,0 @@
-# One loop iteration with no human in it. Dispatched through {spec_folder} + {story_id}.
-
-[workflow]
-
-persistent_facts = [
-  "This repo runs in stories mode. sprint-status.yaml does not exist and MUST NOT be created.",
-  "Test-first discipline binds: a test MUST fail first, and MUST fail for the expected reason.",
-  "A worker MUST NOT change anything outside the story it was dispatched. A change it judges necessary beyond that MUST be stated in the final report, never made silently.",
-  "When a test or build fails and the cause is not yet known, wdi-systematic-debugging MUST run before any fix is proposed. A third failed fix attempt is the signal to stop and report, not to try a fourth.",
-]

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

@@ -1,52 +0,0 @@
-# G5 — the only executor, dispatched by wdi-build. An executor MUST NOT assemble its own chain.
-#
-# Supplies the test-first discipline bmad-build lacks on its own: it audits tests AFTER
-# implementation (Matrix Test Audit in step-03), but never requires a test to fail first.
-#
-# Merge rule: a string replaces, a list appends, a table merges per key.
-# .claude/skills/bmad-build/customize.toml MUST NOT be edited — it is overwritten on every update.
-
-[workflow]
-
-# Replaces the default step-03 handoff. Everything the default carries stays (a subagent with no
-# conversation context, the spec as the sole source of truth, loading the files listed in
-# `context:`, a closing report); this override adds the test-first cycle on top.
-
-#
-# Deliberately carries METHOD only. Restating the goal, the file list, the acceptance criteria,
-# and house style rules does NOT belong in the dispatch — all of it is already in the spec, and
-# step-03 forbids duplicating it here.
-
-implementation_handoff = """
-Launch a subagent with no prior conversation context, with this prompt:
-
-> Read {spec_file} fully and implement it — the spec is the sole source of truth. Load every file listed in its frontmatter `context:` before you start.
->
-> Work test-first, one task at a time:
->
-> 1. Write the smallest test that expresses the next unmet acceptance criterion.
-> 2. Run it. Confirm it fails, and confirm it fails for the reason you expect — a test that errors on a typo or a missing import has proven nothing.
-> 3. Write the minimum code that makes it pass. No extra scope, no "while I'm here" refactoring.
-> 4. Run the test plus the surrounding suite. Both must be green before you start the next task.
->
-> If a criterion genuinely cannot be expressed as a test — pure configuration, a docs change, a visual-only tweak — say so explicitly in your report and state how you verified it instead. Never invent a test that asserts nothing in order to satisfy the cycle, and never write the implementation first and the test afterwards to make it look followed.
->
-> When done, report what you changed, how you verified it, and anything left incomplete or risky. Include the actual command output for the final test run — a claim of green without the output does not count as verification.
-"""
-
-persistent_facts = [
-  "This repo runs in stories mode. sprint-status.yaml does not exist and MUST NOT be created; story status lives in the story file's own frontmatter.",
-  "A Logical Component MUST be registered in components.yaml before the story touching it is worked.",
-  "When something breaks and the cause is not yet known, wdi-systematic-debugging MUST run before any fix is proposed.",
-]
-
-# Not overridden, and deliberately so:
-#
-# - review_layers — the three default layers (blind-hunter, edge-case-hunter,
-#   verification-gap) plus the two-CLI-family Review Panel that bmad-code-review runs afterward
-#   already cover this repo's review needs. A fourth layer would spend tokens without closing a
-#   gap.
-#
-# - on_complete — updating the registry once a story is done belongs to wdi-build and the skill
-#   that owns that layer, not to bmad-build. Putting it here would give one file two writers.
-#   The story-closing checklist lives in 05-gates.md.

package/kit/assets/bmad-custom/bmad-code-review.toml

@@ -1,13 +0,0 @@
-# Review Panel: two reviewers from two different CLI families, and neither may come from the
-# family that ran the implementation.
-#
-# WARNING: the adversarial and edge-case lenses here are read from the bundled copy of
-# review-prompts/, NOT from the bmad-review skill. An override on bmad-review will not be visible
-# on this path.
-
-[workflow]
-
-persistent_facts = [
-  "file:{project-root}/.constitution/project/codebase-conventions-guide.md",
-  "A finding that repeats across stories MUST be recorded through bmad-project-context intent record, not fixed silently every time it recurs.",
-]

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

@@ -1,9 +0,0 @@
-# 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 +0,0 @@
-# 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/scaffold/.control/registry/requirements.yaml

@@ -1,15 +0,0 @@
-# requirements.yaml — SSOT for BG · CAP · FR · NFR · UJ
-#
-# Keys are English; prose values follow the product's chosen `doc_language`.
-# Numbers are allocated FROM HERE and MUST NOT restart per document, per component, or per release.
-# The sequence is global to one product.
-
-goals: []
-
-capabilities: []
-
-functional: []
-
-nonfunctional: []
-
-journeys: []

package/scaffold/.control/registry/waves.yaml

@@ -1,5 +0,0 @@
-# waves.yaml — rencana kerja.
-#
-# `release` MUST disebut tiap wave. STATUS STORY MUST NOT DISALIN KE SINI.
-
-waves: []