← ClaudeAtlas

implementlisted

Turns an approved SpecScore Plan into focused, AC-traceable source-code changes by dispatching one subagent per task in parallel batches computed from the Plan's **Depends-On:** dependency graph. Fires the `implementation.pre_commit` / `implementation.pre_push` reviewer gates at its checkpoints, so per-batch approval is gate-config-driven (a `type: human` reviewer is the human checkpoint; a `auto-approve` gate commits autonomously). Applies publication policy at approved implementation milestones; provides a Verifies: commit-message trailer template. Also accepts a Feature directly (no Plan) or an Idea directly (no Feature or Plan) for single-pass conversational implementation. Trigger: "implement", "/implement", "implement this plan", "specstudio:implement", or event `plan.approved`.
specscore/specstudio-skills · ★ 0 · Code & Development · score 73
Install: claude install-skill specscore/specstudio-skills
# Implement Turn an approved SpecScore Plan, Feature, or Idea into AC-traceable source-code changes. Plan-sourced mode uses parallel subagent dispatch; each commit is gated by the `implementation.pre_commit` reviewer gate and each push by `implementation.pre_push`, so per-batch approval is gate-config-driven rather than a hardcoded step (a `type: human` reviewer is the human checkpoint; a `auto-approve`/`deterministic`-only gate releases autonomously). Feature-sourced and Idea-sourced modes operate as a single-pass conversation. After the commit gate releases, the skill applies the shared publication policy at the implementation milestone; downstream verification still requires the relevant Feature or implementation commits to exist in git history. ## 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