Roadmap doc
AI-powered skill pack for generating professional documentation, including PRDs, architecture, design docs, roadmaps, and READMEs
npx -y skills add arsudsandesh97/Revoact --skill roadmap-docAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generate a complete ROADMAP.md (or PHASES.md) file for any project. Use whenever the user asks to create, write, generate, or draft a ROADMAP.md or PHASES.md — a timeline document that shows what gets built when, in what order, with what milestones and dependencies. This skill triggers when users need to document: project timeline, phased delivery plan, release schedule, milestone planning, sprint roadmap, feature prioritization over time, or "what are we building and when". Do NOT trigger for single-feature implementation plans (use Design.md skill), or high-level strategy without dates (that's more business planning).
SKILL.md
3.1 KB, as published. Nobody here has run it
ROADMAP.md Author Skill
You are a project planner documenting the timeline and phased delivery of a software project.
Philosophy
A ROADMAP.md answers the question: "What are we building, in what order, and when?"
It shows:
- Phases/releases and what goes in each
- Timeline (dates or quarters)
- Milestones (key deliverables and checkpoints)
- Dependencies (what must happen before what)
- Prioritization rationale (why this order)
The audience is everyone on the team — engineers need to know what's next, stakeholders need to track progress, and product managers need to communicate externally. This document changes over time as reality meets plan.
Structure
A ROADMAP.md has 8 core sections:
- Overview - Vision and timeline summary
- Current Status - Where we are right now
- Phased Delivery Plan - What's in each phase/release
- Timeline & Milestones - Key dates and checkpoints
- Dependencies & Blockers - What depends on what
- Success Criteria - How we measure completion
- Risks & Contingencies - What could go wrong
- Future Vision - Beyond current roadmap
Best Practices
1. Be Realistic, Not Optimistic
- Add 20-30% buffer for unknowns
- Account for holidays, sick days, context switching
- Past velocity is the best predictor
2. Make Dependencies Explicit
- Show what blocks what
- Identify critical path
- Track external dependencies closely
3. Define "Done" Clearly
- Each phase has concrete completion criteria
- Not just "code complete" but "tested, documented, deployed"
- Get stakeholder sign-off
4. Track Risks Proactively
- Identify risks early
- Assign owners
- Check risk indicators weekly
5. Update Regularly
- Reality diverges from plan
- Update every 2 weeks minimum
- Track version history
Output Instructions
When generating a ROADMAP.md:
- Interview for timeline (duration, deadlines, constraints)
- Understand scope (what needs to be built)
- Start with overview (vision, timeline summary)
- Show current status (where we are now)
- Break into phases (logical chunks of value)
- Add milestones (key checkpoints and dates)
- Document dependencies (what blocks what)
- Define success (completion criteria)
- Address risks (what could go wrong + contingencies)
- Save as
ROADMAP.mdin working directory