roadmap
Skill1 starsChanged 17 days agoMITView on GitHub
Plan a goal bigger than one wayfinder map as a roadmap: one issue with a final deliverable, done-when checks and stages, kept in a GitHub milestone. Each stage gets its own map, then spec, tickets and code. Charts the roadmap, starts and ends stages, and closes it when every check passes. User-invoked.
51 other projects use a version of this.
Adopted by
Most recently taken up by
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- GravionLabs/skillstheir own version, first seen Nov 15, 2026
- Palatine-Labs/conisotheir own version, first seen Nov 15, 2026
- iuliandita/skillstheir own version, first seen Nov 15, 2026
- yarikleto/claude-teacher-plugintheir own version, first seen Nov 14, 2026
- ryanmoelter/plumetheir own version, first seen Nov 12, 2026
Used with
Projects with it also use sequence, stakeholder-update and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GTMifySkillsequence
Build a multi-channel outreach cadence (email + LinkedIn + phone) for a target persona or named prospect. Use when the user says 'build a sequence', 'outreach cadence', 'multi-touch sequence', 'multi-channel cadence', 'follow-up sequence', or needs a coordinated multi-channel play. Do NOT use for single cold emails — use cold-email instead.
Also in 3 projects that use this
AnthropicSkillstakeholder-update
Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.
Also in 3 projects that use this
EpistatesSkillstrategy
Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.
Also in 3 projects that use this
ArvorCoSkillspecify
Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.
Also in 3 projects that use this
GitHubSkillprd
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
Also in 7 projects that use this
michalattSkillchallenge
Pressure-test plans, decisions, and directions by picking and answering the most relevant challenge questions for the current conversation
Also in 3 projects that use this
Other versions51 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 51
- cloudposse/atmos★ 1.4ksame name
- me2resh/apexyard★ 542same name
- andreaskelm/pm-brain★ 235same name
- genkovich/sdd★ 187same name
- YougLin-dev/Aha-Loop★ 181same name
- Ovid/paad★ 154same name
- facebookresearch/autoform-bot★ 143same name
- Mehdibargach/claude-code-pm-skills★ 97same name
- joshuadavidthomas/agent-skills★ 49same name
- spmtitsolution/OpenBA-Kit★ 38same name
41 more not listed
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 repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- broSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- hq-modeSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- ketchupSkill
- lab-containersSkill
- lab-edisonSkill
- lab-hpcSkill
- lab-jupyterSkill
- lab-presentationSkill
- lab-setupSkill
- prototypeSkill
- prSkill
- researchSkill
- retroSkill
- setup-matt-pocock-skillsSkill
- tddSkill
- teachSkill
- technical-writingSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- unslopSkill
- unslop-zhSkill
- wait-whatSkill
- wayfinderSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Write it from references/roadmap-issue.md, which also holds the tracker commands.
- Distinctive: line 29
Every map here is a wayfinder map: read wayfinder before charting one.
- Distinctive: line 47
File it: Create the roadmap issue and its milestone, and put the roadmap in it.
- Distinctive: line 55
Start a stage: when its After column allows.
- Distinctive: line 60
End a stage: when its ends-when test holds.
- Distinctive: line 64
Close the roadmap: when every done-when check has passed, each with its evidence comment.
“Common” is measured: kept by at least 6 in 10 of the 44 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
A roadmap is a map of maps. A goal arrives that one wayfinder map cannot hold: it needs several specs, and its stages wait on each other. The roadmap fixes the goal and the stages only. Every design choice stays open until that stage's own map. When every stage has landed, the goal is met.
Three pieces, all on the repo's issue tracker:
- Background: a GitHub Discussion with the goal in the user's words and what exists today.
- The roadmap issue, titled
<goal>: stages: the final deliverable with numbered done-when checks, and a stage table giving each stage an outcome and an ends-when test. Write it from references/roadmap-issue.md, which also holds the tracker commands. - Stage maps: one wayfinder map per stage, each a sub-issue of the roadmap. The roadmap, its
stage maps, and each stage's spec, tickets and pull requests sit in one GitHub milestone,
M<n>: <goal>. A map's decision tickets stay out of it.
Every map here is a wayfinder map: read wayfinder before charting one. Its tickets, fog and resolution rules hold unchanged.
Chart the roadmap
The user invokes with a goal.
- Write the goal down. Find or post its Discussion. Done when the Discussion is linked.
- Chart the roadmap's map: a wayfinder map whose destination is the roadmap issue. Its Notes say: each ticket settles only what placing a stage needs, and the rest goes to that stage's map; grilling tickets may be taken in waves, several per session. Its last ticket is "Draft the roadmap". Skip this map when the Discussion already makes the stages clear.
- Ask the scale question. A goal over a large set climbs in rungs: 1% (early proof), 10% (scale proof), 100% (the full run). The roadmap does one rung, and its last check is that the next rung can be planned from measured cost, time and failure rate.
- Draft on a review page. Publish the draft as an HTML review page: the stages as a diagram, the done-when checks, one section per stage, the calls you made and the questions left. Done when the user agrees with the page.
- File it. Create the roadmap issue and its milestone, and put the roadmap in it. Place every item still open on the map under the stage that meets it. Close "Draft the roadmap" and the map, with the roadmap in its Decisions so far.
Work the roadmap
The user invokes with the roadmap. Load its body and comments, not the stage maps' tickets.
- Start a stage when its After column allows. Chart its wayfinder map. Its destination is usually a build spec for this stage, with the stage's ends-when test as the spec's acceptance. Its Notes carry what earlier stages measured and the roadmap's open items for this stage. Make the map a sub-issue of the roadmap, add it to the milestone, and comment on the roadmap that the stage has started, naming its map.
- End a stage when its ends-when test holds. Comment on the roadmap with the evidence (what ran, against what, the numbers), the follow-ups, and every done-when check's status in a table.
- Change the plan by editing the roadmap body: a stage added, reordered or split, a check reworded. Say what changed and why in a comment.
- Close the roadmap when every done-when check has passed, each with its evidence comment. Close the milestone with it.
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.

