Stats
Actions
Tags
Guides implementation of specification tasks with checklists, step-by-step file edits, tests, acceptance criteria validation, and progress tracking. Phase 4 of Spec Kit workflow.
How this skill is triggered — by the user, by Claude, or both
Slash command
/spec-driven-development:implementThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide the implementation of tasks from a specification, validating acceptance criteria as you go.
Guide the implementation of tasks from a specification, validating acceptance criteria as you go.
Load Artifacts
Present Implementation Checklist
Guide Implementation
Validate Acceptance Criteria
Update Task Status
$ARGUMENTS - Path to specification file OR specific task ID (e.g., "TASK-1")# Start implementing from specification
/spec-driven-development:implement .specs/user-auth/spec.md
# Implement specific task
/spec-driven-development:implement TASK-3
# Continue with next task
/spec-driven-development:implement --next
During implementation, the command provides:
╔══════════════════════════════════════╗
║ TASK-3: Create login endpoint ║
╠══════════════════════════════════════╣
║ Requirement: FR-1 ║
║ Depends On: TASK-1 ✓, TASK-2 ✓ ║
╚══════════════════════════════════════╝
Acceptance Criteria:
[✓] AC-1.1: Given valid credentials, login succeeds
[ ] AC-1.2: Given invalid password, returns 401
[ ] AC-1.3: Given locked account, returns 403
Feature Progress: 3/8 tasks complete (37%)
Current Task: TASK-3 (2/3 criteria met)
/spec-driven-development:specify - Generate specification (Phase 1)/spec-driven-development:plan - Generate design (Phase 2)/spec-driven-development:tasks - Generate task breakdown (Phase 3)/spec-driven-development:validate - Validate specificationnpx claudepluginhub melodic-software/claude-code-plugins --plugin spec-driven-developmentExecutes approved implementation tasks from a plan.json file created by spec-plan. Tracks progress via beads or harness todos, enforces TDD, and reports between batches. Invoke when ready to start coding from an approved plan.
Orchestrates spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates. Activates for structured feature planning or 'use spec-driven'.
Executes tasks from an OpenSpec tasks.md file during implementation. Reads task checkboxes, applies code changes, marks progress, runs validation, and handles blockers.