
Roadmap Architect
Build quarterly product roadmaps balancing features, bugs, and technical debt
What You Can Do
Create comprehensive quarterly product roadmaps that balance feature development, bug fixes, and technical debt paydown across multiple teams. The skill maps explicit dependencies to surface blockers early, allocates finite resources realistically across work types, and assesses risk mitigation strategies for each initiative—then generates tailored communication templates for leadership reviews, customer updates, and team standups.
Features
RICE, Kano, or custom scoring systems to systematically rank competing initiatives
Visualize cross-team, cross-platform, and milestone dependencies to identify critical blockers
Balance capacity planning across features, bugs, and technical debt with realistic effort estimates
Evaluate risk factors and mitigation strategies for each major initiative, not just feature lists
Pre-built templates for leadership reviews, customer updates, and team standups tailored to audience
Calculate available engineering capacity by squad and allocate against competing demand
Justify what's cut or deferred with transparent reasoning tied to strategic priorities
Define quarterly milestones and link initiatives to measurable outcomes
Example Output
Example 1: Prioritized Initiative List
- Q2 Feature: API v3 Migration (RICE Score: 89) — Dependencies: Platform team, Infrastructure team; Risk: 2/5 (mitigation: parallel testing); Resource Allocation: 35% of Squad A capacity
- Q2 Debt: Legacy Auth Refactor (RICE Score: 72) — Enables: 3 future features; Risk: 3/5 (mitigation: feature-flagged rollout); Resource Allocation: 20% of Squad B capacity
Example 2: Leadership Communication ✓ Q2 focuses on foundational work: API migration (tier-1) and auth refactor (tier-2) enable 5 customer features in Q3 ✓ Feature requests A, B, C deferred to Q3 pending dependency completion ✓ Bug backlog reduced 25% through triage and resource priority
Example 3: Risk Registry
| Initiative | Risk | Probability | Impact | Mitigation |
|---|---|---|---|---|
| API v3 Migration | Third-party vendor delay | Medium | High | Partner kickoff Dec 1; contingency plan ready |
| Auth Refactor | Regression issues | Medium | Critical | QA review + staged rollout to 10% users |
| Customer Portal | Design-eng misalignment | Low | Medium | Weekly sync + signed-off wire-frames |
What's Included
- SKILL.md instruction file with strategic planning workflows and prioritization frameworks:
- Quarterly roadmap template with initiative tracking, dependency mapping, and capacity allocation:
- RICE/Kano prioritization scorecard for weighted comparison of competing work:
- Stakeholder communication suite including leadership review deck, customer-facing summary, and team standup talking points:
- Risk registry and mitigation template for assessing and mitigating initiative-level risks:
- Capacity planning worksheet to calculate squad availability and allocate across features, bugs, and debt:
- Dependency matrix for visualizing cross-team blockers and critical path items:
Who It's For
- Product Managers at mid-stage companies (15+ engineers) managing multi-squad or cross-functional complexity
- Head of Product or Director of Product overseeing multiple product lines or domains
- Platform or infrastructure PMs balancing feature velocity with technical debt paydown
- Technical Product Managers coordinating dependencies across distributed engineering teams
- Scaleup product leaders transitioning from ad-hoc planning to structured quarterly cycles
Best For
- Quarterly roadmap planning and prioritization across competing initiatives and work types
- Communicating strategic trade-offs (features vs. debt vs. bugs) to leadership and customers with transparent reasoning
- Mapping and surfacing cross-team dependencies to prevent project delays and blockers
- Resource allocation and capacity planning when engineering headcount is finite
- Risk assessment and mitigation planning for high-stakes or complex initiatives
- Stakeholder alignment workshops where teams or executives disagree on priorities







