roadmapping

Sequences project candidates into a prioritized roadmap with ROI scoring, dependencies, and capacity allocation.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/Zhachory1/autopraxis --skill roadmapping-zhachory1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: roadmapping
Source: https://github.com/Zhachory1/autopraxis/tree/main/skills/roadmapping
Command: npx skills add https://github.com/Zhachory1/autopraxis --skill roadmapping-zhachory1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a pile of project candidates into a defensible, executable roadmap is hard: priorities get set by the loudest voice, dependencies are discovered too late, and capacity is assumed rather than planned. This Skill structures roadmap creation so tradeoffs across value, cost, risk, and strategy are explicit and leadership-ready. ## Core Features & Use Cases - Consistent ROI Scoring: Score candidates on value, cost, risk, confidence, strategic fit, and reversibility using a shared rubric. - Dependency and Capacity Planning: Map technical and organizational blockers, then allocate real team capacity across now/next/later horizons. - Council Review and Approval: Escalate high-stakes roadmaps through agent-fleet council lenses and package the result for leadership sign-off via a human approval gate. - Use Case: A PM has ten feature proposals from ideation and a two-team budget for next quarter. Use this Skill to score each proposal, resolve dependency conflicts, group work into themes, and produce an approval package with explicit tradeoffs. ## Quick Start Use the roadmapping skill to score these project candidates, map their dependencies, and build a now/next/later roadmap with a leadership approval package.

Frequently Asked Questions about roadmapping

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

FAQPage Schema
How do I create a product roadmap from a list of project ideas?▼

Score each candidate on value, cost, risk, confidence, and strategic fit using a shared rubric, then map dependencies and allocate real team capacity. Group the results into now/next/later horizons with themes that explain the strategy.

How do I prioritize projects with ROI scoring?▼

Use consistent criteria across all candidates: user and business value, effort, risk, reversibility, time sensitivity, and learning value. Record the rationale for each score so tradeoffs remain defensible during leadership review.

When should a roadmap go through council review?▼

Escalate to minimal or full council review for leadership commitments, multi-team capacity conflicts, platform bets, high opportunity cost, or disputed feasibility. Simple sequencing can skip council or use a single product or execution lens.

What is the difference between lite, default, and deep roadmap modes?▼

Lite handles small candidate sets with one scoring pass and no council. Default adds dependency and capacity loops with at most a minimal council. Deep allows full council and a complete approval package for high-risk or executive decisions.

Why do roadmaps fail even after careful planning?▼

Common failure modes include loudest-voice prioritization, unrealistic capacity assumptions, theme groupings based on org charts instead of outcomes, and vague approval asks. Fix these with shared scoring rubrics, dependency loops, and explicit leadership sign-off.