The roadmap is the plan — what we intend to build and in what order. It answers two questions:
- Where are we going? —
phases/(Phase A through Phase J). - Where are we now? —
current.md.
The plan is separate from the work. Individual tasks and reviews live under ../analysis/ and are cross-linked from here. See ADR-0013 for the rationale behind this split.
| Path | Purpose |
|---|---|
README.md |
This file. |
phases/README.md |
Index of phase files with a one-paragraph summary each. |
phases/phase-<letter>.md |
Detailed breakdown of one phase, with its milestones and acceptance criteria. |
current.md |
Short pointer to the active phase, milestone, and task. Updated often. |
- Individual task user stories — they live under
../analysis/tasks/phase-<letter>/. - Reviews — they live under
../analysis/reviews/<type>/. - Design rationale for architectural choices —
../decisions/(ADRs). - Procedural rules —
../standards/. - Repeatable procedures —
../../.agents/skills/.
- New to the project: read
phases/README.md, then skim the phase files top-to-bottom. Then look atcurrent.mdto see where work is. - Returning after a pause: open
current.mdfirst. It points to the active phase / milestone / task and the date of the last review. - Planning the next work session:
current.mdnames the active task; the task file lists its acceptance criteria; the phase file shows what it leads to.
- Phase IDs are letters (A, B, C, …), in execution order, stable once published.
- Milestone IDs are
<phase><N>(A1, A2, …), stable once the milestone becomes active. - Task IDs (
T-NNN) are stable across the whole project and live under../analysis/tasks/.
See ADR-0013 for the full identifier and change-process rules.
- Tweaking a phase's milestones or sub-breakdowns — edit the phase file.
- Adding or dropping a phase, or reordering phases at the top level — structural change; requires an ADR that supersedes the affected statements.
- Opening a new task —
start-taskskill. - Running a review —
conduct-reviewskill.