plan-phase

Generates interface-freeze swim-lane implementation plans from versioned roadmap phases.

2|1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Consiliency/agent-harness --skill plan-phase-consiliency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-phase
Source: https://github.com/Consiliency/agent-harness/tree/main/phase-loop-skills/plan-phase
Command: npx skills add https://github.com/Consiliency/agent-harness --skill plan-phase-consiliency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

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.

Frequently Asked Questions about plan-phase

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

FAQPage Schema
How do I plan a roadmap phase for parallel execution?▼

Invoke the skill with a phase alias, number, or fuzzy name from specs/phase-plans-v*.md. It reads the phase, researches the touched code areas, and writes plans/phase-plan-<VERSION>-<PHASE_ALIAS>.md with interface freeze gates, swim lanes, and acceptance criteria.

What makes a phase plan execution-ready for the phase-loop runner?▼

The plan must start with phase_loop_plan_version: 1 frontmatter containing phase, repo-relative roadmap path, and roadmap_sha256. It also needs disjoint lane file ownership, an acyclic lane DAG, a Spec Closeout Plan section, and machine-checkable verification commands.

Why does the phase-loop runner reject plans with overlapping owned files?▼

Overlapping owned files across lanes trigger the overlapping_write_ownership lane-IR diagnostic and refuse execution, because two parallel lanes writing the same file cause merge corruption. Shared files must move into a preamble lane or the overlapping lanes must be collapsed.

Can I use this planner with Claude Code, Gemini, or Codex?▼

Yes, the skill ships per-harness override files under _overrides/ for claude, gemini, codex, and opencode. Each override adapts subagent usage, adapter-mode behavior, and closeout conventions while keeping the shared plan document contract identical.

When should I not use phase planning with swim lanes?▼

Skip it for single-file or single-concern changes, pure research questions, or specs without phase structure; a simpler detailed-plan approach fits those cases. Swim-lane planning pays off only when work spans multiple code areas that benefit from parallel lane execution.