| name | build-plan |
| description | Use when planning what to build and in what order — splitting a project into sequenced, scoped feature phases so the agent never has to decide "what's next" on its own. Use when work feels like random feature-hopping. |
build-plan
Overview
Knowing what to build isn't enough — the agent needs the order. This file splits the project into phases and scoped features so the agent always knows the next step and never invents sequencing mid-build.
Lives at context/build-plan.md.
When to use
- After
project-overview and architecture, before building.
- When the build feels like aimless feature-hopping.
What goes in it
- Phases — group features into a handful of ordered phases (e.g. 25 features across 5 phases).
- Per feature — a one-line definition, its scope, and its position in the sequence.
- Dependencies — which features must come before others.
How to build it
Have a planning conversation with the agent BEFORE coding: describe the product, let it propose a phased feature breakdown, then refine. You can deviate later, but the plan is the default path.
How to maintain
Re-sequence when priorities change. Pair with progress-tracker (what's done) — build-plan is the route, progress-tracker is the position.
Common mistakes
- Features without scope → the agent over- or under-builds. Scope each.
- One giant phase → defeats the purpose. Phase the work so each chunk is shippable.
