roadmap

Generate phased implementation plans from research documents with dependency graphs.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/lasswellt/cc-plugin-suite --skill roadmap-lasswellt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap
Source: https://github.com/lasswellt/cc-plugin-suite/tree/main/skills/roadmap
Command: npx skills add https://github.com/lasswellt/cc-plugin-suite --skill roadmap-lasswellt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roadmap helps transform scattered research into a structured, phased implementation plan that maps capabilities to domains and epics.

Core Features & Use Cases

  • Extract capabilities from research documents.
  • Cluster capabilities into domains and assign domain owners.
  • Generate phase plans, dependency graphs, and epic backlogs.

Quick Start

Start by providing your research documents and run the roadmap skill to generate an initial plan.

Frequently Asked Questions about roadmap

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

FAQPage Schema
How do I convert research documents into a phased implementation roadmap?

Generating a phased implementation roadmap from research documents involves extracting capabilities, clustering them into domains, resolving dependencies, and producing machine-readable epics with traceability to the original sources.

What is the best way to structure an epic backlog from multiple research sources?

The best way to structure an epic backlog from multiple research sources is to cluster extracted capabilities into domains, resolve dependencies, and produce machine-readable epics with traceability to source documents.

Can I generate dependency graphs and domain maps from existing project research?

Yes, you can generate dependency graphs and domain maps by extracting capabilities from research, clustering them into structured domains, and resolving dependencies for implementation sequencing.

Does this approach work for projects requiring separate phase plans for frontend and backend?

Yes, this approach works for projects needing separate phase plans by generating detailed implementation plans across frontend, backend, and infrastructure layers from clustered domain capabilities.

How do I ensure traceability between generated epics and my original research documents?

You ensure traceability by generating machine-readable epics directly from extracted capabilities, mapping each epic back to the original research documents used to build the domain overviews.