roadmap-management
Skill0 starsChanged 6 months agoMITView on GitHub
Conduct Roadmap Management Track for product/project roadmaps. Triggers "create roadmap", "update roadmap", "review roadmap", "align stakeholders", "roadmap communication".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- insight68/Skillstheir own version, first seen Nov 8, 2026
- akachandan1/proofstacktheir own version, first seen Oct 11, 2026
- theseus-run/theseustheir own version, first seen May 16, 2026
- ichuan/skillstheir own version, first seen Feb 3, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- insight68/Skills★ 5same name
- ichuan/skills★ 1same name
- theseus-run/theseus★ 1same name
- akachandan1/proofstack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- plugin-v2/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- plugin-v2/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agents.mdcCursor rule
- agentic-security-reviewSkill
- arc42-baselineSkill
- caveman-commitSkill
- caveman-helpSkill
- caveman-reviewSkill
- cavemanSkill
- create-goalSkill
- design-twiceSkill
- discovery-sprintSkill
- domain-contextSkill
- github-project-setupSkill
- grillSkill
- improve-codebase-architectureSkill
- issue-breakdownSkill
- issue-draftSkill
- issue-pr-syncSkill
- new-adrSkill
- new-glossary-entrySkill
- orchestrateSkill
- portfolio-trackSkill
- product-pageSkill
- project-reviewSkill
- project-runSkill
- project-scaffoldingSkill
- quality-assuranceSkill
- quality-metricsSkill
- record-decisionSkill
- review-fixSkill
- sales-cycleSkill
- specorator-designSkill
- specorator-improvementSkill
- specorator-onboardSkill
- stock-takingSkill
- tackle-issueSkill
- tdd-cycleSkill
- token-budget-reviewSkill
- tracer-bulletSkill
- ubiquitous-languageSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 7 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Run when the user wants to:
- Distinctive: line 20
create or maintain a product roadmap
- Distinctive: line 26
Do not run when:
- Very specific: line 35
If $ARGUMENTS is list, print each roadmap slug, status, last_review, and next_review, then stop.
- Very specific: line 36
If no roadmap exists, ask for a roadmap slug and run /roadmap:start <slug>.
- Distinctive: line 37
If one active roadmap exists and no slug is provided, select it.
- Distinctive: line 38
If multiple active roadmaps exist, ask which one to manage.
- Very specific: line 46
After the command completes, read roadmaps/<slug>/roadmap-state.md and report status, next review, attention items, and decisions needed.
- Distinctive: line 50
Never promise dates or external commitments without explicit human approval.
- Very specific: line 51
Never edit roadmap artifacts directly from this skill.
- Very specific: line 52
Never modify specs/, projects/, portfolio/, or discovery/ artifacts.
- Distinctive: line 53
Keep stakeholder communication separated by audience.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Roadmap Management
You are the conductor for docs/roadmap-management-track.md. Your job is to pick the right /roadmap:* command, gather missing context, and hand off to the roadmap-manager agent. Do not do the agent's artifact work yourself.
Read first
docs/roadmap-management-track.mdmemory/constitution.md- Existing
roadmaps/*/roadmap-state.mdfiles, if any
When to run
Run when the user wants to:
- create or maintain a product roadmap
- connect product outcomes to project delivery plans
- prepare roadmap communication for leadership, customers, clients, or delivery teams
- review priorities, sequencing, dependencies, risks, or stakeholder alignment
- turn scattered feature/project signals into a readable roadmap
Do not run when:
- the user wants portfolio-level stop/start investment governance across many projects; recommend
portfolio-track - the user wants a single feature lifecycle; recommend
orchestrateor/spec:start - the user wants client engagement governance only; recommend
project-run
Procedure
- Intake gate. List
inputs/non-recursively before scoping. Surface every item via a singleAskUserQuestion: "I see N items ininputs/. Which are relevant for this roadmap work?" Common roadmap inputs: stakeholder briefs, prior roadmap exports, OKRs, customer feedback bundles, leadership memos. Ifinputs/is empty, print one line and proceed. Never auto-extract archives. Cite paths intoinputs/fromroadmap-board.mdandstakeholder-map.md. Full contract:docs/inputs-ingestion.md. Decision: ADR-0017. - Detect roadmaps by scanning for
roadmaps/*/roadmap-state.md. - If
$ARGUMENTSislist, print each roadmap slug, status, last_review, and next_review, then stop. - If no roadmap exists, ask for a roadmap slug and run
/roadmap:start <slug>. - If one active roadmap exists and no slug is provided, select it.
- If multiple active roadmaps exist, ask which one to manage.
- Recommend the command:
- no
roadmap-board.mdyet:/roadmap:shape - no
stakeholder-map.mdyet:/roadmap:align - user asks for an update, announcement, or meeting prep:
/roadmap:communicate next_reviewis today or earlier, or priorities changed:/roadmap:review- otherwise: ask whether to shape, align, communicate, or review
- no
- Dispatch the selected
/roadmap:*command. - After the command completes, read
roadmaps/<slug>/roadmap-state.mdand report status, next review, attention items, and decisions needed.
Constraints
- Never promise dates or external commitments without explicit human approval.
- Never edit roadmap artifacts directly from this skill; commands and the
roadmap-manageragent own writes. - Never modify
specs/,projects/,portfolio/, ordiscovery/artifacts. - Keep stakeholder communication separated by audience. Do not send customer/client language to delivery teams as if it were a delivery plan.
References
- Methodology:
docs/roadmap-management-track.md - Agent:
.claude/agents/roadmap-manager.md - Templates:
templates/roadmap-*-template.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.