Forge-Roadmap-Planning

Translates strategy and evaluation findings into themed, milestone-based product roadmaps with recorded assumptions.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-roadmap-planning-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Roadmap-Planning
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/01-Product/Forge-Roadmap-Planning
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-roadmap-planning-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Strategic direction, evaluation findings, and improvement actions often remain disconnected, leaving prioritisation decisions ad hoc and inconsistent. This Skill consolidates those inputs into a sequenced, outcome-oriented roadmap so that ordering decisions happen inside a coherent forward plan. ## Core Features & Use Cases - Theme Formation: Groups candidate work into outcome-oriented themes rather than feature lists, each stating the outcome it pursues. - Milestone Sequencing: Orders themes into milestones based on value, risk register signals, dependencies, and capacity assumptions. - Assumption Tracking: Records the assumptions each theme rests on, with explicit validation points, and triggers re-planning when assumptions are invalidated. - Use Case: During an Improve phase, a Product Owner feeds product evaluation findings and retrospective actions into this Skill to re-plan the roadmap, producing an updated milestone plan that flows into prioritisation and backlog refinement. ## Quick Start Ask the AI to consolidate the current strategy, evaluation findings, and risk register into a themed roadmap with sequenced milestones and recorded assumptions.

Frequently Asked Questions about Forge-Roadmap-Planning

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

FAQPage Schema
How do I create a product roadmap from strategy and evaluation findings?▼

Consolidate strategic direction, product evaluation findings, retrospective actions, and risk register signals, then group candidate work into outcome-oriented themes. Sequence those themes into milestones by value, risk, dependencies, and capacity assumptions, recording each theme's assumptions and validation points.

What is the difference between roadmap planning and backlog prioritisation?▼

Roadmap planning operates above individual work items, grouping work into themes and sequencing them into milestones. Prioritisation orders specific items within that roadmap frame, and backlog refinement details near-term milestone items for execution.

When should a product roadmap be re-planned?▼

Re-plan when assumptions are invalidated, capacity shifts, strategy or constraints materially change, or evaluation findings demand it. Re-planning should be triggered by signals rather than calendar habit, with each roadmap change recorded as a decision.

What inputs are needed for outcome-oriented roadmap planning?▼

Required inputs include strategic direction and Product Owner objectives, product evaluation findings, retrospective actions, the risk assessment register, technical debt signals, and current capacity and dependency information.

When should I not use roadmap planning?▼

Do not use it to rank or sequence individual work items, which belongs to prioritisation, or to detail items for execution, which belongs to backlog refinement. It also does not set business strategy, which remains the Product Owner's responsibility.