roadmap-planning

Plan and prioritize engineering roadmaps with prioritization frameworks and tradeoff analysis.

104|7|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/manager-dot-dev/manager-skills --skill roadmap-planning-manager-dot-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap-planning
Source: https://github.com/manager-dot-dev/manager-skills/tree/main/skills/roadmap-planning
Command: npx skills add https://github.com/manager-dot-dev/manager-skills --skill roadmap-planning-manager-dot-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Roadmap Planning helps engineering managers turn vague priorities into a focused, defensible plan by exposing tradeoffs, maintenance costs, and delivery risks so decisions are made with business impact in mind.

Core Features & Use Cases

  • Prioritization frameworks: delivers the 20% tech-debt framework with five common traps and fixes to make technical work visible and actionable.
  • Release and delivery checks: phased-release pressure-tests, the Always Green delivery method, sprint anti-patterns, and a critical-deadline playbook to improve predictability.
  • Cost and forecasting tools: maintenance-cost modeling, the Iron Law of Projects with reference-class forecasting, and guidance for framing technical work as business initiatives.
  • Stakeholder communication: concise messaging templates for PMs, leadership, and teams; tradeoff analysis and recommended next steps.
  • Use Cases: quarterly planning and OKR prioritization, negotiating tech-debt time with stakeholders, pressure-testing phased rollouts, and rescuing at-risk deadlines.

Quick Start

Ask the skill to prioritize this quarter's roadmap for a 12-person platform team balancing feature work, reliability improvements, and a backlog of technical debt.

Frequently Asked Questions about roadmap-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize technical debt against feature work during quarterly planning?

Roadmap planning uses a 20% tech-debt framework to make maintenance work visible and actionable, exposing tradeoffs between features, reliability, and debt so you can build a defensible quarterly plan with business impact in mind.

What's the best way to negotiate tech-debt time with stakeholders?

Stakeholder communication templates and tradeoff analysis help you frame technical work as business initiatives. You get concise messaging for PMs and leadership that highlights maintenance costs and delivery risks to justify prioritization decisions.

How do I pressure-test a phased release schedule for predictability?

Phased-release pressure-tests and the Always Green delivery method evaluate rollout risks to improve predictability. The skill applies sprint anti-patterns and a critical-deadline playbook to identify delivery bottlenecks before they threaten your release timeline.

Can I use this for capacity planning and OKR setting with a large platform team?

Yes, the skill supports capacity planning and OKR prioritization for teams of various sizes. It integrates with engineering manager context files to provide grounded recommendations tailored to your specific team structure and capacity constraints.

How does maintenance-cost modeling work for roadmap forecasting?

Maintenance-cost modeling applies the Iron Law of Projects with reference-class forecasting to estimate ongoing support burdens. This cost forecast exposes hidden delivery risks and helps you balance new feature work against required platform reliability improvements.

What should I do to rescue an at-risk engineering deadline?

Use the critical-deadline playbook to triage at-risk releases by applying tradeoff analysis and phased-release pressure-tests. This identifies which deliverables can slip without impacting core business objectives and generates recommended next steps for stakeholders.