Plan once
You own project-plan.md and build-plan.md. The overview step checks those inputs and generates the compact project context agents read every session.
project-plan.md + build-plan.md -> /overview -> project-overview.mdRun overview again only when the plans change materially.
Repeat for each feature
The normal loop keeps one active scope at a time.
| Stage | Command | Result |
|---|---|---|
| Specify | /feature |
Writes current-feature.md and stops for review |
| Build | /implement |
Makes small changes with explanation and proof |
| Prove | /check |
Runs the real app against the done-when criteria |
| Land | /complete |
Archives, commits, and merges with approval |
If a bug or small request is not in the build plan, use /fix instead of /feature.
Keep human gates visible
The workflow deliberately pauses before application code and before merging. A feature spec is cheaper to change than a large diff, and a diff is cheaper to change than a broken main branch.
Autopilot is an explicit opt-in for a bounded spec, build, and check pass. It keeps the same files and quality gates but delays the human review packet until the pass ends. It still cannot merge, push, deploy, publish, or perform destructive actions without separate approval.
Resume from files
The current feature checklist records completed steps. Git records code and checkpoint commits. After a context clear, $status or /status can determine the exact next action without reconstructing the project from conversation history.