codex-execute-phase

Executes Codex phase plans with lane ownership, verification, and structured closeout handoffs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementing a multi-lane phase plan by hand risks crossing file-ownership boundaries, skipping verification, and leaving the git worktree in an ambiguous state. This Skill turns a codex-plan-phase plan into a disciplined execution run with preflight checks, lane-scoped edits, and machine-readable closeouts. ## Core Features & Use Cases - Lane-scoped execution: Parses the plan's lane DAG, owned files, and interface gates, then implements each lane in topological order without touching peer-owned files. - Verification and closeout contract: Runs lane and phase verification commands, audits the dirty worktree with phase-loop-closeout-audit, and emits a typed automation closeout with blocker taxonomy, handoff files, and reflections. - Optional worker fanout: Supports explicit parallel worker subagents only for disjoint lanes, with strict per-worker ownership briefs. - Use Case: After planning a roadmap phase, invoke this Skill so Codex implements the lanes, runs the tests, and reports the next phase and next command without manual git triage. ## Quick Start Ask Codex to execute the latest phase plan in plans/ using the codex-execute-phase skill and report the verification results and next command.

Frequently Asked Questions about codex-execute-phase

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

FAQPage Schema
How do I execute a phase plan with Codex?▼

Point the skill at a plan produced by codex-plan-phase, defaulting to the latest plans/phase-plan-*.md file. It runs preflight git checks, executes lanes in topological order, runs verification commands, and emits a structured closeout with the next phase and command.

How does lane file ownership work during phase execution?▼

Each lane's Owned files entries define the write contract; the executor edits only those paths and treats consumed interfaces as read-only. If implementation requires touching another lane's files, execution stops and routes back to planning for an ownership amendment.

Can I run lanes in parallel with worker subagents?▼

Parallel worker fanout is allowed only when the user explicitly requests it and the DAG-ready lanes are disjoint with machine-verified ownership. Each worker brief assigns exact owned files, read-only files, and requires a final report of changes, tests, and blockers.

What happens when verification fails during phase execution?▼

The executor diagnoses the failure once and repairs it within the lane if the cause is local. If the same verification still fails, it reports a blocked status with blocker_class=repeated_verification_failure instead of forcing completion.

Why does execution stop with a dirty_worktree_conflict blocker?▼

The blocker triggers when dirty paths are unowned, ignored outputs are typed unknown by phase-loop-closeout-audit, or unrelated user work overlaps required lane files. Phase-owned outputs with passing verification instead report awaiting_phase_closeout for the runner to commit.