Menu
Create an rdm roadmap with phases for a topic
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Rate each phase's difficulty and assign a model tier from its body
Act on document reviews requesting changes — work each comment and drive the review to addressed
Review the plan for an rdm roadmap, phase, or task before implementation begins
Implement an rdm roadmap phase or work on an rdm task — plan, execute, then finalize into needs-review for rdm-review
Run a batched backlog grooming pass over rdm's stale/duplicate/tag-cluster/archivable signals and emit a reviewable, propose-only plan of exact rdm commands — no mutations
Drive one named rdm roadmap from not-started to reviewed autonomously — pick the next actionable phase, estimate it, dispatch it on its model tier, interpret the outcome, and advance — batching decisions and blockers instead of interrupting
| name | rdm-roadmap |
| description | Create an rdm roadmap with phases for a topic |
| allowed-tools | ["Read","Bash","Glob","Grep"] |
Create an rdm roadmap with phases for the topic described in $ARGUMENTS.
IMPORTANT: This is the rdm source repo. Always run cargo build first, then use ./target/debug/rdm — never bare rdm.
Run cargo build to ensure the binary is up to date.
Explore the codebase to understand the current state relevant to $ARGUMENTS. Read key files, search for related code, and build context.
Design phases that break the work into independently deliverable increments. Each phase should produce a working, testable result.
Create the roadmap: ./target/debug/rdm roadmap create <slug> --title "Title" --body "Summary." --tags <tag1>,<tag2> --no-edit --project rdm
Create each phase with context, steps, and acceptance criteria in the body:
./target/debug/rdm phase create <slug> --title "Phase title" --number <n> --tags <tag> --no-edit --roadmap <roadmap-slug> --project rdm <<'EOF'
## Context
Why this phase exists and what it builds on.
## Steps
1. First step
2. Second step
## Acceptance Criteria
- [ ] Criterion one
- [ ] Criterion two
EOF
Pass a bare slug like hook-commit-bug — rdm prepends phase-<number>- automatically. Do not include phase-N- in the slug; you'll get a doubled prefix like phase-1-phase-1-hook-commit-bug.
Land the batch: ./target/debug/rdm commit -m "feat(plan): add <roadmap> roadmap" — one commit for the roadmap and all its phases.
Verify the roadmap looks correct: ./target/debug/rdm roadmap show <slug> --project rdm
add-caching, migrate-auth)auth, tech-debt); prefer existing tags — check with
./target/debug/rdm search "" --tag <candidate> --project rdm before
inventing a new one.plan_review is enabled, every roadmap and phase created above already
carries a needs-plan-review tag — leave it in place, don't strip it by
hand. It's cleared by the rdm-plan-review skill (run manually or via the
Stop hook/extension) once the plan passes review.