cm-roadmap

Retires shipped issue seeds and repairs ROADMAP.md references after cycles land on main.

3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/PurdueRCAC/rcac-mcp --skill cm-roadmap-purduercac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cm-roadmap
Source: https://github.com/PurdueRCAC/rcac-mcp/tree/main/.agents/skills/cm-roadmap
Command: npx skills add https://github.com/PurdueRCAC/rcac-mcp --skill cm-roadmap-purduercac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a development cycle seeded from an issues/{slug}.md file ships to main, nothing retires the seed, so ROADMAP.md keeps advertising work that is already done. This Skill finds adopted seeds whose cycles have landed, deletes them after a human-confirmed preview, and repairs the drift a shipped cycle leaves behind. ## Core Features & Use Cases - Seed retirement: Finds every issues/{slug}.md carrying status: adopted:{slug}, confirms the cycle reached main via git ls-tree, and deletes the seed with its ROADMAP entry after a gated preview. - Drift repair: Fixes discharged Depends on: prerequisites, dangling cross-references, stale counts, and file:line citations in surviving seeds, .agents/ docs, and AGENTS.md. - Security-lane handling: Moves closed .security/ROADMAP.md entries to a Not scheduled section instead of deleting anything in the gitignored lane. - Use Case: After merging a feature cycle, run /cm-roadmap --dry-run to preview which seeds shipped, then confirm the retirement so the backlog reflects only work that remains. ## Quick Start Ask the assistant to run /cm-roadmap --dry-run to preview which adopted seeds have shipped and what roadmap cleanup would be performed.

Frequently Asked Questions about cm-roadmap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retire a shipped issue seed from ROADMAP.md?

Run /cm-roadmap with no arguments to consider every adopted seed, or pass a cycle slug to target one. The skill confirms the cycle landed on main via git ls-tree, previews the deletion and ROADMAP entry removal, and asks for confirmation before acting.

How do I preview roadmap cleanup without changing anything?

Use /cm-roadmap --dry-run to run the classification and preview steps only. It reports what would be retired and repaired but performs no deletions, edits, prompts, or commits. Use /cm-roadmap status to just classify seeds as landed, in-flight, or stale.

Does cm-roadmap delete files in the .security directory?

No. The .security lane is gitignored, so deletions there leave no history. Instead, the skill moves the entry to the Not scheduled section of .security/ROADMAP.md, updates .security/STATUS.md if present, and keeps the seed file.

What happens if a seed has an adopted marker but the cycle never shipped?

The skill checks whether a feature or fix branch exists. If the branch exists the seed is left alone as in-flight; if no branch exists the marker is stale, and the skill offers to reset status to shaped or unshaped rather than deleting anything.

Why does cm-roadmap refuse to run on a dirty git tree?

A clean tree prevents a retirement commit from being tangled with unrelated work. The one exception is a repair that made the skill itself loadable, which is committed separately as its own [harness] commit before the sweep continues.