# Development Roadmap

Build in vertical slices that produce demonstrable user value. Each phase ends with tested evidence and a go/no-go decision; calendar dates alone do not make a milestone complete.

[Kit README](README.md) · [Project Overview](Project%20Overview.md) · [PRD](Full%20PRD%20Template.md) · [Master Build Prompt](Master%20Build%20Prompt.md) · [Completion Checklist](Project%20Completion%20Checklist.md)

## Roadmap

| Phase | Objective | Required Evidence | Owner | Target |
| --- | --- | --- | --- | --- |
| 0 — Confirm | Approve overview, evidence, MVP, PRD, architecture, and acceptance tests | [DEMO + TESTS + REVIEW] | [OWNER] | [DATE] |
| 1 — Foundation | Create project structure, quality checks, environments, tokens, and core domain model | [DEMO + TESTS + REVIEW] | [OWNER] | [DATE] |
| 2 — Vertical Slice | Implement one thin end-to-end path through home page | [DEMO + TESTS + REVIEW] | [OWNER] | [DATE] |
| 3 — MVP Capabilities | Complete one reusable content template, about or proof page, contact path | [DEMO + TESTS + REVIEW] | [OWNER] | [DATE] |
| 4 — Reliability | Handle permissions, errors, recovery, accessibility, performance, and unclear positioning | [DEMO + TESTS + REVIEW] | [OWNER] | [DATE] |
| 5 — Release | Migrate data, deploy safely, monitor, document, and complete the launch review | [DEMO + TESTS + REVIEW] | [OWNER] | [DATE] |

## Phase Gate Template

~~~text
Phase: [NAME]
Goal: [USER OR RISK OUTCOME]
Inputs: [APPROVED DOCUMENTS / DEPENDENCIES]
Included stories: [IDS]
Tasks: [SMALL BUILD/TEST/DOC ITEMS]
Automated evidence: [TESTS / METRICS]
Manual evidence: [DEMO / ACCESSIBILITY / REVIEW]
Risks retired: [RISKS]
Open decisions: [OWNER + DATE]
Exit decision: [PROCEED / REVISE / STOP]
~~~

## Build Order Rules

1. Establish formatting, type checking, tests, secret handling, and reproducible setup before feature growth.
2. Implement a thin slice through the real interface, application rules, and persistence or local state.
3. Add one user story at a time with its tests and states.
4. Run security, accessibility, performance, and failure checks continuously.
5. Keep migrations backward-compatible through rollout where practical.
6. Do not begin CMS authoring while a P0 flow is incomplete or failing.

## Status Reporting

Report completed outcomes, evidence, blockers, changed assumptions, risks, and next decisions. Avoid status based only on percentages. A feature is done when code, tests, states, permissions, documentation, and acceptance evidence agree.

## Completion Gates

- [ ] Every phase has one accountable owner and measurable exit criteria.
- [ ] Dependencies and decisions have due dates.
- [ ] High-risk technical questions are tested before large feature investment.
- [ ] Testing and documentation are scheduled with implementation.
- [ ] Release includes monitoring, backup, rollback, support, and feedback capture.
- [ ] Deferred work remains visible but does not quietly enter the MVP.