roadmaplisted

# The roadmap `record.roadmap` holds **milestones**, and inside each, the **blocks** that make it up and the order they happen in. This skill is its sole writer. A **milestone is the unit that ships.** It carries the version it intends to ship as, and marking one completed is the only thing in this workflow that authorises a tag. That intended version is a *plan*: `--release` confirms the number and is the only thing that turns it into a tag or a changelog entry. It is **not** a task list and **not** a place for design arguments. The checklist is `record.todo` and the reasoning is `record.decisions`, both `--todo`/`--log`'s. Keeping those apart is the whole reason the records were split; a task or an argument landing here is the failure this separation exists to avoid. **Project facts come from `.claude/workflow.json`**: `record.roadmap`, `record.todo`, `record.openDecisions`, `record.decisionsIndex`, `record.audits`, and `agents.roadmap`. Without a manifest, fall back to `ROADMAP.md` and say so. Who owns what is [`~/.claude/workflow/ownership.md`](../../workflow/ownership.md); what each record holds is [`record-contract.md`](../../workflow/record-contract.md). ## Why this is a skill and not only the agent Same split as `--release` and for the same reason. The agent named in `agents.roadmap` does the reading — the roadmap, the backlog, the decision index, the audit log, the git history — and returns a proposal. That reading is thousands of tokens and belongs in a conte