create-roadmap

Creates a project roadmap sequencing initiatives across Now/Next/Later horizons aligned to goals.

11|1|Updated Jul 25, 2025
Ready to run
npx skills add https://github.com/tomzx/agents --skill create-roadmap-tomzx
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: create-roadmap
Source: https://github.com/tomzx/agents/tree/main/skills/create-roadmap
Command: npx skills add https://github.com/tomzx/agents --skill create-roadmap-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Without a roadmap, prioritization is ad hoc: every issue is ranked in isolation, sequencing constraints are invisible, and there is no shared view of what is committed versus exploratory. This Skill produces a single context-level roadmap artifact that ties initiatives to objectives so downstream prioritization has a strategic plan to follow. ## Core Features & Use Cases - Horizon-Based Sequencing: Groups work into initiatives placed across Now, Next, and Later horizons with confidence falling toward Later, plus an explicit Not Now section with promotion conditions. - Goal Alignment: Anchors every initiative to an objective in goals.md with a hypothesis, owner, dependencies, and a success signal tied to a key result or KPI. - Timeline Visualization: Renders a Mermaid Gantt chart mapping initiatives and dependencies across horizons, anchored to the current period. - Use Case: A product team with a growing backlog needs to decide what to build next quarter. The Skill inventories open issues via ghx, groups them into initiatives, and writes .sdlc/context/roadmap.md for review and downstream prioritization. ## Quick Start Ask the agent to create a project roadmap from the current goals and open issue backlog, sequenced across Now, Next, and Later horizons.

Frequently Asked Questions about create-roadmap

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

FAQPage Schema
How do I create a product roadmap from a GitHub issue backlog?▼

Inventory open issues with ghx issue list, group them into initiatives tied to goal objectives, then place each initiative in a Now, Next, or Later horizon. The result is written to .sdlc/context/roadmap.md with a Mermaid Gantt timeline.

What is the difference between Now/Next/Later horizons and quarterly roadmaps?▼

Now/Next/Later horizons avoid the false precision of calendar dates, which turn a roadmap into a commitment device. Now is fully scoped and high-confidence, Next is roughly scoped, and Later is exploratory hypothesis-level work.

Can I use calendar quarters instead of Now/Next/Later horizons?▼

Yes, the horizon model is confirmed with the user before writing. Quarter-based schemes like 2026 Q3/Q4/2027 Q1 work with the same initiative fields, mapping Now to the current quarter and Later to exploratory future quarters.

What happens if goals.md is missing when creating a roadmap?▼

The Skill notes that goal alignment cannot be checked and flags it as an open question. Every initiative is expected to align to a goals.md objective, so the missing file weakens the roadmap's strategic grounding.

How are roadmap revisions handled after a review?▼

If .sdlc/context/review-roadmap.md exists with verdict changes-requested, the existing roadmap is revised to address each finding rather than regenerated. Content the review did not challenge is preserved with minimum changes.