To Roadmap

Break a large effort into sequential stages, checked into docs/roadmaps/<name>/. A roadmap is to stages what a /to-tasks plan is to tasks, one level up: each stage later becomes exactly one /to-tasks feature (one branch, one review unit), started via /next-stage.

Asking questions

Whenever you put a question to the user — the quiz in step 3, or an ad-hoc question when something is unclear or has drifted — ask it and wait for their answer before carrying on.

Why briefs, not task files

The planning session's context is richest now and evaporates at the next /clear — but detailed task slicing goes stale as earlier stages land and the codebase moves. So a roadmap splits the difference:

• Capture now: the decisions in force and their why (expensive to reconstruct later), stage boundaries, ordering, and a provisional task chunking per stage.
• Defer to stage start: final task slicing, grounded against the codebase as it exists then. /to-tasks does that re-grounding when handed a stage brief.

Process

1. Gather context