wdi-method 0.3.0

package/kit/.constitution/structure-guide.md

@@ -0,0 +1,202 @@
+---
+status: Accepted
+---
+
+# Structure Guide
+
+**Loaded when:** writing, reading, or refreshing a structure map — `.control/structure-codebase.md`
+or `.control/structure-document.md`.
+
+## Two maps
+
+| Map | Describes | Derived | Refreshed by |
+|---|---|---|---|
+| `.control/structure-codebase.md` | The code tree: what runs, what it is built from, where new code goes | `wdi-init` intent `structure` | `wdi-init` intent `structure` |
+| `.control/structure-document.md` | The corpus tree: which layers and slots actually carry content today | `wdi-init` intent `structure` | `wdi-init` intent `structure` |
+
+Both ship as empty skeletons, so the slot is taken from day one. The first run replaces a skeleton
+**wholesale** rather than filling it in; a half-derived map that still carries skeleton headings
+cannot be told apart from a stale one. The intent MAY be run read-only — derive, report the drift,
+write nothing — and that is the right mode when the caller is unsure.
+
+**The maps live in `.control/`, this guide lives here, and the split is deliberate.** A guide states
+a rule that holds before the thing exists; a map states what is currently true. That is the same
+line the kit already draws between `decision-guide.md` and `.control/decisions/`, and between
+`corpus-guide.md` and `.control/registry/`. The two MUST NOT be merged, and a map MUST NOT be moved
+into `.constitution/` because it happens to be read alongside these guides.
+
+Consequence worth knowing: `.control/` is `{project_knowledge}`, so both maps are visible to the
+BMad skills that read it. That is intended — a builder that knows where code goes is the point.
+
+## Descriptive, not prescriptive — the line that MUST hold
+
+This is the whole reason the maps can exist without colliding with the guides already in
+`.constitution/`.
+
+| Question | Answered by |
+|---|---|
+| Where does this live, and what is already there? | **structure map** |
+| Which layer owns it, and what is it named? | `document/corpus-guide.md` |
+| How is code named, and which patterns apply? | `codebase/conventions-guide.md` |
+| What is it built with, and on which version? | `codebase/stack-guide.md` |
+| Which legacy shapes are ratified rather than fixed? | `codebase/brownfield-guide.md` |
+
+- A structure map MUST NOT restate a naming rule, a layer rule, or a version. It MUST reference the
+  guide that owns it.
+- A guide MUST NOT carry a directory tree. A tree in a guide goes stale silently, because nothing
+  refreshes it.
+- Where a map and a guide disagree, the **guide** wins on the rule and the **map** wins on the fact.
+  The disagreement itself MUST be reported, not smoothed over — one of the two is lying.
+
+## What a map MUST contain
+
+1. A **Verified** line: date plus the commit the tree was read at.
+2. A **top-level tree**: every base folder in the root, complete, one annotated line each.
+3. A **section per unit**, each carrying its folder convention as an annotated tree.
+4. **Key files marked `★` inline**, inside those trees.
+
+Nothing else. A map that also explains how the system works has become an architecture document,
+and `.how/` already owns that.
+
+The form is an **annotated tree**, not prose and not a file table. A tree shows convention and
+location in the same glance, and a `★` next to a filename is read at the moment it matters. Both
+maps MUST close with the one-line legend for `★`.
+
+## How units are split
+
+Each map splits its sections along the axis its reader is lost on, and the two axes differ:
+
+| Map | Sections | Split by |
+|---|---|---|
+| `structure-codebase.md` | Containers · Libraries · the non-unit sections below | **Deployability** |
+| `structure-document.md` | One per layer that carries content | **Layer** |
+
+For the codebase map the distinction is exact and MUST NOT be softened:
+
+- A **container** runs its own code or stores its own data, and can be replaced without rebuilding
+  another one. `architecture-guide.md` owns the two-question test; this map only applies it. The term
+  MUST NOT be renamed to "application", "service", or "app" here — a synonym for a term that already
+  has a glossary entry is drift, and `wdi-reconcile` hunts for it. It does not mean a Docker image.
+- A **library** is an includable artifact — compiled into or imported by something else, never run
+  on its own. A library with an entry point is a container wearing the wrong label, and a library
+  MUST NOT appear at C4 L2.
+- Anything that is neither is not a unit. It stays a line in the top-level tree, or in one of the
+  non-unit sections below.
+- A unit that stops being separately deployable MUST move sections, not keep its old heading.
+
+### The registry match is one-directional
+
+**Every container heading MUST be a container registered in `components.yaml`. Not every registered
+container gets a heading.** Reading it both ways makes the rule unsatisfiable: a `built: false` container
+— a database, a web server — MUST be registered, because it runs inside the boundary and carries NFRs,
+and MUST NOT get a heading, because no code of ours lives there. So the check is **heading = exactly the
+`built: true` containers**, and V25 runs it. `c4-l2-containers.md` still owns the list itself.
+
+### Sections that are not units
+
+Containers and Libraries are the unit sections. A map MAY also carry sections for what is not a unit at
+all, and these MUST NOT be dressed up as containers to earn a place:
+
+| Section | Holds |
+|---|---|
+| **Tooling** | Scripts run by a human or by CI, never deployed |
+| **Generated** | Output, named with its generator — that is what makes a hand edit visible |
+| **Unclaimed** | A folder that exists with no stated purpose. A finding, not a category |
+
+The list is open, the test is not: a section that is neither a unit nor one of these MUST say in one line
+why it exists.
+
+## Base folders — complete
+
+- MUST list every base folder that exists, including the ones that look uninteresting. An unlisted
+  folder is the one people misuse, because nothing told them what it was for.
+- MUST descend only until directories stop carrying distinct roles. A shape that repeats MUST be
+  described once, generically, rather than enumerated per instance.
+- MUST mark a folder that exists but has no stated purpose as unclaimed instead of inventing one.
+  An unclaimed folder is a finding, and `wdi-init` MUST report it.
+- MUST NOT list a folder that the architecture implies but no file has created yet.
+
+## Key files — selective
+
+A file earns a `★` only if it passes one of these:
+
+- It is an entry point, a composition root, or where dependencies get wired.
+- It is the single place a rule is enforced for the whole tree below it.
+- An agent asked to change behaviour in that folder would have to open it first.
+- Removing it would change what the folder *is*, not merely what it does.
+
+Everything else MUST be left out. Completeness at file level is what killed every source-tree
+document that came before: it is impossible to keep true, so it stops being read.
+
+A folder with no key file MUST still appear in the tree. Folders are complete; files are not.
+
+## Freshness — this is a living document
+
+- The **Verified** line MUST carry a date and a commit SHA. Without the SHA, staleness cannot be
+  measured, only felt.
+- A map MUST be refreshed when a base folder is born or removed, when a key file moves or is
+  renamed, when a project or container is added, or when a key file's role changes.
+- **Wave close** carries this hook — it left the story-closing checklist along with four other items,
+  because a structural change is visible at the end of a wave and guessed at the end of a story.
+- A map MUST NOT be edited by hand. `wdi-init` intent `structure` re-derives it from the actual tree;
+  a hand edit records what someone remembers, and memory is exactly what the map exists to replace.
+- A map whose **Verified** commit is no longer an ancestor of `HEAD` SHOULD be treated as stale, and
+  MUST be refreshed before a gate that reads it.
+
+## `structure-codebase.md` — specifics
+
+- Born as a skeleton listing only what exists. On an empty repo that is almost nothing, and that is
+  correct: writing the tree the spine implies means guessing.
+- Each unit's tree MUST show its **folder convention** — including the shape a feature repeats,
+  written once with a placeholder, never enumerated per feature.
+- Each container MUST mark its entry point and its composition root with `★`. A container whose
+  tree has neither has not been read properly.
+- Each container SHOULD carry one **Flow** line: the authoritative call direction through its
+  folders. A builder who gets that wrong writes code that works and is still wrong. MUST NOT be
+  invented where none exists.
+- Each library MUST state who consumes it. A library nobody consumes is a finding.
+- Generated output MUST be named with its generator, even when it looks like ordinary source — that
+  is what makes a hand edit visible.
+- MUST NOT carry framework versions, and MUST NOT repeat the suffix list from
+  `conventions-guide.md`. Where new code goes is answered by the convention tree itself; how it is
+  named is not this file's question.
+
+## `structure-document.md` — specifics
+
+- The four layers and the workspace are fixed by `corpus-guide.md`. This map records which of them
+  actually carry content: which Product Component folders exist, which slots have been split out of
+  a kernel, which registries are populated.
+- MUST reference the placement test rather than restating it, and MUST NOT explain slot numbering —
+  `corpus-guide.md` owns both.
+- MUST list every Product Component folder that exists in `.what/` or `.how/`, and MUST flag any
+  that exists on one side only. A PC with an SRS and no SDD is drift, not layout.
+- Product Component folders MUST live in the table, and MUST NOT also be expanded in the per-layer
+  trees. Maintaining the same fact in two places is how one of them starts lying.
+
+## File names MUST survive every OS the repo is cloned on
+
+This is the one structural rule that is not about where a file sits but about whether it can exist at
+all. It applies to every file any skill in this method creates — corpus documents, generated tables,
+spec folders, and code alike.
+
+| Rule | Detail |
+|---|---|
+| Forbidden characters | `\ / : * ? " < > \|` MUST NOT appear in a file or folder name |
+| Substitution | A forbidden character MUST be replaced by `-` or dropped, and the substitution MUST be consistent across the repo |
+| Trailing characters | A name MUST NOT end in a space or a `.` — Windows strips both silently, and the read path then no longer matches the write path |
+| Length | A single path segment SHOULD stay under 255 characters |
+
+The failure this prevents is not cosmetic. A repository whose branches carry `:` in a filename
+**cannot be checked out on Windows at all** — `git checkout` fails outright, and recovering the
+content takes per-blob extraction plus a rename map. That has happened in a sibling repo, which is
+why this is stated as a rule rather than left to taste.
+
+A name derived from something else — an endpoint path, a URL, a title — MUST be sanitised at the
+moment it becomes a filename, and the mapping SHOULD be recorded when it is not reversible by
+inspection.
+
+## Writing rules
+
+Inherited from `.constitution/`: normative keyword on every instruction, concise, no duplication,
+English, SHOULD stay under 200 lines. A map that outgrows 200 lines is marking files that never
+earned a `★` — cut those, never the folders.

