implementlisted

# Implement Turn an approved SpecScore Plan, Feature, or Idea into staged, AC-traceable source-code changes. Plan-sourced mode uses parallel subagent dispatch with per-batch user approval. Feature-sourced and Idea-sourced modes operate as a single-pass conversation. ## Hard Gate <HARD-GATE> Do NOT invoke `specstudio:verify`, `writing-plans`, `frontend-design`, `mcp-builder`, or ANY downstream skill until ALL FIVE conditions hold for **every batch** produced in the current invocation: 1. Every subagent in the batch returned a terminal status (`DONE`, `DONE_WITH_CONCERNS`, or `BLOCKED` with user decision); no subagent is still `NEEDS_CONTEXT`. 2. The consolidated staged diff for the batch is lint-clean (`specscore spec lint` exits zero against the project, including any Plan-file changes staged in stub mode). 3. The conflict-detection check has passed (no line-overlap between sibling subagents' staged diffs) OR the user has explicitly approved a manual conflict-resolution path. 4. The user has explicitly approved the batch's consolidated staged diff. 5. The user has committed the staged set (the skill MUST NOT advance to the next batch while the working tree still has the prior batch staged but uncommitted). The only skill invoked after `specstudio:implement` is `specstudio:verify` (or — while `verify` is unshipped — a hand-back to the user with that recommendation). </HARD-GATE> ## When to Use - **Plan-sourced:** An approved Plan at `spec/plans/<slug>.md` is re