What problem does it solve? Executing a multi-lane phase plan by hand risks touching files owned by other lanes, skipping verification, and losing track of what comes next in a roadmap. This Skill gives OpenCode a disciplined executor that enforces lane ownership, runs verification, and produces a structured closeout and handoff. ## Core Features & Use Cases - Lane-scoped execution: Parses the phase plan's lane DAG, owned files, and interface gates, then executes lanes in topological order without crossing ownership boundaries. - Git preflight and verification: Checks worktree state, runs lane-level and phase-level verification commands, and inspects diffs to confirm no peer-owned files were modified. - Optional worker fanout: Supports explicit parallel worker subagents for disjoint lanes when the user authorizes delegation. - Structured closeout: Emits machine-readable automation handoffs, reflections, manifest lifecycle updates, and next-phase routing back to planning or roadmap building. - Use Case: After generating a phase plan with opencode-plan-phase, run this Skill to implement each lane, verify tests, and produce a closeout that names the next phase and command. ## Quick Start Ask OpenCode to execute the latest phase plan in the plans directory, for example: run opencode-execute-phase on plans/phase-plan-03.md and verify all lanes.
