roadmap

Solid

Review roadmap status, evidence freshness, blockers, and alignment

AI & Automation 476 stars 127 forks Updated yesterday NOASSERTION

Install

Quality Score: 83/100

Stars 20%

89

Recency 20%

100

Frontmatter 20%

70

Documentation 15%

100

Issue Health 10%

50

License 10%

100

Description 5%

100

Skill Content

## Purpose Produce a dated, source-backed roadmap review across the confirmed project cohort. Surface explicit blockers, alignment gaps, evidence freshness, and unknown status without inventing an aggregate health judgment. ## Usage - `/roadmap` — review the confirmed roadmap cohort - `/roadmap [pillar]` — filter by an exact configured pillar ## Evidence, authority, and recovery Treat the review as an evidence report, not a projection. - Use the canonical status source and status date from each project record. Record the path/ID, status date, and review as-of time. Filesystem modified time is only a discovery clue, never a replacement status date. - Cite source evidence for every status, blocker, milestone, pillar, alignment claim, and feedback item. If sources contradict, show both source dates and leave the field `Unknown`. - Unknown is distinct from blocked. Use `Blocked` only when the canonical source explicitly identifies an unresolved dependency preventing progress. - Define every denominator and disclose excluded projects. If the cohort or status is incomplete, report counts and coverage rather than a percentage or health score. - Never invent status, dates, blockers, dependencies, milestones, tags, feedback, counts, or health scores. - Keep analysis read-only. Preview requested changes, require explicit human authority,...

Details

Author: davekilleen
Repository: davekilleen/Dex
Created: 7 months ago
Last Updated: yesterday
Language: Python
License: NOASSERTION

Integrates with

Anthropic · AI

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

repo-to-roadmap

Analyze an entire software/product project and turn verified project truth into an evidence-based, dependency-aware, reusable roadmap. Use for first-time or delta whole-project baselines such as "analyze the whole repo/project", "what is left to build before target state", "create/update a roadmap from GitHub/Notion", "przeanalizuj całe repo", or "update the roadmap after recent changes". Inventory topology before searching, separate intent/presence/behavior/release/outcome truth, prove material absence instead of inferring it from search misses, expose coverage and contradictions, model capabilities/critical journeys, prioritize target blockers and gates, validate hard dependencies, and create immutable baseline/delta roadmap snapshots. Do not use for weekly sprint control, release-candidate GO/NO_GO gates, or "is build v1.2.3 ready to ship?" — use Product Operator or Release Readiness instead. Do not use as an implementation agent, narrow code review, or specialist security/SEO/CRO audit.

1 Updated 2 days ago

AI & Automation Listed

roadmap-plan

Adds, retargets, and reshapes roadmap items in `project/roadmap.md` per `spec/project/roadmap/` and `spec/project/mission/`. Invoke when the user asks to "add a roadmap item", "queue work for sprint N", "promote roadmap item to fine", "retarget R-3 to sprint 9", "flip MVP on this item", or equivalent German-language requests. Validates outcome IDs against `goals.md`, validates `target_sprint` against `project/sprints/`, enforces the lifecycle transitions declared in the roadmap and mission specs (including the asymmetric MVP-flag rule: `false→true` allowed before stabilisation, `true→false` forbidden after the item entered `status: active`), and refuses partial writes that would leave inconsistencies. Don't use to scaffold the roadmap from scratch (use `roadmap-init`) or to enforce the detail-level invariant (use `roadmap-refine`). Supports resume on re-invocation per `spec/claude/resumable-work/`.

0 Updated 1 weeks ago

AI & Automation Listed

roadmap

Use when the user asks what to work on next, wants to start the next thing, adds or tracks a feature, page, function or integration, initializes a project, asks what is left to build, wants work batched into parallel waves or phases, wants competing items prioritized or ranked, or the roadmap needs reconciling against reality.

0 Updated today