From pm-planning
Creates structured, audience-calibrated roadmap presentations and narratives using Now/Next/Later framework for executives, stakeholders, and teams.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-planningThis skill uses the workspace's default tool permissions.
Build roadmaps that tell a strategy story — not just a list of features with dates. Every roadmap output is audience-calibrated: executives get outcomes, teams get specificity, customers get value.
Guides building product roadmaps with Now-Next-Later, outcome-based, theme, and timeline frameworks, plus prioritization and communication tactics for team alignment.
Builds outcome-focused product roadmaps with Now/Next/Later horizons, theme-based structure, Markdown templates, success metrics, and audience-specific views.
Builds strategic product roadmaps in Now/Next/Later format with quarterly themes, milestones, dependencies, resource allocation, and stakeholder templates for 3-12 month planning.
Share bugs, ideas, or general feedback.
Build roadmaps that tell a strategy story — not just a list of features with dates. Every roadmap output is audience-calibrated: executives get outcomes, teams get specificity, customers get value.
Always ask who the audience is before building:
| Audience | They care about | Format |
|---|---|---|
| Executive / Board | Business outcomes, revenue, risk, strategic alignment | Outcome-led, 3 columns (Now / Next / Later), no sprint detail |
| Cross-functional stakeholders | Dependencies, timelines, their team's involvement | Theme-based, with dependency callouts |
| Engineering team | Specificity, sequencing, technical constraints | Detailed, with epics and rough sizing |
| Customers / External | Value delivered, no internal detail | Benefits-focused, no dates — "Coming soon / In progress / Done" |
Standard output structure:
NOW (Current quarter — high confidence, committed)
NEXT (Following quarter — medium confidence, directional)
LATER (6–12 months — low confidence, aspirational)
⚠️ Never put specific dates on "Later" items. Use quarters or halves.
Every roadmap needs a narrative, not just a timeline. Structure it as:
Audience: [Executive / Team / Customer] Roadmap Owner: [PM Name] Last Updated: [Date] Confidence Level: Now = High | Next = Medium | Later = Low
Strategic Context:
[2–3 sentences: what company/product goal does this roadmap serve?]
Guiding Themes This Period:
NOW — [Quarter]
| Theme | Initiative | Outcome Expected | Team | Status |
|---|---|---|---|---|
| [Theme] | [What we're building] | [Metric it moves] | [Owner] | In Progress / Starting |
NEXT — [Quarter]
| Theme | Initiative | Hypothesis | Dependencies |
|---|---|---|---|
| [Theme] | [What we plan to build] | [If we build X, we expect Y] | [What needs to be true first] |
LATER — [H2 / Next Year]
| Theme | Strategic Bet | Why Later |
|---|---|---|
| [Theme] | [What we might build] | [What's blocking or uncertain] |
What We're NOT Building (and Why):
Success Metrics for This Roadmap:
| Metric | Now Target | End of Year Target |
|---|---|---|
| [Metric] | [X] | [Y] |