Skill Tracer
Skills › BMAD Method › bmad-build › plan-template.md

plan-template.md

112 lines · skills/bmad-build/plan-template.md at bd70c64

Open on GitHub
1---
2title: '{title}'
3type: 'feature' # feature | bugfix | refactor | chore
4ticket: '' # the entry id from the ticket tree, or the story file's stem when the entry has no id; empty outside it
5created: '{date}'
6status: 'draft' # draft | ready-for-dev | in-progress | in-review | built | done | blocked | dropped
7baseline_revision: '' # the commit the work starts from, set before any code change
8route: '' # oneshot | full — set by step-02
9route_source: '' # pinned | auto — set with route by step-02
10risk: '' # low | medium | high — set by step-02; a CI process can read it to decide how much review the change gets
11review: '' # none | quick | thorough — set by step-04
12review_source: '' # pinned | auto — set with review by step-04
13lenses_ran: [] # ids of the lenses launched, set by step-04
14review_loop_iteration: 0 # incremented by step-04 before each review loopback
15context: [] # optional: `{project-root}/`-prefixed paths the implementation agent should load: companions the ticket names that this work needs, and project-wide standards. Keep short — only what isn't already distilled into the plan body.
16---
18<!-- Target: 900–1300 tokens (less if route is oneshot). Above 1600 = high risk of context rot.
19 Never over-specify "how" — use boundaries + examples instead.
20 Cohesive cross-layer changes (DB+BE+UI) stay in ONE file.
21 IMPORTANT: Remove all HTML comments when filling this template. -->
23<frozen-after-approval reason="human-owned intent — do not modify unless human renegotiates">

<!-- Target: 900–1300 tokens (less if route is oneshot). Above 1600 = high risk of context rot. Never over-specify "how" — use boundaries + examples instead. Cohesive cross-layer changes (DB+BE+UI) stay in ONE file. IMPORTANT: Remove all HTML comments when filling this template. -->

<frozen-after-approval reason="human-owned intent — do not modify unless human renegotiates">

Raw lines 1 to 24
25## Intent
27<!-- What is broken or missing, and why it matters. Then the high-level approach — the "what", not the "how". -->
29**Problem:** ONE_TO_TWO_SENTENCES
31**Approach:** ONE_TO_TWO_SENTENCES

Intent

<!-- What is broken or missing, and why it matters. Then the high-level approach — the "what", not the "how". -->

Problem: ONE_TO_TWO_SENTENCES

Approach: ONE_TO_TWO_SENTENCES

Raw lines 25 to 32
33## Boundaries & Constraints
35<!-- Two tiers: Always = invariant rules. Never = out of scope + forbidden approaches.
36 Delete this section if route is oneshot. -->
38**Always:** INVARIANT_RULES
40**Never:** NON_GOALS_AND_FORBIDDEN_APPROACHES

Boundaries & Constraints

<!-- Two tiers: Always = invariant rules. Never = out of scope + forbidden approaches. Delete this section if route is oneshot. -->

Always: INVARIANT_RULES

Never: NON_GOALS_AND_FORBIDDEN_APPROACHES

Raw lines 33 to 41
42## I/O & Edge-Case Matrix
44<!-- If no meaningful I/O scenarios exist, delete this section. Do not write "N/A" or "None".
45 Delete this section if route is oneshot. -->
47| Scenario | Input / State | Expected Output / Behavior | Error Handling |
48|----------|--------------|---------------------------|----------------|
49| HAPPY_PATH | INPUT | OUTCOME | No error expected |
50| ERROR_CASE | INPUT | OUTCOME | ERROR_HANDLING |
52</frozen-after-approval>

I/O & Edge-Case Matrix

<!-- If no meaningful I/O scenarios exist, delete this section. Do not write "N/A" or "None". Delete this section if route is oneshot. -->

ScenarioInput / StateExpected Output / BehaviorError Handling
HAPPY_PATHINPUTOUTCOMENo error expected
ERROR_CASEINPUTOUTCOMEERROR_HANDLING

</frozen-after-approval>

Raw lines 42 to 53
54## Code Map
56<!-- Agent-populated during planning. Annotated paths prevent blind codebase searching.
57 Delete this section if route is oneshot. -->
59- `FILE` -- ROLE_OR_RELEVANCE
60- `FILE` -- ROLE_OR_RELEVANCE

Code Map

<!-- Agent-populated during planning. Annotated paths prevent blind codebase searching. Delete this section if route is oneshot. -->

  • FILE -- ROLE_OR_RELEVANCE
  • FILE -- ROLE_OR_RELEVANCE
