wdi-method 0.4.3 → 0.4.6

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

@@ -1,15 +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.",
-]
+# This skill has no `persistent_facts` key, so house rules cannot be injected through the usual
+# path. `preferences` is the equivalent lever: literal sentences a reviewer follows every
+# session.
+#
+# Only a house rule that changes HOW a critique lands belongs here — the full method stays in
+# .constitution/document/delivery-flow-guide.md.
+
+[workflow]
+
+preferences = [
+  "Honor AGENTS.md and .constitution/document/ as the rules currently in force in this repo.",
+  "Judge a G1-G4 artifact chiefly by its Decision Summary: one page, business language, no jargon that lacks a Glossary entry. A summary that cannot be read in full within its gate's time budget is the finding itself.",
+  "There are only five normative words — MUST, MUST NOT, SHOULD, SHOULD NOT, MAY — in English and uppercase; the surrounding prose follows the product's chosen `doc_language`. Flag as a defect: any other imperative marker in any language, a translated method term, or an invented equivalent for a technical term the industry writes in English.",
+  "Pushback MUST name the decision actually at stake and its cost if wrong, not merely grade the writing.",
+]

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

@@ -1,8 +1,9 @@
-# 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.
+# Class A — initiative altitude only.
+# The spine holds the invariants that keep separately built units from diverging.
+# Structure (stack, tree, data shapes) is treated as a seed, not a contract.
 #
-# Urutan mengikat: spine lebih dulu, bmad-spec membacanya sebagai companion — bukan sebaliknya.
+# Order binds: the spine comes first, and bmad-spec reads it as a companion — never the other
+# way round.
 
 [workflow]
 
@@ -10,22 +11,23 @@ spine_template     = "{project-root}/.constitution/document/templates/architectu
 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:
+# architecture-guide.md MUST NOT be installed as doc_standards, even though that is the usual
+# place for a document guide. This skill deliberately excludes the spine from doc_standards —
+# its own default customize.toml says "never to the spine", and SKILL.md step 5 repeats it:
 # "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.
+# Installed there, the AD-N rule would only polish the deck and C4 — documents that carry no
+# AD-N — while the spine itself gets written with no guide at all. So it is installed as a
+# persistent fact, held from activation, rather than as end-of-run polish.
 #
-# 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.
+# doc_standards is deliberately left empty. BMad's own default
+# `skill:bmad-review lenses=structure,prose` still applies to rendering, and this array appends —
+# emptying it does not remove the 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.
+# The consequence is that the spine gets no automatic review. `bmad-review` on it MUST be called
+# manually before G4 — see the "Who calls bmad-review" table in 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.",
+  "Every memlog.py call MUST use --path {project-root}/.control/memlog/spine.md. --workspace MUST NOT be used.",
 ]

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

@@ -1,10 +1,10 @@
-# Satu iterasi loop tanpa interaksi manusia. Dispatch lewat {spec_folder} + {story_id}.
+# One loop iteration with no human in it. Dispatched through {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.",
+  "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 +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.
+# 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,12 +1,13 @@
-# Review Panel: dua peninjau dari dua keluarga CLI berbeda, dan tidak boleh dari keluarga yang
-# menjalankan implementasinya.
+# Review Panel: two reviewers from two different CLI families, and neither may come from the
+# family that ran the implementation.
 #
-# 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.
+# 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/codebase/conventions-guide.md",
-  "Temuan yang berulang lintas story MUST dicatat lewat bmad-project-context intent record, bukan diperbaiki diam-diam tiap kali muncul.",
+  "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-correct-course.toml

@@ -1,27 +1,28 @@
-# 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/."
+# 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/."

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

@@ -1,11 +1,12 @@
-# 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.",
-]
+# This skill ships with `persistent_facts = []`, so unlike the other 41 skills it picks up no
+# project context of its own. This file closes that gap; without it, research ahead of G1 runs
+# with no vocabulary and no repo rules, and its output uses terms that don't exist in the
+# Glossary.
+
+[workflow]
+
+persistent_facts = [
+  "file:{project-root}/.control/product-glossary.md",
+  "A research report lands in _bmad-output/ and stays there permanently. It MUST NOT be promoted into .what/ and MUST NOT be folded into the brief or a PRD; a `DEC-` or PRD references it by path instead. Its run folder MUST NOT be deleted — intent Update reads it back as original inputs.",
+  "A domain term MUST use the Glossary entry as written. A new term surfacing from research MUST be proposed as a Glossary entry, not used silently.",
+]

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

@@ -1,42 +1,42 @@
-# Kelas A — menulis langsung ke korpus.
+# Class A — writes straight into the corpus.
 #
-# 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.
+# 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 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.
+# 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.
 #
-# 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.
+# 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 = "ISI-slug-inisiatif"
+run_folder_pattern = "FILL-initiative-slug"
 
 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.
+# 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, 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.",
+  "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.",
 
-  "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.",
+  "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.",
 
-  "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.",
+  "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.",
 
-  "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.",
+  "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.",
 
-  "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.",
+  "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 @@
-# 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.",
-]
+# 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.",
+]

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

@@ -1,9 +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.",
-]
+# 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.",
+]

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

@@ -1,15 +1,16 @@
-# Kelas C — satu run per (wave x Product Component), habis setelah G5.
+# Class C — one run per (wave x Product Component), spent once G5 closes.
 #
-# 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.
+# 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 = [
-  "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.",
+  "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",
 ]

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

@@ -1,9 +1,9 @@
-# Kelas B — path bisa dikonfigurasi, granularitas per-PC tidak.
+# Class B — the path is configurable, per-PC granularity is not.
 #
-# 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.
+# 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]
 
@@ -13,7 +13,7 @@ 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.",
+  "Every memlog.py call MUST use --path {project-root}/.control/memlog/ux.md. --workspace MUST NOT be used.",
 ]
 
-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."
+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/assets/bmad-custom/config.toml

@@ -1,6 +1,6 @@
-# Dipasang di langkah 1 runbook — MUST lebih dulu dari yang lain.
+# Installed at runbook step 1 — MUST come before anything else.
 #
-# bmad-help dan bmad-correct-course membaca {project_knowledge}. Selama ia menunjuk docs/,
-# keduanya membaca folder yang sudah dibubarkan.
+# bmad-help and bmad-correct-course read {project_knowledge}. As long as it points at docs/,
+# both read a folder that has already been dissolved.
 
 project_knowledge = "{project-root}/.control"