package/kit/assets/bmad-custom/bmad-advanced-elicitation.toml

@@ -0,0 +1,15 @@
+# Skill ini tidak punya key `persistent_facts`, jadi aturan rumah tidak bisa disuntikkan lewat
+# jalur biasa. `preferences` adalah tuas setaranya: kalimat literal yang dipatuhi perefine tiap
+# sesi.
+#
+# Hanya aturan rumah yang mengubah CARA sebuah kritik mendarat yang pantas di sini — metode
+# lengkapnya tetap di .constitution/document/delivery-flow-guide.md.
+
+[workflow]
+
+preferences = [
+  "Honor AGENTS.md dan .constitution/document/ sebagai aturan yang sedang berlaku di repo ini.",
+  "Nilai artefak G1-G4 terutama dari Decision Summary-nya: satu halaman, bahasa bisnis, tanpa jargon yang belum punya entri Glossary. Ringkasan yang tidak bisa dibaca habis dalam time budget gate-nya adalah temuan itu sendiri.",
+  "Kata normatif hanya lima — MUST, MUST NOT, SHOULD, SHOULD NOT, MAY — dalam bahasa Inggris dan huruf besar; prosanya tetap Bahasa Indonesia. Tandai sebagai cacat: penanda imperatif lain dalam bahasa apa pun, istilah metode yang diterjemahkan, dan karangan padanan Indonesia untuk istilah teknis yang lazim ditulis dalam bahasa Inggris.",
+  "Pushback MUST menyebut keputusan yang sedang dipertaruhkan dan ongkosnya bila salah, bukan sekadar menilai tulisannya.",
+]

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

