Execute Phase

Execute Phase

Modes: unit loop (default when P<n> is omitted) executes every remaining phase through close-out, with one gate/commit per phase; explicit phase P<n> executes exactly that phase; legacy SPECs without ## Phases run once. --fix selects a fix unit.

First matching row wins:

Never infer a phase ID absent from the invocation/ledger.

Turn contract

Load and verify the canonical Turn contract (11 boxes) before ending every turn. Skill-specific additions and push policy live only in PREFLIGHT.md. Missing reference → STOP.

Hard rules

• Honor Workflow conventions (branch/PR, gate-before-commit, docs language). Run git branch --show-current before editing/committing; if main, create the working branch first (unless the user explicitly uses main).
• Phases are P1, P2, …. The <phase> argument and every reference in PLAN.md/TASKS.md/progress.md/commits is P1, P2, … ("phase N") — never S1/S2/"Step N". If a plan you're handed uses S1-style labels, normalize it to P1, … before executing and note it in decisions.md.
• Implement only the requested scope: all remaining ledger phases when omitted, or exactly P<n>. Never invent/bundle across phase boundaries; unit-loop mode still gates and commits each phase.
• Stop after the gate passes; keep commits small and reviewable.
• Feature mode: update TASKS.md, progress.md, testing.md, known-issues.md each phase (and decisions.md if architecture moved).
• Plan conflict: update TASKS.md/PLAN.md and record why in decisions.md; never silently diverge.
• Dependency gate before any work — the preflight resource owns it. No edit, branch, or commit for an unmerged dependency closure unless the user passed --force.
• Phase-lint before any edit — the preflight resource runs it after dependency/own-status gates. Any FAIL stops unless the user passed --force.
• Pre-execution review before any edit — a current, independently recorded PLAN-REVIEW-PASS bound to the plan's exact bytes must exist (--fix: on the fix unit). Missing, stale, or wrong-stage stops the turn with the gate block; this is the one preflight gate --force does not reach — the block, no-forgery and legacy rules live in pre-execution gate.
• Pre-write discovery before any repository write — after the read-only gates and before branch creation, planning commit, or source/test edit, settle the mapper contract (implementation-discovery). It answers the seven evidence questions, emits the fixed compact map, and routes READY | REPLAN | NEEDS-DESIGN | BLOCKED; only READY authorizes the first write.

Context budget (hard rule — context is repaid every turn)

• File cap: read at most 10 full files per phase beyond SPEC.md, the phase TASKS.md section and progress.md. Targeted ≤50-line reads and greps do not count. If the cap would be exceeded, stop, record known/unknown facts in Gotchas:, then proceed only with targeted evidence or report the blocker.
• Summarize: record needed facts with file:line; never re-read summarized files or quote whole files.
• Step 0: read only Workflow conventions, the architecture section for the phase Layer:, and the optional invariant document named by the map.
• Unit-loop reset: after each commit retain only the progress.md receipt; use a fresh worker per phase where possible, otherwise never re-read prior files.

Progressive loading — mandatory route before acting

This entrypoint carries the universal turn contract and handoff schema. Load only the listed one-hop route resource immediately before its step.

1. Every invocation: consume verification contract, read/run preflight gates, and stop on a contracted blocker before editing. This route owns NRS and Architectural invariants gates. After the read-only pre-execution gate and before any branch/planning/source write, load and settle the pre-write mapper implementation-discovery — it emits the fixed map and routes READY | REPLAN | NEEDS-DESIGN | BLOCKED.
2. Without explicit P<n>, read unit loop, then execution contract, then exactly one workflow: feature, small/phased, --fix, or legacy. Never load another mode.
3. Read only the needed policy:
   • writing a forge body → forge body policy
   • creating an issue → descope guard first
   • finding out-of-scope work → opportunistic finding policy
4. Before progress.md, read handoff schema.
5. For implementation/finish, read closeout; for a folded finding also folding.
6. Only for /loop, external drivers, manual batching, or missing vendor primitives, read batch and portability.

Fixed blocks in selected resources are normative and copied exactly. Missing or unreadable required resource → STOP; never reconstruct from memory.

Portability

The contract is vendor-neutral. When slash commands, tiers or a loop primitive are absent, read batch and portability and use its fallback; never skip the workflow step.

Relationship to other skills

Planned by plan-feature/plan-fix; executes their SPEC. Explicit phases may hand off to review-change at layer/accumulation/sensitivity checkpoints and must at unit end. Unit-loop skips intermediate checkpoints and recommends the manual /review-change → /fold-findings (only on REVIEW-FAIL) → re-run /review-change path after opening the PR; review-change remains the manual entry. Independent work stays a proposal. A finished unit always opens its PR and flips to done; audit-pr gates merge. Every invocation prints the next step.

Done when

• Requested scope is implemented (all remaining phases, one explicit phase, or legacy pass), gate is green, per-phase docs are updated, and the work is committed on the correct branch with nothing bundled beyond scope.
• git status --porcelain is empty and an open-PR branch has nothing unpushed.
• A finished unit is done, has an opened PR (URL printed), and recommends the mandatory /review-change end review, then /fold-findings (only on REVIEW-FAIL) and a re-run /review-change, with /audit-pr as the merge gate.