What problem does it solve? Turning a conversation, architecture discussion, or markdown spec into a structured, machine-validated multi-phase roadmap is error-prone and inconsistent. This Skill produces versioned specs/phase-plans-v<N>.md roadmap files that downstream planning skills can parse directly, with enforced structure, unique phase aliases, and an acyclic dependency DAG. ## Core Features & Use Cases - Roadmap creation and append modes: Create a new versioned roadmap or append phases to an existing one without rewriting prior phases, preserving alias namespaces per roadmap file. - Parallelization-maximizing decomposition: Applies heuristics that minimize serial phases, split work into parallel lanes and sibling phases, and define narrow interface-freeze gates (IF-0-<ALIAS>-<N>) that unblock downstream work early. - Mechanical validation: Runs phase-loop validate-roadmap to check stable headings, unique aliases, DAG acyclicity, gate reconciliation, and lane-count hints before handoff. - Use Case: After an architecture discussion about refactoring a monorepo, invoke this Skill to produce specs/phase-plans-v1.md with phased objectives, exit criteria, dependency DAG, and verification commands, then hand off each phase to a lane-level planning skill. ## Quick Start Ask the assistant to turn the current conversation or a named markdown spec into a phased roadmap saved as specs/phase-plans-v1.md.