@@ -0,0 +1,31 @@
+# Kelas A — altitude initiative saja.
+# Spine memuat invariant yang mencegah unit yang dibangun terpisah jadi divergen.
+# Struktur (stack, tree, data shape) diperlakukan sebagai seed, bukan kontrak.
+#
+# Urutan mengikat: spine lebih dulu, bmad-spec membacanya sebagai companion — bukan sebaliknya.
+
+[workflow]
+
+spine_template     = "{project-root}/.constitution/document/templates/architecture-spine.md"
+spine_output_path  = "{project-root}/.how/_platform"
+run_folder_pattern = "architecture"
+
+# architecture-guide.md MUST NOT dipasang sebagai doc_standards, meski itu tempat lazimnya
+# bagi guide dokumen. Skill ini mengecualikan spine dari doc_standards secara sengaja —
+# customize.toml bawaannya menyebut "never to the spine", dan langkah 5 SKILL.md mengulanginya:
+# "apply {workflow.doc_standards} polish to that prose only, never to the spine".
+# Dipasang di sana, aturan AD-N cuma memoles deck dan C4 — dokumen yang tidak punya AD-N —
+# sementara spine ditulis tanpa guide-nya. Karena itu ia jadi fakta yang dipegang sejak
+# aktivasi, bukan poles di akhir.
+#
+# doc_standards sengaja tidak diisi. Default BMad `skill:bmad-review lenses=structure,prose`
+# tetap berlaku untuk rendering, dan array ini append — mengosongkannya tidak mencabut default.
+#
+# Akibatnya spine tidak punya review otomatis. `bmad-review` atasnya MUST dipanggil manual
+# sebelum G4 — lihat tabel "Siapa memanggil bmad-review" di 05-gates.md.
+
+persistent_facts = [
+  "file:{project-root}/.constitution/document/architecture-guide.md",
+  "file:{project-root}/.constitution/document/decision-guide.md",
+  "Seluruh panggilan memlog.py MUST memakai --path {project-root}/.control/memlog/spine.md. --workspace MUST NOT dipakai.",
+]

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

