# Plan Product Roadmaps with Sprint Capacity

Roadmap plans often fail when epics, milestones, and team capacity are estimated separately. This skill helps Claude, Codex, and Claude Code create practical sprint and milestone plans.

## Install

```bash
npx skillstore add andresnaza/roadmap-planning-expert
```

## Metadata

- - Slug: andresnaza-roadmap-planning-expert
- - Version: 1.0.0
- - Author: AndresNaza
- - GitHub username: AndresNaza
- - License: MIT
- - Repository: https://github.com/AndresNaza/claude-plugins/tree/main/roadmap-planner/skills/roadmap-planning
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: safe
- - Quality score: 80
- - Quality tier: silver
- - Public page: https://skillstore.pages.dev/skills/andresnaza-roadmap-planning-expert
- - Manifest: https://skillstore.pages.dev/api/skills/andresnaza-roadmap-planning-expert/manifest

## Capabilities

- Explains a roadmap model based on quarters, epics, milestones, and sprints.
- Applies a capacity model of 20 points per developer per two-week sprint.
- Guides collaborative planning for quarters, epics, and sprint allocation.
- Defines when to split milestones larger than 25 points.
- Documents roadmap file locations under a .roadmap directory.
- Describes ClickUp sync concepts for epics, milestones, and status updates.

## Use Cases

- Plan a Quarterly Roadmap: Convert product goals into epics, milestone sizes, and sprint placement for a six-sprint quarter.
- Estimate Delivery Capacity: Calculate whether planned milestones fit available team capacity with a practical buffer.
- Prepare Sprint Scope: Select milestones for an upcoming sprint based on team availability and known work size.

## Prompt Templates

### Create a Basic Roadmap

```
Help me plan a quarter for this product goal. Ask me for missing details, then propose epics, milestones, estimates, and sprint allocation.
```

### Break an Epic into Milestones

```
Break this epic into two to four milestones. Estimate each milestone in points and explain which milestones should be split.
```

### Check Sprint Capacity

```
Review this sprint plan against our team capacity. Use a 15 percent buffer and identify which milestones should move.
```

### Build a Roadmap and Sync Plan

```
Create a quarterly roadmap with epics, milestones, sprint placement, dates, and a ClickUp sync mapping for each planned work item.
```

## Limitations

- Does not include executable automation or scripts.
- Does not track pull requests, QA status, or detailed issue execution.
- Assumes a two-week sprint and a 20-point developer capacity model.
- ClickUp syncing depends on separate commands outside this skill.

## Best Practices

- Provide team size, sprint length, and planned absences before capacity planning.
- Keep milestones coarse enough for roadmap planning but specific enough to assign to sprints.
- Review milestone estimates with the delivery team before committing dates.

## Anti Patterns

- Do not use the skill as a replacement for detailed issue tracking.
- Do not force milestones larger than 25 points into a single sprint.
- Do not plan a full quarter without reserving buffer for unexpected work.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T08:57:08.212\+00:00
- - Summary: Static analysis reported external command and weak cryptography patterns, but review found these are false positives in Markdown guidance. The flagged lines contain code fences, inline file names, and slash-command documentation, with no executable scripts, network calls, prompt injection, or secret access found.

## Stats

- - Views: 195
- - Downloads: 5
- - Favorites: 0
- - Popularity score: 0