execute-task

# execute-task The execution loop. Three sources converge: - **Plan** (HOW) — `docs/superpowers/plans/*.md` produced by GENERATE - **TaskMaster** (WHAT) — `.taskmaster/tasks/tasks.json` with dependencies and complexity scores - **CDD** (PROOF) — acceptance cards per task, evidence-gated execute-task is the single skill that runs the full build from "tasks are ready" to SHIP_CHECK_OK. It is autonomous — no AskUserQuestion inside the loop. Any gap that would require user input is surfaced through the recon escalation ladder (step 11) or the inbox (steps 4 and 8), never via a modal prompt. ## Entry This skill is invoked either: 1. Directly by the user once HANDOFF has completed and a task-execution mode (A/B/C) has been dispatched, **or** 2. By the `prd-taskmaster` orchestrator when `current_phase` is `EXECUTE`. On entry, confirm that: - `.atlas-ai/state/pipeline.json` exists and records `phase: EXECUTE` - `.taskmaster/tasks/tasks.json` exists with at least one ready task - `.atlas-ai/customizations/system-prompt-template.md` is present (may be empty — absence is a setup bug, empty is fine) If any of the above are missing, report the gap and halt. Do NOT attempt to bootstrap the missing artifact from inside this loop — that is the orchestrator's job. ## Cycle (per iteration) Each pass through this cycle moves exactly one TaskMaster task from `pending` to `done`. Do the 13 steps in order. Do not skip. > **Task-start SHA** — at the very beginning of each iterati...