@@ -0,0 +1,10 @@
+# Satu iterasi loop tanpa interaksi manusia. Dispatch lewat {spec_folder} + {story_id}.
+
+[workflow]
+
+persistent_facts = [
+  "Repo ini berjalan di stories mode. sprint-status.yaml tidak ada dan MUST NOT dibuat.",
+  "Disiplin test-first mengikat: test MUST gagal lebih dulu, dan MUST gagal karena alasan yang diharapkan.",
+  "Worker MUST NOT mengubah apa pun di luar story yang didispatch. Perubahan yang dinilai perlu di luar itu MUST dinyatakan di hasil akhir, tidak pernah dilakukan diam-diam.",
+  "Saat test atau build gagal dan sebabnya belum diketahui, wdi-systematic-debugging MUST dijalankan sebelum perbaikan apa pun diusulkan. Percobaan perbaikan ketiga yang gagal adalah tanda untuk berhenti dan melapor, bukan untuk mencoba keempat.",
+]

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

@@ -0,0 +1,52 @@
+# G5 — satu-satunya pelaksana, dan wdi-build yang mendispatch-nya. Pelaksana MUST NOT merakit
+# rantai sendiri.
+#
+# Memasok disiplin test-first yang bmad-build tidak punya: ia mengaudit test SETELAH implementasi
+# (Matrix Test Audit di step-03), tetapi tidak pernah mewajibkan sebuah test gagal lebih dulu.
+#
+# Aturan merge: string mengganti, list menambah, tabel merge per key.
+# .claude/skills/bmad-build/customize.toml MUST NOT diedit — ia ditimpa tiap update.
+
+[workflow]
+
+# Mengganti handoff step-03 bawaan. Semua yang dibawa bawaan tetap ada (subagent tanpa konteks
+# percakapan, spec sebagai satu-satunya sumber kebenaran, memuat berkas `context:`, laporan
+# penutup); siklus test-first inilah yang ditambahkan override ini.
+#
+# Sengaja memuat METODE saja. Pernyataan ulang tujuan, daftar berkas, acceptance criteria, dan
+# aturan gaya rumah TIDAK masuk dispatch — semuanya sudah ada di spec, dan step-03 melarang
+# menggandakannya di sini.
+
+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 = [
+  "Repo ini berjalan di stories mode. sprint-status.yaml tidak ada dan MUST NOT dibuat; status story tinggal di frontmatter story file.",
+  "Satu Logical Component MUST terdaftar di components.yaml sebelum story yang menyentuhnya dikerjakan.",
+  "Saat ada yang rusak dan sebabnya belum diketahui, wdi-systematic-debugging MUST dijalankan sebelum perbaikan apa pun diusulkan.",
+]
+
+# Tidak dioverride, dan itu disengaja:
+#
+# - review_layers — tiga layer bawaan (blind-hunter, edge-case-hunter, verification-gap) plus
+#   Review Panel dua keluarga CLI yang dijalankan bmad-code-review sesudahnya sudah menutup
+#   kebutuhan review repo ini. Menambah layer keempat memakan token tanpa menutup celah.
+#
+# - on_complete — pembaruan registry setelah story selesai adalah tugas wdi-build dan skill pemilik
+#   lapisannya,
+#   bukan bmad-build. Menaruhnya di sini membuat dua penulis untuk satu berkas.
+#   Checklist penutup story ada di 05-gates.md.

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

