Files
Ken Yasue 00cb087f77 Add /execute-milestones to run milestones one by one with per-milestone steering docs
- New command /execute-milestones: executes all (or selected) milestones strictly in order; for each milestone creates a separate .steering/[date]-milestone-NN-[name]/ directory, divides its features into tasks grouped by feature, implements, validates, tests, reconciles docs, and updates milestone/roadmap statuses before starting the next
- New skill milestone-execution: per-milestone steering structure, task-division rules, gate criteria between milestones, and failure handling
- plan-milestones completion message, AGENTS.md, README, and docs/milestones/README.md updated

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-02 11:32:01 +02:00

42 lines
1.8 KiB
Markdown

# Milestone Documents (`docs/milestones/`)
This directory holds the project's **milestone plan**: an ordered breakdown of the product into releases, with the features for each milestone. It is created by `/plan-milestones` and kept up to date by `/add-feature`.
## Structure
```
docs/milestones/
├── roadmap.md # Overview: milestone table, ordering rationale, icebox
├── milestone-01-[name].md # Milestone 1 (the MVP)
├── milestone-02-[name].md
└── milestone-NN-[name].md
```
## File purposes
### `roadmap.md`
The overview: a table of all milestones (goal, feature count, status), the ordering rationale, a pointer to the current milestone, and a "Later / Icebox" list of consciously deferred items.
### `milestone-[NN]-[name].md`
One document per milestone. Contains the milestone's goal, scope, dependencies, and its **feature list** — each feature sized for exactly one `/add-feature` run, with description, related PRD requirements, affected screens, acceptance criteria, and the ready-to-run command.
## Status tracking
- Each feature has a checkbox in its milestone document; `/add-feature` checks it off (`[ ]``[x]`) when the feature completes.
- Milestone status (`Not started` / `In progress` / `Completed`) is kept in sync between the milestone document and the roadmap table.
## Workflow
```
/setup-project → product/architecture docs
/define-design → UI/UX design spec
/generate-app → initial app shell
/plan-milestones → creates the files above
/execute-milestones → implements all milestones one by one (one steering directory per milestone), updating statuses here
/add-feature → implements one feature, then checks it off here
```
## Status
This directory is populated by running `/plan-milestones`. Until then, the files above do not exist.