spec-codinglisted

Guide users through spec-driven development — from goal clarification through requirements, design, task planning, and incremental execution. Use this skill whenever a user wants to build a new feature with upfront planning, asks for a structured development workflow, mentions "spec-driven", wants to create requirements or a design doc before coding, or invokes /spec-coding. Also trigger when a user has existing spec files (requirements.md, design.md, tasks.md) and wants to continue or execute tasks from them.
kevinlin/skills · ★ 3 · Code & Development · score 74

Install: claude install-skill kevinlin/skills

# Spec-Driven Development A workflow for building features specification-first. Instead of jumping straight into code, you walk through five stages — each producing a concrete artifact that the next stage builds on. This front-loaded planning catches design issues early and produces better implementations. ## Stages | Stage | Output | Purpose | |-------|--------|---------| | 1. Goal Confirmation | Shared understanding | Align on what we're building and why | | 2. Requirements | `requirements.md` | Define *what* the system does (EARS format) | | 3. Design | `design.md` | Define *how* it works technically | | 4. Task Planning | `tasks.md` | Break the design into executable coding steps | | 5. Execution | Working code | Implement tasks incrementally | All spec artifacts live in `docs/specs/{feature-name}/` (kebab-case). ## Resuming a Workflow Users often return to a workflow across multiple sessions. Before starting fresh, check whether spec files already exist for the feature: - If `tasks.md` exists with unchecked items → offer to resume at Stage 5 (Execution) - If `design.md` exists but no `tasks.md` → offer to resume at Stage 4 (Task Planning) - If `requirements.md` exists but no `design.md` → offer to resume at Stage 3 (Design) - If no spec files exist → start from Stage 1 When resuming, read all existing spec files first to rebuild context, then confirm with the user where they'd like to pick up. ## Approval Gates Every stage that produces a document (Stages 2–4)