@@ -0,0 +1,12 @@
+# Review Panel: dua peninjau dari dua keluarga CLI berbeda, dan tidak boleh dari keluarga yang
+# menjalankan implementasinya.
+#
+# PERINGATAN: lensa adversarial dan edge-case di sini dibaca dari salinan bundel review-prompts/,
+# BUKAN dari skill bmad-review. Override pada bmad-review tidak akan terlihat di jalur ini.
+
+[workflow]
+
+persistent_facts = [
+  "file:{project-root}/.constitution/codebase/conventions-guide.md",
+  "Temuan yang berulang lintas story MUST dicatat lewat bmad-project-context intent record, bukan diperbaiki diam-diam tiap kali muncul.",
+]

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

@@ -0,0 +1,27 @@
+# Kelas B — tidak ada knob path sama sekali.
+#
+# customize.toml bawaan bmad-correct-course hanya membuka activation_steps, persistent_facts, dan
+# on_complete. Tidak ada *_output_path, jadi proposalnya tetap mendarat di
+# _bmad-output/planning-artifacts/sprint-change-proposal-{date}.md dan MUST didaratkan ulang oleh
+# wdi-decision sebagai `DEC-` bertipe course-correction. Kode `SCP-` dan folder
+# .control/supplements/ SUDAH DICABUT — koreksi arah adalah keputusan, dan tidak ada kode kedua yang
+# menamai hal yang sama.
+#
+# Bahaya utamanya bukan path, melainkan kebiasaan skill ini menyunting langsung: default-nya
+# "direct updates to epics, stories, or PRD sections". Di repo ini itu MUST NOT terjadi — perubahan
+# dokumen lewat wdi-decision intent `apply`, isi wave lewat wdi-build. Karena itu larangannya
+# dipasang sebagai persistent_facts, yang dipegang sejak aktivasi, bukan sebagai poles di akhir.
+
+[workflow]
+
+persistent_facts = [
+  "file:{project-root}/.constitution/document/delivery-flow-guide.md",
+  "file:{project-root}/.constitution/document/corpus-guide.md",
+  "Skill ini MUST NOT menulis atau menyunting apa pun di {project-root}/.what/ maupun {project-root}/.how/. Keluarannya adalah proposal; perubahan dokumen dikerjakan wdi-decision intent `apply` setelah `DEC-`-nya accepted, dan isi wave oleh wdi-build.",
+  "epics.md dan sprint-status.yaml TIDAK dipakai di repo ini — kita menjalankan stories route. Keduanya MUST NOT dibaca sebagai sumber, dan MUST NOT dibuat.",
+  "Pemindaian impak MUST mencakup .what/_prd/, .what/<pc>/, .how/_platform/, .how/<pc>/, SPEC.md, .control/registry/waves.yaml, dan berkas story. .what/<pc>/ tidak dikenal skill ini sama sekali dan tanpa ini akan basi diam-diam.",
+  "Setiap perubahan rencana yang mahal dibalik MUST menjadi `DEC-` lewat wdi-decision, bukan paragraf di dalam proposal. Koreksi arah sendiri adalah satu `DEC-` bertipe course-correction.",
+  "Sebuah koreksi yang membatalkan lebih dari 30% story sebuah wave MUST NOT ditangani sebagai tambalan. Katakan begitu, dan biarkan wave-nya dipotong ulang lewat wdi-build.",
+]
+
+on_complete = "Serahkan pendaratan ke wdi-decision: seluruh proposal jadi satu `DEC-` bertipe course-correction, dan folder run-nya MUST NOT dihapus. MUST NOT menempatkan sendiri, MUST NOT menyunting .what/ atau .how/."

