feature-roadmap

Name: feature-roadmap
Availability: InStock
Author: magnum6actual

Convert a GitHub issue into a structured feature roadmap with components and timeline.

Updated Aug 23, 2026

Search Tags:#planning #github #roadmap #interview #stakeholder-alignment #commander-intent #component-breakdown

Ready to run

npx skills add https://github.com/magnum6actual/dev-sop --skill feature-roadmap-magnum6actual

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-roadmap
Source: https://github.com/magnum6actual/dev-sop/tree/main/planning/skills/feature-roadmap
Command: npx skills add https://github.com/magnum6actual/dev-sop --skill feature-roadmap-magnum6actual

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform a GitHub issue into a clear, sponsor-validated plan by deriving Commander's Intent and a component-based roadmap, reducing ambiguity and alignment gaps during early planning.

Core Features & Use Cases

Interview-driven Commander's Intent capture
Break down work into independently deliverable components
Produce a consolidated Feature Roadmap with decisions, open questions, and timeline

Quick Start

Provide a GitHub issue URL and start the feature roadmap so the system generates a plan and components.

Frequently Asked Questions about feature-roadmap

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

FAQPage Schema

How do I create a structured feature roadmap from a GitHub issue?▼

A feature roadmap from a GitHub issue is generated by initiating sponsor interviews to derive Commander's Intent, breaking work into independently implementable components, and assembling a consolidated plan with open questions and timelines.

What is Commander's Intent in feature planning and when do I need it?▼

Commander's Intent is a sponsor-validated objective captured through interviews to reduce ambiguity and alignment gaps during early planning of standalone features or multi-component enhancements requiring CI-ready planning.

Can I break down a multi-component enhancement into independently deliverable parts?▼

Yes, you can break down multi-component enhancements into independently implementable parts by applying component breakdown to the GitHub issue, ensuring each segment is deliverable before assembling the final roadmap.

Does stakeholder alignment require an interview process for GitHub roadmap planning?▼

Stakeholder alignment for GitHub roadmap planning requires an interview process to capture Commander's Intent, validate sponsor objectives, and identify open questions before finalizing the structured feature roadmap.

What is the best way to document open questions and decisions for a feature roadmap?▼

The best way to document open questions and decisions for a feature roadmap is to consolidate them during the component breakdown phase, producing a CI-ready plan that explicitly lists outstanding decisions alongside delivery timelines.

When should I not use an interview-driven approach for feature roadmap generation?▼

You should not use an interview-driven approach for feature roadmap generation when the GitHub issue already contains fully defined components and sponsor requirements, making additional stakeholder interviews and Commander's Intent capture redundant.