Plans, sequential Epics and parallel Epics
Type /plan and describe the work. The planner breaks it into leaf tasks, each with a file_scope and a runnable acceptance command. The plan type is chosen at /plan and stays fixed for the whole session.
Standard PlanOne plan whose phases run in order on the main worktree. Good for small jobs.
Sequential EpicSeveral child plans in a chain; each plan reads the results of the one before it.
Parallel EpicChild plans run at once in their own worktrees, and plan-99 merges them.
How a parallel Epic runs
- Plan: the Epic is split into child plans, each tied to its own repo.
- Foundation: plan-01 runs first to lock the contract (types, schema, API) the later plans rely on.
- Parallel: child plans run at the same time, each as a lane in its own git worktree. Parallel tasks have non-overlapping scopes, so they don't compete for locks. Phases within a lane continue on their own.
- Merge: plan-99 combines the lanes, AI resolves conflicts and runs E2E. When two plans contradict each other, it asks you.
- PR: open a PR and review agent by agent.
Questions have no timeoutWhen a plan needs your decision, that lane stops and waits until you answer, even if you've left your machine. Lanes that don't depend on it keep running. The Stop all button stops every lane after asking for confirmation and keeps the code written so far.