roadmap
Skill9 starsChanged 7 months agoApache-2.0View on GitHub
Visual roadmap snapshot — theme progress, milestones, velocity. Zero new infra (Linear MCP + velocity.json).
48 other projects use a version of this.
Adopted by
Most recently taken up by
- gopalparashar421/agent-skillstheir own version, first seen Nov 8, 2026
- dirien/yet-another-agent-harnesstheir own version, first seen Nov 8, 2026
- Ovich/charrettetheir own version, first seen Nov 7, 2026
- ryanmoelter/plumetheir own version, first seen Nov 4, 2026
- eyssette/js-templatetheir own version, first seen Nov 1, 2026
- danielcherubini/skillstheir own version, first seen Nov 1, 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 versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 48
- 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★ 150same name
- facebookresearch/autoform-bot★ 136same name
- Mehdibargach/claude-code-pm-skills★ 97same name
- joshuadavidthomas/agent-skills★ 49same name
- spmtitsolution/OpenBA-Kit★ 38same name
38 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 repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cli/CLAUDE.mdCLAUDE.md
- control-plane-api/CLAUDE.mdCLAUDE.md
- control-plane-ui/CLAUDE.mdCLAUDE.md
- e2e/CLAUDE.mdCLAUDE.md
- portal/CLAUDE.mdCLAUDE.md
- stoa-gateway/CLAUDE.mdCLAUDE.md
- analyticsSkill
- cartoSkill
- ci-debugSkill
- ci-fixSkill
- competitive-watchSkill
- councilSkill
- decomposeSkill
- extractSkill
- fill-cycleSkill
- generate-backlogSkill
- impactSkill
- memory-consolidateSkill
- monitor-cdSkill
- parallel-reviewSkill
- pr-guardianSkill
- rewriteSkill
- spec-drivenSkill
- sync-planSkill
- verify-megaSkill
The file
Files
Roadmap Visibility — Strategic Progress Snapshot
Display or generate STOA Platform roadmap aligned with Linear roadmap:* labels and milestones.
Target: $ARGUMENTS
Step 0: Determine Mode
| Argument | Mode | Description | MCP Budget |
| (empty) | Snapshot | Display roadmap in terminal (read-only) | 7-8 reads |
--update | Update | Regenerate ROADMAP.md at repo root | 7-8 reads + 1 file write |
--milestones | Milestones | Show milestone timeline with days remaining | 1 MCP read |
Step 1: Fetch Theme Progress (5 queries)
Query each roadmap:* label to count Done vs Total issues:
For each theme in [gateway, platform, dx, security, community, observability]:
linear.list_issues(
team: "<LINEAR_TEAM_ID>",
labels: ["roadmap:<theme>"],
first: 250
)
Count: total issues, done issues (status = "Done" or "Canceled")Label IDs (cached)
| Theme | Label | ID |
| Gateway | roadmap:gateway | <LABEL_ID_ROADMAP_GATEWAY> |
| Platform | roadmap:platform | <LABEL_ID_ROADMAP_PLATFORM> |
| DX | roadmap:dx | <LABEL_ID_ROADMAP_DX> |
| Security | roadmap:security | <LABEL_ID_ROADMAP_SECURITY> |
| Community | roadmap:community | <LABEL_ID_ROADMAP_COMMUNITY> |
| Observability | roadmap:observability | <LABEL_ID_ROADMAP_OBSERVABILITY> |
Important: Theme percentages depend on roadmap:* labels being applied to issues. If a theme shows 0/0, it means no issues have been tagged with that label yet. Run a backfill session to tag historical issues.
Step 2: Fetch Milestones (1 query)
linear.list_milestones(project: "<LINEAR_PROJECT_ID>")Milestone IDs (cached)
| Milestone | ID | Target Date |
| Demo MVP Ready | <MILESTONE_DEMO_MVP> | 2026-02-17 |
| Demo Day | <MILESTONE_DEMO_DAY> | 2026-03-17 |
| Private Beta | <MILESTONE_PRIVATE_BETA> | 2026-04-30 |
| RC1 Public Beta | <MILESTONE_RC1> | 2026-06-30 |
| v1.0 GA | <MILESTONE_V1_GA> | 2026-07-31 |
For each milestone, compute:
- Status: Done (target date < today AND progress 100%), Active (target date > today), Overdue (target date < today AND progress < 100%)
- Days remaining:
(target_date - today).days(negative = overdue)
Step 3: Read Velocity (file read)
Read .claude/state/velocity.json
Extract:
rolling_avg_3.pts_per_dayrolling_avg_3.issues_per_dayrolling_avg_3.completion_pct- Last cycle data for "Current Cycle" section
Step 4: Fetch Current Cycle (1 query)
linear.list_cycles(teamId: "<LINEAR_TEAM_ID>", type: "current")Extract: cycle name, scope (total pts), done (pts), issue count.
Step 5: Render Output
Snapshot Mode (default) — Terminal Display
STOA Roadmap — YYYY-MM-DD
══════════════════════════
Vision: European Agent Gateway — v1.0 Jul 31, 2026
MILESTONES
✅ Feb 17 Demo MVP Ready
🔄 Mar 17 Demo Day ..................... NN days
⬜ Apr 30 Private Beta (3 partners) .... NN days
⬜ Jun 30 RC1 (public beta) ............ NN days
⬜ Jul 31 v1.0 GA ...................... NN days
THEMES Done/Total Progress
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Gateway [████████████████░░░░] XX% NN/NN
Platform [██████████████░░░░░░] XX% NN/NN
DX [████████████░░░░░░░░] XX% NN/NN
Security [████████████████░░░░] XX% NN/NN
Community [██████████░░░░░░░░░░] XX% NN/NN
Observability [██████████████░░░░░░] XX% NN/NN
VELOCITY (rolling 3-cycle avg)
XX.X pts/day | X.X issues/day | XXX% completion
Capacity (7d): XXX pts target
CURRENT CYCLE — Cycle NN
Committed: XX pts | Done: YY pts | ZZ%Progress Bar Generation
For each theme, generate a 20-char bar:
filled = round(percentage / 100 * 20)
bar = "█" * filled + "░" * (20 - filled)
output = f"[{bar}] {percentage}%"Update Mode (--update) — Write ROADMAP.md
Generate the same content as snapshot but write to ROADMAP.md at repo root.
Add header:
<!-- Auto-generated by /roadmap --update. Do not edit manually. -->
<!-- Last updated: YYYY-MM-DD -->Milestones Mode (--milestones) — Timeline Only
Display only the milestones section with more detail:
STOA Platform — Milestone Timeline
═══════════════════════════════════
✅ 2026-02-17 Demo MVP Ready DONE
🔄 2026-03-17 Demo Day NN days remaining
⬜ 2026-04-30 Private Beta NN days remaining
⬜ 2026-06-30 RC1 Public Beta NN days remaining
⬜ 2026-07-31 v1.0 GA NN days remaining
Total progress: N/5 milestones complete
Next milestone: <name> in NN daysRules
- Read-only by default — snapshot mode makes zero writes (Linear or files)
- MCP budget: max 8 calls per snapshot (5 theme queries + 1 milestones + 1 cycles + 1 velocity file)
- No
--push-metricsin v1 — Pushgateway integration deferred to follow-up - Theme percentages are label-dependent — if labels aren't applied, percentages will be 0/0
- velocity.json is the source of truth for velocity data (maintained by
/sync-plan) - ROADMAP.md is generated — never edit manually (overwritten by
--update) - Milestones are managed on Linear — use Linear UI or MCP to update dates/status
- No auto-commit — show output to user, let them decide whether to commit
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.