package/kit/assets/bmad-custom/bmad-deep-recon.toml

@@ -0,0 +1,11 @@
+# Skill ini dikirim dengan `persistent_facts = []`, jadi tidak seperti 41 skill lain ia tidak
+# memungut konteks proyek sendiri. Berkas ini menutup celah itu; tanpanya riset menjelang G1 berjalan
+# tanpa kosakata dan aturan repo, dan hasilnya memakai istilah yang tidak ada di Glossary.
+
+[workflow]
+
+persistent_facts = [
+  "file:{project-root}/.control/product-glossary.md",
+  "Laporan riset mendarat di _bmad-output/ dan tinggal di sana selamanya. Ia MUST NOT dipromosikan ke .what/ dan MUST NOT dilebur ke brief maupun PRD; `DEC-` dan PRD merujuknya lewat path. Folder run-nya MUST NOT dihapus — intent Update membacanya kembali sebagai original inputs.",
+  "Istilah domain MUST memakai entri Glossary apa adanya. Istilah baru yang muncul dari riset MUST diusulkan sebagai entri Glossary, bukan dipakai diam-diam.",
+]

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

@@ -0,0 +1,42 @@
+# Kelas A — menulis langsung ke korpus.
+#
+# Satu PRD per **inisiatif / area fungsi**, bukan per rilis. Ia living document:
+# perubahan perilaku masuk lewat intent Update ke PRD yang sama, bukan PRD baru.
+# Rilis dibawa registry lewat target_release, bukan oleh nama folder.
+#
+# run_folder_pattern MUST diisi slug inisiatif dan MUST NOT memakai {date}.
+# Saat inisiatif baru dibuka, DUA baris MUST diubah bersamaan:
+#   1. run_folder_pattern             -> slug inisiatif berikutnya
+#   2. --path .../prd-<slug>.md       -> memlog inisiatif berikutnya
+# Mengubah salah satu saja menghasilkan PRD baru yang menempel pada memlog lama.
+#
+# Nilai bawaan di bawah sengaja tidak bisa dipakai apa adanya — ia MUST diganti
+# di langkah 4 runbook. PRD yang mendarat di folder bernama ISI-slug-inisiatif
+# adalah tanda langkah itu terlewat.
+
+[workflow]
+
+prd_template       = "{project-root}/.constitution/document/templates/prd.md"
+prd_output_path    = "{project-root}/.what/_prd"
+run_folder_pattern = "ISI-slug-inisiatif"
+
+doc_standards = ["file:{project-root}/.constitution/document/prd-guide.md"]
+
+# Fakta di bawah sengaja mengulang sebagian prd-guide.md. Sebabnya waktu: doc_standards baru
+# menyala di langkah Polish, sedangkan deteksi intent Create-versus-Update terjadi di aktivasi.
+# Yang otoritatif tetap prd-guide.md; kalau keduanya berselisih, guide yang menang dan baris di
+# sini MUST diperbaiki.
+persistent_facts = [
+  "file:{project-root}/.control/registry/requirements.yaml",
+  "file:{project-root}/.constitution/document/prd-guide.md",
+
+  "FR-N, NFR-N, UJ-N, dan CAP-N MUST dialokasikan dari requirements.yaml dan MUST NOT dimulai ulang dari 1. PRD inisiatif berikutnya melanjutkan deret PRD sebelumnya — deretnya global, satu produk satu deret.",
+
+  "PRD ini living document. Perubahan perilaku, penambahan fitur yang erat kaitannya, maupun koreksi janji MUST masuk lewat intent Update ke PRD yang sama. PRD baru MUST NOT dibuat hanya karena rilisnya berganti; ia dibuat hanya saat area fungsinya benar-benar berbeda dan tidak enak dibaca kalau digabung.",
+
+  "Tiap run intent Update MUST menambah tepat satu baris di tabel Revision History PRD: tanggal, apa yang berubah dalam bahasa pembaca luar, dan sebabnya. Tabel itu untuk pembaca; memlog untuk audit. Keduanya MUST NOT saling menggantikan.",
+
+  "Rilis MUST NOT dinyatakan lewat nama folder PRD maupun judulnya. Ia dibawa field target_release di requirements.yaml dan waves.yaml. Menyebut nomor rilis di dalam prosa PRD MAY dilakukan sebagai konteks, tetapi yang mengikat tetap registry.",
+
+  "Seluruh panggilan memlog.py — init, append, set, dan pembacaan saat resume atau intent Update — MUST memakai --path {project-root}/.control/memlog/prd-ISI-slug-inisiatif.md. Slug-nya MUST sama dengan run_folder_pattern di atas, dan kedua baris MUST diubah bersamaan saat inisiatif berganti. --workspace MUST NOT dipakai.",
+]

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

