Roadmap

Turn a settled direction into a durable map. You read the thread's authoritative inputs, decide how the direction divides into entries that can each be picked up on their own, and write one project-level index file under .work/roadmaps/. Writing that file is where you stop — do not stage, commit, or push.

The index is a map, not a plan: it records where the direction is going and what gets there, at the coarsest grain that still tells someone what to pick up next.

Inputs

Gather all of these before drafting; everything below works from what you gather here.

• The project's AGENTS.md, when the file exists — the project's standing guidance for agents working in it.
• docs/glossary.md, when the file exists — the project's fixed terms, to be used in everything you write.
• docs/adr/ and docs/pdr/, read via /consult-decisions — the project decisions bearing on the direction.
• The roadmap entry named by the seed frontmatter's roadmap mapping, when the seed carries one — the entry this thread answers: its sketch, its scope boundary and its planned behavior, found as the heading whose text is roadmap.entry in the index at roadmap.path.
• The thread's seed.md — why the thread exists and what the direction is meant to reach.
• The thread's spec.md, when the file exists — the direction's spec.
• The thread's delta/, when present — the direction's settled records, glossary terms and agents-file changes as the thread drafted them, which inside the thread take precedence over the project layer. They reach the project layer when the thread closes, so the index restates none of them; what they leave unbuilt is what the entries carry as planned behavior.

Any other thread is history: it records how its own work was understood at the time, not what holds now, so do not read it unless the user or this thread's seed names it.