Use this template when adding or changing behavior in an existing codebase.

• Project:
• Feature:
• Branch:
• Date:
• Owner:
• Status: Draft | Approved | In Progress | Blocked | Complete
• Execution mode:
• Human-control mode:
• Linked Roadmap / Master Plan item:

State the feature goal in one paragraph.

• Existing user workflow:
• Existing code path:
• Existing data:
• Existing tests:
• Known defects or limitations:

Use this section when module boundaries are unclear.

• Module map location:
• Confirmed modules:
• Inferred modules:
• Uncertain modules:
• Components discovered:
• Missing owners or boundaries:
• Questions for human review:

• Modules:
• Components:
• Public APIs, routes, commands, or events:
• Data model and migrations:
• UI flows:
• Background jobs:
• External providers:
• Auth, permissions, or tenant boundaries:
• Docs and diagrams:
• Tests:

• Change type: additive | behavior-changing | migration-backed | contract-breaking | feature-flagged | expand-contract
• Compatibility constraints:
• Migration or backfill:
• Rollback plan:
• Explicit approval needed:

• Spec location:
• New behavior:
• Non-goals:
• Acceptance criteria:
• BDD scenarios:

For each slice:

• Slice:
• User-visible behavior:
• Files, modules, or components:
• Tests:
• Exit signal:

• First valid test layer:
• RED evidence required:
• Smart test selection:
• Unit tests:
• Component tests:
• Integration tests:
• Contract tests:
• Performance tests:
• Resilience tests:
• Migration tests:
• Smoke test:
• Manual test:
• Regression evidence:

• Matrix required: yes | no
• Matrix location:
• Release decision owner:

• Risk:
  • Mitigation:

• Plan approval before implementation: yes
• Final human gate before commit, push, PR, archive, or merge: yes