write-roadmap

Draft outcome-based roadmaps with exit criteria across portfolio, product, or domain scopes.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/daddia/space --skill write-roadmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-roadmap
Source: https://github.com/daddia/space/tree/main/.agents/skills/write-roadmap
Command: npx skills add https://github.com/daddia/space --skill write-roadmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roadmap planning across portfolios, products, or domains is often manual, error-prone, and siloed, hindering alignment and progress tracking.

Core Features & Use Cases

  • Sequenced, phase-based roadmaps that replace epic lists with exit criteria and gates.
  • Cross-scope planning for portfolio, product, and domain initiatives, with dependencies and milestones.
  • Quick generation of actionable roadmaps aligned to product strategy and delivery goals.

Quick Start

Draft a portfolio roadmap for my workspace using outcome-based phases with exit criteria.

Frequently Asked Questions about write-roadmap

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

FAQPage Schema
How do I draft a strategic roadmap using outcome-based phases instead of epic lists?

Draft a strategic roadmap by defining outcome-based phases with clear exit criteria and gates. This approach replaces traditional epic lists, guiding sequencing logic and phase definitions to align product delivery with strategic goals.

What is the best way to plan a cross-scope portfolio roadmap for multiple products?

Plan a cross-scope portfolio roadmap by sequencing initiatives across multiple products with defined dependencies and milestones. This ensures cross-scope alignment for portfolio, product, and domain planning without manual silos.

Do I need a product.md file before generating a roadmap.md?

Yes, a product.md file is required as a prerequisite. The roadmap generation enforces this requirement, utilizing the domain's template scaffolding and related artifacts to produce the final roadmap.md output.

Can I use outcome-based phase planning for a single named domain instead of a full portfolio?

Yes, outcome-based phase planning applies to a single named domain, a single product, or a full portfolio. The tool guides sequencing logic, phase definitions, and governance regardless of the scoped planning level.

How does governance factor into phased delivery roadmaps?

Governance is integrated directly into phased delivery roadmaps through exit criteria and gates. This enforces prerequisites and ensures phase progression aligns with domain strategy and delivery milestones.

What are the limitations of replacing epic lists with exit criteria in roadmap planning?

Replacing epic lists with exit criteria limits granular task tracking, focusing instead on phase-based gates and strategic outcomes. This approach requires existing domain template scaffolding and a product.md file to function correctly.