spec-implement

# Spec Implement Pick up tasks. Execute them. Track progress. Report. Stop when blocked. **Announce at start:** "I'm using the spec-implement skill to execute this plan." This skill does not make design decisions or modify the plan. If the plan is wrong, go back to spec-plan. If the design is wrong, go back to spec-brainstorm. ## Prerequisites Before starting, verify these exist: 1. **Approved spec** — `docs/specs/YYYY-MM-DD-<feature>/design.md` 2. **Approved plan** — `docs/specs/YYYY-MM-DD-<feature>/plan.json` 3. **Tasks created** — In beads, harness todo list, or plan.json task list 4. **Not on main/master** — Never start implementation on main/master without explicit user consent. Create a branch or use a git worktree first. If anything is missing, do not proceed. Tell the human what's needed. --- ## Step 1: Load and Review the Plan Read plan.json critically before writing code. Look for: - Unclear or ambiguous tasks - Missing file paths or incomplete validation criteria - Tasks that conflict with each other - Dependencies that don't match what you see in the codebase If you find concerns, **raise them with the human before starting**. Don't guess. Don't assume. Don't force through blockers. If no concerns, create task tracking and proceed. --- ## Step 2: Choose Execution Mode If the human hasn't specified a mode, ask. ### Autonomous Mode > "Implement it all. Don't stop until you're done." - Execute all tasks in dependency order - Track progress: bead...