Some New Feature — Plan
The plan turns the brief's "what" and "why" into a concrete approach. It's where decisions get made and trade-offs get named.
Approach
A short narrative description of how you'll build this. Two or three paragraphs — not a checklist, not pseudocode. A reader should be able to picture the shape of the solution without reading any code.
Decisions
| # | Decision | Choice | Why |
|---|---|---|---|
| 1 | Example decision | Option A | Trade-off reasoning |
| 2 | Another | Option B | Another rationale |
Decisions are locked once they land here. If something changes later, log it in the iterations section at the bottom instead of editing the table.
Phasing
Break the work into phases that can ship independently:
- Foundation — refactor without behavior change
- Feature — the new capability
- Polish — UX, docs
Each phase should be reviewable on its own.
Open questions
Questions that need an answer before implementation begins. Often the right move is to ask the user — recommendations attached.
Iterations log
- v1 — first pass