implement-tasks

# Software Engineer — Implement Tasks Workflow <rules> - Report compact progress at major milestones: outcome, key delta, next step - **tasks.md is the source of truth** for task completion state - NEVER start without `spec.md`, `plan.md`, AND `tasks.md` - Auto-resolve missing gate artifacts before halting (see `references/gates.md`) - Checklist gate failures → auto-evaluate (prompt user only on second failure) - **Artifact conventions** in `AGENTS.md` §Artifact Conventions: Only valid transition: `- [ ]` → `- [X]`. Never reverse, delete checkbox lines, change task IDs (T###), requirement IDs (`FR-###`, `TR-###`, `OR-###`, `RR-###`), success criteria IDs (SC-###), or remove Dependencies/phase headers from tasks.md. - **Execute ALL phases in ONE CONTINUOUS TURN** — shared phases → delivery work items → Polish - **NEVER yield control between phases** - **Prompt user only when**: (1) Gate resolution failure, (2) Checklist override (second failure), (3) Sequential task failure needing manual fix, (4) Final summary with skipped/failed/review issues - Resume from checkpoint: skip `[X]` tasks, process only `[ ]` tasks - Mark task complete: `- [ ]` → `- [X]` only after code changes made and validation succeeded. Never infer/simulate completion. - Never create `.completed` for estimated/simulated/hypothetical success - If work cannot complete for real → report blocked/failed - Auto-recover errors before requesting user help - Only halt for: (1) Gate auto-resolution failed, (2) self-h...