spec-implement

# Spec Implement Execute the approved Spec-backed Plan. Track progress when it uses tracked tasks. 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 `docs/specs/YYYY-MM-DD-<feature>/design.md` 2. Approved `docs/specs/YYYY-MM-DD-<feature>/plan.json` 3. Any tracker entries selected during planning are available 4. You are not 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, proceed. Use existing tracker entries when present. --- ## Step 2: Choose Execution Style If the human has not specified an execution style, ask. ### Autonomous Mode > "Implement it all. Don't stop until you're done." - Execute all tasks in dependency order - Track progress when the Sp...