Plan

Create tasks that a new agent can finish without making product or technical decisions. Every task and milestone must be a vertical slice: a usable outcome that runs through the required layers and has acceptance checks. Split by working result, not by file, layer, or team boundary.

Process

1. Read the source, repository instructions, and relevant code.
2. Stop and return to /spec if an unresolved choice would change behavior, interfaces, data, security, scale, performance, compatibility, operations, cost, or proof.
3. Split the work into tasks that each deliver working behavior, fit one agent run, and produce one focused pull request.
4. Keep shared contracts in one task. Do not make two tasks answer the same question independently.
5. Separate refactoring when it would hide a behavior change.
6. Order tasks by dependency. Group tasks into milestones when useful. Each milestone delivers a usable end-to-end result, with acceptance checks and dependencies. Do not use milestones such as “database”, “backend”, or “frontend”.
7. Return the plan in chat. Create tracker tickets only when the user asks. Never write a plan document.
8. Stop after planning. Do not implement.

For example, “add a task and see it after a restart” includes CLI input, validation, storage, output, and tests in one task. A later milestone could deliver “manage unfinished tasks” through add, list, and complete slices. Name the milestone's observable result and how to prove the whole result works.

Write for two readers