Roadmap

A repo can make one Markdown roadmap its execution source of record: a master census with one row per issue (status, wave, owner, skill routing, deps) that is the single place you go to pick the next thing to work on. Two cheap hooks keep it from rotting — a PreToolUse guard forces an issue-referencing commit to touch the roadmap (in-branch freshness), and a SessionStart nudge reports out-of-band drift (issues opened/closed via gh/web between sessions, which the commit guard structurally cannot see). This skill is the reconcile half: it repairs the drift the nudge reports, and stands the whole pattern up where it does not exist.

The guard enforces freshness by the issue-reference convention — a commit must touch the roadmap only when its message carries a #NN. That makes it convention-deep, not a guarantee: omitting #NN is both the documented infra-commit escape and a silent bypass of the guard. The SessionStart drift-nudge is the actual integrity net — it catches the drift the guard let through. Wire and trust both; the guard alone is a nudge, not a lock.