Roadmap Planning
Turn goals, themes, and initiatives into a structured product roadmap — now/next/later or quarterly — with outcomes, rough sizing, dependencies, and confidence. Use when the user says "build a roadmap", "plan the quarter/half/year", "prioritize our initiatives", "what should we work on next", or needs to sequence work against objectives.
Install
$ agentstack add skill-janellecipriano-pm-skills-roadmap-planning ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-janellecipriano-pm-skills-roadmap-planning) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Roadmap Planning
Translate strategy into a sequenced, outcome-oriented roadmap that communicates what, why, and roughly when — without overpromising dates.
When to use
- Planning a quarter/half/year, or refreshing an existing roadmap.
- Prioritizing and sequencing a backlog of initiatives against goals.
Inputs to gather
- The objectives/strategy the roadmap serves (link to OKRs if they exist — see
okr-tracking). - Candidate initiatives/themes and any known sizing, dependencies, or hard dates.
- The audience and horizon (internal team vs. external; quarterly vs. now/next/later).
Process
- Anchor each initiative to an objective and a target outcome — drop work that maps to nothing.
- Choose a format: Now / Next / Later (theme-based, low date commitment) or timeline/quarterly (when dates matter).
- For each item: state the outcome/problem, rough size (T-shirt or weeks), confidence (H/M/L), and dependencies.
- Prioritize with a clear lens (impact vs. effort, RICE, or value vs. risk) and make the rationale visible.
- Sequence respecting dependencies and capacity (sanity-check against
capacity-planning). - Note assumptions and what would change the plan. Distinguish committed vs. exploratory.
Output format
Default to a Now/Next/Later table unless dates are required:
## Now (this quarter)
| Initiative | Objective | Outcome | Size | Confidence | Dependencies |
## Next
...
## Later
...Close with prioritization rationale and key assumptions/risks. Avoid precise dates for low-confidence items — use ranges or horizons.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: janellecipriano
- Source: janellecipriano/pm-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.