@@ -0,0 +1,34 @@
+# Kelas A — menulis langsung ke korpus.
+# Singleton: satu produk, satu brief, lintas rilis. Produk kedua MUST dapat repo sendiri.
+#
+# Dipanggil lewat `wdi-problem`, bukan langsung. Override di sini yang menentukan
+# ke mana artefaknya mendarat; skill wrapper yang memeriksa isinya.
+
+[workflow]
+
+brief_template     = "{project-root}/.constitution/document/templates/brief.md"
+
+# run_folder_pattern MUST konstan — tanpa {project_name} dan tanpa {date}.
+# Itu yang memaksa singleton: tiap run jatuh ke folder yang sama, jadi run kedua
+# terdeteksi sebagai resume/update, bukan folder sebelah.
+# Hasilnya .what/_product-brief/brief.md dan .what/_product-brief/addendum.md;
+# kedua nama berkas itu di-hardcode di SKILL.md dan tidak bisa diatur.
+brief_output_path  = "{project-root}/.what"
+run_folder_pattern = "_product-brief"
+
+# Append-only terhadap default `skill:bmad-review lenses=structure,prose`.
+doc_standards = ["file:{project-root}/.constitution/document/brief-guide.md"]
+
+persistent_facts = [
+  "Seluruh panggilan memlog.py — init, append, set, dan pembacaan saat resume atau intent Update — MUST memakai --path {project-root}/.control/memlog/brief.md. --workspace MUST NOT dipakai; ia akan menaruh .memlog.md di dalam .what/, dan tidak ada memlog yang boleh tinggal di korpus.",
+
+  "Template brief membuka dengan izin membuang section yang tidak layak. Izin itu MUST NOT diterapkan pada delapan section wajib: The Problem, Who This Serves, Goals, Success Criteria, Scope In, Scope Out, Constraints, Assumptions — beserta Prerequisites. Section template lain MAY dibuang.",
+
+  "Goals MUST bernomor BG-1, BG-2, dan seterusnya. MUST NOT bernomor G1, G2 — G1 sampai G5 adalah nama lima gate di metode ini, dan BG adalah mata rantai pertama rantai traceability BG -> CAP -> FR/NFR -> UC -> Story -> Test.",
+
+  "Tabel Who This Serves MUST memuat tepat satu baris bertanda primary, dan MUST memuat seluruh stakeholder termasuk yang tidak pernah membuka produknya.",
+
+  "Brief MUST NOT memuat daftar Product Component dan MUST NOT mengisi product_components maupun logical_components. Slicing lahir di EKOR G2 lewat wdi-init intent `component`, dibaca dari brief plus seluruh PRD.",
+
+  "Keluaran riset, brainstorming, forge, dan PRFAQ MUST tetap di _bmad-output/. Ia MUST NOT dilebur ke dalam brief dan MUST NOT dipromosikan ke .what/; `DEC-` atau PRD merujuknya lewat path. Folder run itu MUST NOT dihapus — intent Update membacanya kembali sebagai original inputs.",
+]

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

