ken/claudecode-boilerplate
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add milestone planning phase between /generate-app and /add-feature

Browse Source 
- New command /plan-milestones: generates docs/milestones/ (roadmap.md + one document per milestone with its features, acceptance criteria, and ready-to-run /add-feature commands)
- New skill milestone-planning: MVP-first vertical-slice planning rules + milestone/roadmap templates
- /add-feature: reads the feature's milestone document before planning and checks the feature off (updating milestone/roadmap status) in Step 8
- Workflow diagrams, CLAUDE.md, README, and settings.json updated for the new phase

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Ken Yasue
2026-07-02 10:14:32 +02:00
parent f04ef5e182
commit 92d34e2814
10 changed files with 394 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
README.md
View File

@ -13,7 +13,7 @@ https://github.com/GenerativeAgents/claude-code-book
How a project goes from idea to working code with this boilerplate:
```
Idea → /setup-project → /define-design → refine design → /generate-app → /add-feature (repeat)
Idea → /setup-project → /define-design → refine design → /generate-app → /plan-milestones → /add-feature (repeat)
```
### Step 1 — Write down your idea
@ -42,19 +42,26 @@ This is the key design-decision gate: iterate on the design while it is still ch
Scaffolds the app shell from the approved design: theme (from tokens), routes, screens, and
reusable components. No feature logic yet.
### Step 6 — Implement features: `/add-feature <feature>`
A fully autonomous loop, one feature at a time. Each run:
### Step 6 — Plan milestones: `/plan-milestones`
Breaks the product into an ordered set of milestones and generates `docs/milestones/`:
a `roadmap.md` overview plus one document per milestone listing **the features it contains** —
each sized for exactly one `/add-feature` run, with acceptance criteria and a ready-to-run command.
Milestone 1 is the MVP; later milestones build on it by priority and dependency.
### Step 7 — Implement features: `/add-feature <feature>`
A fully autonomous loop, one feature at a time, milestone by milestone. Each run:
1. Creates `.steering/[YYYYMMDD]-[feature]/` (requirements, design, tasklist)
2. Reads the design spec first — and updates it first if the feature changes the UI
2. Reads the feature's milestone document and the design spec first — and updates the design first if the feature changes the UI
3. Implements every task in `tasklist.md`, checking items off as it goes
4. Validates quality with the `implementation-validator` subagent
5. Runs `npm test`, `npm run lint`, `npm run typecheck` until green
6. Records a retrospective and reconciles all six `docs/` documents with the feature
6. Records a retrospective, reconciles all six `docs/` documents, and checks the feature off in its milestone document
### Step 7 — Repeat and maintain
- More features → `/add-feature <feature>` (again and again)
### Step 8 — Repeat and maintain
- More features → `/add-feature <feature>`, working through the milestones in order
- UI changes → `/update-design <change>` first, then `/add-feature`
- Re-planning → re-run `/plan-milestones` or edit `docs/milestones/` in conversation
- Document quality checks → `/review-docs <path>`
**A feature is "done" when**: all tasks in its tasklist are `[x]`, validation passes,
@ -91,7 +98,8 @@ claude
> /define-design
> /update-design [refinement] # repeat until the design is approved
> /generate-app web # or flutter | winui3
> /add-feature [feature name]
> /plan-milestones
> /add-feature [feature name] # milestone by milestone
```
See [Development Workflow (Step by Step)](#development-workflow-step-by-step) above for what each step does.
@ -104,5 +112,6 @@ See [Development Workflow (Step by Step)](#development-workflow-step-by-step) ab
| `/define-design` | Create the UI/UX design spec under `docs/design/` | `/define-design` |
| `/update-design` | Refine the design before generation, or update it when a feature changes the UI | `/update-design add a profile screen` |
| `/generate-app` | Scaffold the initial app for a target platform | `/generate-app web` |
| `/plan-milestones` | Plan milestones and generate milestone documents with the features for each | `/plan-milestones 3 milestones, MVP first` |
| `/add-feature` | Implement a feature end-to-end (autonomous) | `/add-feature User profile editing` |
| `/review-docs` | Detailed document review via subagent | `/review-docs docs/architecture.md` |