bmad-template/.codebuddy/skills/bmad-quick-dev/spec-template.md

---

title: ‘{title}’ type: ‘feature’ # feature | bugfix | refactor | chore created: ‘{date}’ status: ‘draft’ # draft | ready-for-dev | in-progress | in-review | done

context: [] # optional: {project-root}/-prefixed paths to project-wide standards/docs the implementation agent should load. Keep short — only what isn’t already distilled into the spec body.

Intent

Problem: ONE_TO_TWO_SENTENCES

Approach: ONE_TO_TWO_SENTENCES

Boundaries & Constraints

Always: INVARIANT_RULES

Ask First: DECISIONS_REQUIRING_HUMAN_APPROVAL

Never: NON_GOALS_AND_FORBIDDEN_APPROACHES

I/O & Edge-Case Matrix

Scenario	Input / State	Expected Output / Behavior	Error Handling
HAPPY_PATH	INPUT	OUTCOME	N/A
ERROR_CASE	INPUT	OUTCOME	ERROR_HANDLING

Code Map

• FILE -- ROLE_OR_RELEVANCE
• FILE -- ROLE_OR_RELEVANCE

Tasks & Acceptance

Execution:

• FILE -- ACTION -- RATIONALE

Acceptance Criteria:

• Given PRECONDITION, when ACTION, then EXPECTED_RESULT

Spec Change Log

Design Notes

DESIGN_RATIONALE_AND_EXAMPLES

Verification

Commands:

• COMMAND -- expected: SUCCESS_CRITERIA

Manual checks (if no CLI):

• WHAT_TO_INSPECT_AND_EXPECTED_STATE