track-roadmap
Installation
SKILL.md
Track Roadmap
Maintain ROADMAP.md in the project root as a living, high-level feature plan, so decisions about what to build next are intentional, not reactive. Keep it to features (user-visible capabilities), not tasks — use track-session for task-level work. A healthy roadmap is 5-15 committed features readable in under 2 minutes.
Modes
| Mode | Command | Essence |
|---|---|---|
| Generate | /track-roadmap or generate |
Offer a codebase scan, ask 4 discovery questions, propose a feature list, then write ROADMAP.md after the user confirms |
| Update | /track-roadmap update |
Read current file, ask what changed (add/remove/complete/reword), apply after confirmation |
| Audit | /track-roadmap audit |
Scan code to mark each feature Done/In-Progress/Not-Started/Unclear, review relevance with the user, update |
| Brainstorm | /track-roadmap brainstorm |
Divergent ideation — explore directions before committing; viable ideas land in "Future Ideas" as status:idea |
| Resume | /track-roadmap resume |
Check session state, present remaining features, user picks one, hand off to /track-session |
Full per-mode procedures (discovery questions, brainstorm question banks, audit steps): reference/MODES.md.