Roadmap planning

Skill orbty-ai/orbty-eazy/skills/roadmap-planning

Use when generating project roadmap - creates ROADMAP.md with milestones and timelineFrom its SKILL.md

Install

npx -y skills add orbty-ai/orbty-eazy --skill roadmap-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 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.

SKILL.md

3.5 KB, as published. Nobody here has run it

Roadmap Planning

Overview

Generate project roadmap with milestones, timeline, and high-level feature planning.

Announce at start: "I'm using the roadmap-planning skill to generate the roadmap."

Output

docs/planning/ROADMAP.md

Input Required

Project timeline (from PROJECT_CHARTER)
Major milestones
Feature priorities (from MVP_DEFINITION)
Dependencies and constraints

ROADMAP.md Template

# Roadmap: {Project Name}

## Overview
{1-2 sentence roadmap summary}

## Timeline

```mermaid
gantt
    title Project Roadmap
    dateFormat YYYY-MM-DD
    section Foundation
        Project Setup     :m1, 2026-01-01, 2w
        Core Architecture :m2, after m1, 2w
    section MVP
        Feature 1         :m3, after m2, 3w
        Feature 2         :m4, after m3, 2w
    section Launch
        Beta Testing      :m5, after m4, 2w
        Launch            :milestone, after m5, 0d

Milestones

M1: Foundation ({Target Date})

Goal: Project infrastructure ready

Deliverables:

Repository setup and CI/CD
Development environment
Core architecture in place
Database schema

Success Criteria:

All developers can build locally
CI pipeline passing
Basic deployment working

M2: Core Features ({Target Date})

Goal: Primary functionality complete

Deliverables:

{Feature 1}
{Feature 2}
{Feature 3}

Success Criteria:

Core user flows working
Tests passing
Performance acceptable

M3: MVP ({Target Date})

Goal: Minimum viable product ready

Deliverables:

All P0 features complete
User authentication
Core functionality end-to-end

Success Criteria:

All acceptance criteria met
Ready for beta users
Documentation complete

M4: Beta ({Target Date})

Goal: Beta testing complete

Deliverables:

Beta user feedback collected
Critical bugs fixed
Performance optimized

Success Criteria:

{N} beta users onboarded
NPS > {score}
No critical issues

M5: Launch ({Target Date})

Goal: Production launch

Deliverables:

Production deployment
Monitoring in place
Support processes ready

Success Criteria:

System stable
Users can sign up
Business metrics tracking

Feature Phases

Phase 1: Foundation

Feature	Priority	Status
{Feature}	P0	Planned

Phase 2: Core

Feature	Priority	Status
{Feature}	P0	Planned

Phase 3: Enhancement

Feature	Priority	Status
{Feature}	P1	Planned

Future (Backlog)

Feature	Priority	Notes
{Feature}	P2	Post-launch

Dependencies

flowchart LR
    A[Foundation] --> B[Core Features]
    B --> C[MVP]
    C --> D[Beta]
    D --> E[Launch]

Risks & Mitigation

Risk	Impact	Mitigation
{Risk}	High	{Strategy}

Key Dates

Date	Event
{Date}	Development Start
{Date}	MVP Complete
{Date}	Beta Start
{Date}	Launch

Created: {YYYY-MM-DD} Last Updated: {YYYY-MM-DD}


## Remember

- Align with PROJECT_CHARTER timeline
- Be realistic about estimates
- Include buffer for unknowns
- Mark critical path clearly
- Use mermaid for visualizations

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.