execute

# /supergraph:execute Dispatch plan tasks with TDD. Parallel by default when tasks are independent. Usage: `/supergraph:execute` | `task N` | `tasks N,M` | `from task N` | `plan auth-login task 2` | `plan auth-login sequential` ## Steps ### 0. Announce "I'm using /supergraph:execute to implement this plan." ### 1. Load Context - `/supergraph:scan` should already be done. If `.supergraph-env` missing → STOP: "Run `/supergraph:scan` first." - Commands from `.supergraph-env` (if present) or plan `## Environment Context` ### 2. Select Plan Count plan files in `docs/supergraph/plans/*.md`: | Count | Action | |---|---| | 0 | STOP: "Run `/supergraph:plan` first" | | 1 | Auto-select | | >1, no `plan <slug>` arg | STOP: list plans, ask user | | `plan <slug>` provided | Match filename. If >1 match ask. | Parse task scope: `task N`, `tasks N,M,K`, `from task N`, or all incomplete. Parse `sequential` flag → force sequential mode. ### 3. Critical Review Read plan before dispatch: - Has `## Environment Context`? - Selected tasks have all required fields (Status, Risk, Dependencies, Files, Acceptance, TDD, Steps, Checkpoint)? - Commands real, not placeholders? File paths exact? - Plan-reviewer returned `Approved` (or user explicitly approved)? If missing or not Approved → STOP, dispatch `supergraph:plan-reviewer`, wait for Approval. Also check: plan has user approval step (step 11)? If not → ask user: "Plan was not reviewed by you. Proceed anyway? [yes / no]" Check dependencies: T...