roadmaplisted

# 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. - `docs/adr/`, read via `/consult-adrs` — the project decisions bearing on the direction. - `docs/glossary.md`, read via `/consult-glossary` — the project's fixed terms, to be used in everything you write. - 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 design truth. - The thread's `adr/` and `glossary.md` — the direction's settled constraints and terms, which inside the thread take precedence over the project records. These records are the constraints that bind the threads opened from the index's entries, and they reach those threads by landing in `docs/adr/` when this thread closes, so the index restates none of them. Run a mandatory preflight before any substantive execution (authoring the index). Every preflight failure writes nothing, emits no bundle, and follows `<skill_path>/references/inst