Skill

implement

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.

developer-tools

npx claudepluginhub melodic-software/claude-code-plugins --plugin spec-driven-development

Tool Access

This skill is limited to using the following tools:

ReadGlobGrepWriteEditBashSkillTask

Preview

Guide the implementation of tasks from a specification, validating acceptance criteria as you go.

SKILL.md

Similar Skills

spec-driven

123

Orchestrates spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates. Activates for structured feature planning or 'use spec-driven'.

handbook-agent-spec-kit

spec-implement

Executes implementation tasks from approved plan.json, enforcing TDD, tracking progress via beads, and reporting in batches or autonomously. Use after spec-plan.

python

using-superpowers

185.1k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Parent Repo Stars63

Parent Repo Forks9

Last CommitFeb 15, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Guide Implementation

Guide the implementation of tasks from a specification, validating acceptance criteria as you go.

Workflow

Load Artifacts
- Read specification, design, and tasks
- Identify current task to implement
- Load relevant acceptance criteria
Present Implementation Checklist
- Show current task details
- Display acceptance criteria
- List files to create/modify
Guide Implementation
- Provide step-by-step guidance
- Create/modify files as needed
- Run tests after each change
Validate Acceptance Criteria
- Check each criterion is met
- Run verification commands
- Mark criteria as passed/failed
Update Task Status
- Mark task as complete
- Update tasks.md
- Show progress summary
- Suggest next task

Arguments

$ARGUMENTS - Path to specification file OR specific task ID (e.g., "TASK-1")

Examples

# 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

Implementation Session

During implementation, the command provides:

Task Context

╔══════════════════════════════════════╗
║  TASK-3: Create login endpoint       ║
╠══════════════════════════════════════╣
║  Requirement: FR-1                   ║
║  Depends On: TASK-1 ✓, TASK-2 ✓      ║
╚══════════════════════════════════════╝

Acceptance Criteria Tracker

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

Progress Summary

Feature Progress: 3/8 tasks complete (37%)
Current Task: TASK-3 (2/3 criteria met)

Related Commands

/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 specification