roadmap
Create a delivery roadmap that translates strategy into sequenced releases with milestones and dependencies.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install edwardmonteiro-aiskillinpractice-roadmap
Repository
Skill path: skills/delivery/roadmap
Create a delivery roadmap that translates strategy into sequenced releases with milestones and dependencies.
Open repositoryBest for
Primary workflow: Research & Ops.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: edwardmonteiro.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install roadmap into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/edwardmonteiro/Aiskillinpractice before adding roadmap to shared team environments
- Use roadmap for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: delivery.roadmap
phase: delivery
roles:
- Product Manager
- Program Manager
description: Create a delivery roadmap that translates strategy into sequenced releases with milestones and dependencies.
variables:
required:
- name: product
description: Product or program to roadmap.
- name: horizon
description: Time horizon (e.g., next 2 quarters).
optional:
- name: themes
description: Strategic themes or pillars to organize work.
- name: dependencies
description: Known cross-team or platform dependencies.
outputs:
- Timeline view of releases or increments with objectives and success metrics.
- Dependency and risk register with mitigation steps.
- Communication plan for stakeholders.
---
# Purpose
Provide a roadmap artifact that balances ambition with delivery realism and gives stakeholders visibility into upcoming milestones.
# Pre-run Checklist
- ✅ Align on strategic themes and investment mix with leadership.
- ✅ Confirm engineering capacity and velocity assumptions.
- ✅ Collect known dependencies, risks, and sequencing constraints.
# Invocation Guidance
```bash
codex run --skill delivery.roadmap \
--vars "product={{product}}" \
"horizon={{horizon}}" \
"themes={{themes}}" \
"dependencies={{dependencies}}"
```
# Recommended Input Attachments
- OKR drafts or strategic plans.
- Engineering capacity plans.
- Dependency tracker or RAID log.
# Claude Workflow Outline
1. Summarize product vision, horizon, and strategic themes.
2. Map releases or increments across the horizon with objectives, metrics, and target dates.
3. Identify dependencies, risks, and mitigation strategies per increment.
4. Provide stakeholder communication plan and review cadence.
5. Suggest visualization tips for slides or shared docs.
# Output Template
```
## Roadmap Overview — {{product}} ({{horizon}})
| Increment | Target Date | Theme | Objective | Success Metric | Key Dependencies |
| --- | --- | --- | --- | --- | --- |
## Risks & Mitigations
| Risk | Impact | Likelihood | Mitigation | Owner | Review Date |
| --- | --- | --- | --- | --- | --- |
## Stakeholder Communication Plan
- Audience:
- Channel:
- Cadence:
```
# Follow-up Actions
- Socialize roadmap with core stakeholders for feedback and sign-off.
- Integrate roadmap milestones into project tracking tools.
- Review and update monthly based on delivery progress and learnings.