What problem does it solve? Implementing a multi-lane phase plan by hand risks touching files owned by other lanes, losing track of verification results, and leaving the git worktree in an ambiguous state. This Skill gives Gemini a disciplined execution loop that enforces lane ownership, runs per-lane and phase-level verification, and produces a machine-readable closeout the phase-loop runner can reconcile. ## Core Features & Use Cases - Lane-scoped execution: Parses the plan's lane DAG, owned files, and interface gates, then executes lanes in topological order without crossing ownership boundaries. - Git preflight and closeout audit: Checks git status before and after work, classifies dirty paths, runs the closeout audit for ignored outputs, and blocks on unowned or unauthorized changes. - Optional worker fanout: Supports explicit parallel worker subagents for disjoint lanes, with strict per-worker ownership briefs. - Use Case: After gemini-plan-phase produces plans/phase-plan-*.md, run this Skill to implement each lane, run its verification commands, and emit a shared automation: closeout with next-phase routing for the runner. ## Quick Start Ask Gemini to execute the latest phase plan from the plans directory, for example: run gemini-execute-phase on plans/phase-plan-v2.md and report verification results.
