forge-buildlisted

# /forge:build — Implementation ## When to Use - User says `/forge:build` - User wants to implement a task, write code, or work through the task DAG - Working in a Forge project at Stage 5 or 6 ## Pre-flight Check **Entry gate (REQ-GATE-ENTRY-001)** — before adopting the persona, verify the prior stage's artifact exists: ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py preflight --stage 6 ``` If it exits non-zero, **STOP**: present its message verbatim and do not proceed — the prior stage must be completed first (or use `/forge:force-advance` to skip intentionally). 1. Read `pipeline/state.md` — confirm Forge project. 2. Confirm `pipeline/05-plan/task-dag.md` exists. If not: "Complete Stage 5 first (`/forge:plan`)." 3. Read `build/05-implementation/progress.md` (or create it) to identify the current task. 4. Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/check-gate.py --stage 5` to confirm Stage 5 gate passes. If gate fails, show what's missing and pause. 5. Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd . --stage 6` to load project-type overrides — these add build-stage criteria (e.g., fullstack: design tokens enforced, bundle budget, RSC boundary) that the Builder must respect. ## Steps 1. Read `agents/builder.md` to load the Builder persona. 2. Adopt that persona — you are now the Builder. 3. Read the current task from the task DAG and the corresponding spec section. 4. Follow the Builder workflow: read before editing, implement, tes