What problem does it solve? Turning a roadmap phase into an executable plan requires freezing interfaces, partitioning file ownership across parallel lanes, and defining testable acceptance criteria; doing this by hand produces overlapping edits, vague gates, and plans that fail at execution time. ## Core Features & Use Cases - Lane decomposition with disjoint ownership: Converts a roadmap phase into swim lanes (SL-N) with acyclic dependencies, explicit provided/consumed interfaces, and complete owned-file sets including tests, lockfiles, and migrations. - Machine-validated plan documents: Emits plans with phase_loop_plan_version: 1 frontmatter, roadmap SHA-256 pinning, Dispatch Hints, Execution Policy, and a Spec Closeout Plan, all linted by scripts/validate_plan_doc.py for DAG cycles, ownership overlap, and untestable criteria. - Harness-adaptable workflow: Ships per-harness overrides (Claude, Gemini, Codex, opencode) plus a review prompt asset for cross-vendor plan review, and integrates with the phase-loop runner via handoffs, reflections, and plan manifests. - Use Case: Given specs/phase-plans-v1.md, run the planner on phase FOUND to produce plans/phase-plan-v1-FOUND.md with interface freeze gates, parallel-safe lanes, and EC-referenced acceptance criteria ready for the execute-phase skill. ## Quick Start Ask the agent to plan phase FOUND from specs/phase-plans-v1.md into an execution-ready swim-lane plan document.