build-phaselisted

# Build Phase > **Judging doctrine:** the verifier/gate invariants behind this skill's quality gates and halt contract (mechanical checks gate first, deterministic gate verdicts) live in [`_shared/judge-core.md`](../_shared/judge-core.md) §2/§5 — this skill instantiates the executable-verifier archetype between steps. Thin orchestrator that reads step definitions from a plan document and runs `/build-step` for each one in sequence. Does not classify steps or decide flags -- those are declared in the plan. Posts comprehensive progress updates to GitHub issues so long-running builds are visible in real time. ## When to use - When you have 2+ build steps to run sequentially from a plan - When the user says "run all steps", "build phase N", or "run the whole phase" ## When NOT to use - For a single step: use `/build-step` directly --- ## Operator preference — autonomous + bundled UI + parallel (HEAVY) This skill's default posture, by strong operator preference: 1. **Autonomous end-to-end.** On parse-success the phase begins immediately — no operator confirmation prompt. The operator opted into autonomous execution by invoking `/build-phase`; if they wanted a preview, they would have used `--dry-run` (see Arguments table). build-phase then runs through dev → review → iterate → checkpoint without checking back in between code steps. Halts are reserved for the structural cases the skill already defines: BLOCKED verdicts, operator/wait/conditional step types, quality-gate f