@@ -0,0 +1,9 @@
+# Berjalan di stories mode: membaca SPEC.md + stories.yaml + stories/<id>-*.md, bukan
+# sprint-status.yaml. Keluarannya RETROSPECTIVE.md di dalam folder spec — yang fana.
+
+[workflow]
+
+persistent_facts = [
+  "Repo ini berjalan di stories mode. RETROSPECTIVE.md MUST diarsipkan jadi RTR-<wave> di .control/reports/ oleh wdi-build sebelum wave ditutup. Ia WAJIB pada wave `L` dan advisory pada `S` dan `M` — V19 diikatkan ke ukuran wave, bukan ke `mode`, dan melewatinya MUST dinyatakan alih-alih didiamkan.",
+  "Seluruh baris tabel distilasi di .constitution/document/bmad-guide.md MUST tuntas sebelum wave dinyatakan tertutup.",
+]

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

@@ -0,0 +1,15 @@
+# Kelas C — satu run per (wave x Product Component), habis setelah G5.
+#
+# Slug menentukan apakah spec fana atau hidup: slug yang sama mendarat di folder yang sama dan
+# mempertahankan capability ID. Slug per-PC saja akan membuat SPEC.md jadi dokumen hidup per PC —
+# saingan langsung SRS. Slug w<N>-<pc> menjaga spec tetap fana, dan CAP-N tetap terjaga karena
+# dialokasikan dari registry, bukan dari mekanisme internal BMad.
+
+[workflow]
+
+persistent_facts = [
+  "Slug spec MUST berbentuk w<N>-<pc>, satu run per pasangan wave x Product Component.",
+  "SPEC.md MUST NOT memuat apa pun yang tidak berasal dari SRS, SDD, atau PRD. Temuan baru MUST didaratkan ke korpus oleh skill pemilik lapisannya — tabel kepemilikan di .constitution/document/corpus-guide.md — sebelum wave ditutup, bukan dibiarkan tinggal di spec.",
+  "CAP-N MUST dialokasikan dari {project-root}/.control/registry/requirements.yaml.",
+  "file:{project-root}/.control/product-glossary.md",
+]

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

@@ -0,0 +1,19 @@
+# Kelas B — path bisa dikonfigurasi, granularitas per-PC tidak.
+#
+# bmad-ux hanya mengenal {project_name} dan {date}, tidak ada {slug}, jadi ia tidak bisa mendarat
+# sendiri ke .how/<pc>/. Landing zone-nya dibuat NETRAL di _bmad-output/ karena keluarannya
+# membelah dua lapisan: DESIGN.md milik .how/, EXPERIENCE.md milik .what/. Mendarat lebih dulu di
+# salah satunya adalah pelanggaran lapisan yang hidup selama satu 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 = [
+  "Seluruh panggilan memlog.py MUST memakai --path {project-root}/.control/memlog/ux.md. --workspace MUST NOT dipakai.",
+]
+
+on_complete = "Serahkan pendaratan ke wdi-ux: DESIGN.md ke .how/<pc>/01-ux/, token dan komponen dasar ke .how/_platform/design-system.md, EXPERIENCE.md ke .what/<pc>/04-usecases/, tiap layar didaftarkan sebagai LC ui-screen di components.yaml. MUST NOT menempatkan sendiri."

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

@@ -0,0 +1,6 @@
+# Dipasang di langkah 1 runbook — MUST lebih dulu dari yang lain.
+#
+# bmad-help dan bmad-correct-course membaca {project_knowledge}. Selama ia menunjuk docs/,
+# keduanya membaca folder yang sudah dibubarkan.
+
+project_knowledge = "{project-root}/.control"