implementation-speclisted

Produce a phased implementation spec (build guide) from requirements and research. Use when the user has a researched problem and needs a concrete plan for building it — with phases, acceptance criteria, and file-level change lists. Triggers include "write a spec", "create a build plan", "implementation plan", "how should I build this", "write a PRD", "create a build guide", "phase this work", "break this into steps", "spec this out", or any situation where requirements and research exist and the next step is a structured plan for implementation. Also use when a tracked issue has both requirements and a research brief and needs to move to the build stage.
jacarty/claude-toolkit · ★ 0 · Testing & QA · score 70

Install: claude install-skill jacarty/claude-toolkit

# Implementation Spec — From Research to Build Plan ## What This Skill Does This skill takes requirements and research as inputs and produces an **implementation spec** — a single document combining scoping decisions, technical choices, acceptance criteria, and a phased build plan. The spec is the contract between the planning stage and the build stage. It is designed to be consumed by a developer, by Claude Code, and by review agents (e.g. a phase-acceptance agent), so it must be precise and actionable. ## When to Use This Skill Use when: - Requirements exist (from the requirements-elicitation skill or an existing brief) - Research has been done (from the research-brief skill or existing investigation) - The user wants a structured plan for building, not just a list of things to do - A tracked issue has been researched and needs to move to implementation Do NOT use when: - Requirements haven't been gathered yet (use requirements-elicitation first) - The technical landscape hasn't been investigated (use research-brief first) - The work is small enough that a spec would be overhead (just do it) - The user wants to explore options (use tree-of-thought, graph-of-thought, or trade-off-analysis) --- ## Process ### Step 1 — Gather Inputs Collect the inputs that ground the spec: - **Requirements document** — from the requirements-elicitation skill, an existing PRD, or the issue description itself. - **Research brief** — from the research-brief skill or existing rese