Raw lines 54 to 61
62## Tasks & Acceptance
64<!-- Tasks: backtick-quoted file path -- action -- rationale. Prefer one task per file; group tightly-coupled changes when splitting would be artificial. -->
65<!-- If an I/O Matrix is present, include a task to unit-test its edge cases. -->
66<!-- AC covers system-level behaviors not captured by the I/O Matrix. Do not duplicate I/O scenarios here. -->
67<!-- Delete this section if route is oneshot. -->
69**Execution:**
70- [ ] `FILE` -- ACTION -- RATIONALE
72**Acceptance Criteria:**
73- Given PRECONDITION, when ACTION, then EXPECTED_RESULT

Tasks & Acceptance

<!-- Tasks: backtick-quoted file path -- action -- rationale. Prefer one task per file; group tightly-coupled changes when splitting would be artificial. --> <!-- If an I/O Matrix is present, include a task to unit-test its edge cases. --> <!-- AC covers system-level behaviors not captured by the I/O Matrix. Do not duplicate I/O scenarios here. --> <!-- Delete this section if route is oneshot. -->

Execution:

  • [ ] FILE -- ACTION -- RATIONALE

Acceptance Criteria:

  • Given PRECONDITION, when ACTION, then EXPECTED_RESULT
Raw lines 62 to 74
75## Implementation Notes
77<!-- Agent-owned. Append-only during implementation: decisions made, files touched, surprises
78 encountered. Never delete this section. Leave empty at planning time, except on the
79 oneshot route: start with a short explanation of why. -->

Implementation Notes

<!-- Agent-owned. Append-only during implementation: decisions made, files touched, surprises encountered. Never delete this section. Leave empty at planning time, except on the oneshot route: start with a short explanation of why. -->

Raw lines 75 to 80
81## Plan Change Log
83<!-- Append-only. Populated by step-04 during review loops. Do not modify or delete existing entries.
84 Each entry records: what finding triggered the change, what was amended, what known-bad state
85 the amendment avoids, and any KEEP instructions (what worked well and must survive re-derivation).
86 Empty until the first bad_plan loopback. -->

Plan Change Log

<!-- Append-only. Populated by step-04 during review loops. Do not modify or delete existing entries. Each entry records: what finding triggered the change, what was amended, what known-bad state the amendment avoids, and any KEEP instructions (what worked well and must survive re-derivation). Empty until the first bad_plan loopback. -->

Raw lines 81 to 87
88## Review Triage Log
90<!-- Append-only. Populated by step-04 on EVERY review pass, including loopbacks and blocked exits.
91 Each entry records verdict counts (high/medium/low/false/maybe-false) and one row per
92 reviewer finding: verdict, route, and evidence — the refutation for false, what would settle
93 it for maybe-false, the action taken for patches. Empty until the first review pass. -->

Review Triage Log

<!-- Append-only. Populated by step-04 on EVERY review pass, including loopbacks and blocked exits. Each entry records verdict counts (high/medium/low/false/maybe-false) and one row per reviewer finding: verdict, route, and evidence — the refutation for false, what would settle it for maybe-false, the action taken for patches. Empty until the first review pass. -->

Raw lines 88 to 94
95## Design Notes
97<!-- If the approach is straightforward, delete this section. Do not write "N/A" or "None".
98 Delete this section if route is oneshot. -->
99<!-- Design rationale and golden examples only when non-obvious. Keep examples to 5–10 lines. -->
101DESIGN_RATIONALE_AND_EXAMPLES

Design Notes

<!-- If the approach is straightforward, delete this section. Do not write "N/A" or "None". Delete this section if route is oneshot. --> <!-- Design rationale and golden examples only when non-obvious. Keep examples to 5–10 lines. -->

DESIGN_RATIONALE_AND_EXAMPLES

Raw lines 95 to 102
103## Verification
105<!-- If no build, test, or lint commands apply, delete this section. Do not write "N/A" or "None". -->
106<!-- How the agent confirms its own work. Prefer CLI commands. When no CLI check applies, state what to inspect manually. -->
108**Commands:**
109- `COMMAND` -- expected: SUCCESS_CRITERIA
111**Manual checks (if no CLI):**
112- WHAT_TO_INSPECT_AND_EXPECTED_STATE

Verification

<!-- If no build, test, or lint commands apply, delete this section. Do not write "N/A" or "None". --> <!-- How the agent confirms its own work. Prefer CLI commands. When no CLI check applies, state what to inspect manually. -->

Commands:

  • COMMAND -- expected: SUCCESS_CRITERIA

Manual checks (if no CLI):

  • WHAT_TO_INSPECT_AND_EXPECTED_STATE
Raw lines 103 to 112