deliveryroadmap

edwardmonteiro's avatarfrom edwardmonteiro

Create a delivery roadmap that translates strategy into sequenced releases with milestones and dependencies.

⭐0stars🔀1forks📁View on GitHub🕐Updated Dec 23, 2025

When & Why to Use This Skill

This Claude skill empowers Product and Program Managers to bridge the gap between high-level strategy and execution. By automating the creation of sequenced delivery roadmaps, it provides a structured framework for defining milestones, managing cross-team dependencies, and establishing clear communication plans, ensuring project transparency and delivery realism.

Use Cases

  • Strategic Alignment: Translating annual product themes and OKRs into a concrete, time-bound release schedule for the upcoming quarters.
  • Dependency Mapping: Identifying and documenting critical technical or resource dependencies between multiple teams to prevent bottlenecks and ensure smooth sequencing.
  • Risk Management: Proactively identifying delivery risks and creating structured mitigation strategies to maintain project momentum and manage stakeholder expectations.
  • Stakeholder Communication: Generating professional roadmap overviews and communication plans tailored for executive reviews and cross-functional alignment.
namedelivery.roadmap
phasedelivery
descriptionKnown cross-team or platform dependencies.
- namedependencies

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

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.