speckit-implement

Execute task breakdowns to implement features and tests with TDD.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/a2mus/smart-da3m --skill speckit-implement-a2mus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-implement
Source: https://github.com/a2mus/smart-da3m/tree/main/.agents/skills/speckit-implement
Command: npx skills add https://github.com/a2mus/smart-da3m --skill speckit-implement-a2mus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a written task breakdown and project plan into a disciplined, step-by-step implementation workflow so teams can reliably turn specifications into tested code without skipping verification gates.

Core Features & Use Cases

  • Prerequisite verification: Runs the specified .specify prerequisite script to discover FEATURE_DIR and AVAILABLE_DOCS and ensures paths are absolute.
  • Checklist gating: Scans checklists/, computes pass/fail status, and pauses for user confirmation if any checklist is incomplete.
  • Structured task parsing: Loads tasks.md, plan.md, and optional data-model.md/contracts to derive phases, dependencies, and execution order.
  • TDD-first execution: Enforces tests-before-code for tasks, respects sequential vs parallel markers, and marks tasks complete in the tasks file.
  • Progress and error handling: Reports progress after each task, halts on non-parallel failures, and suggests next steps when blocked.
  • Use Case: Ideal for developers implementing a feature from a generated task plan in a repo that follows the spec-kit layout, ensuring checklists and tests are honored before code changes.

Quick Start

Run the speckit-implement skill to execute tasks.md, validate checklists, run tests-first, and implement the planned changes following the project's plan and TDD rules.

Frequently Asked Questions about speckit-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement task plans from markdown files using TDD rules?

Task plan implementation with TDD rules executes phases from tasks.md and plan.md, enforcing tests-before-code execution, sequential and parallel dependency markers, and checklist gating to ensure structured feature delivery.

What does checklist gating do during TDD-driven feature implementation?

Checklist gating scans the checklists directory to compute pass or fail statuses before implementation begins, pausing execution for user confirmation whenever any prerequisite checklist remains incomplete to prevent skipping verification steps.

Do I need a .specify directory to use spec-kit task execution?

Yes, spec-kit task execution requires a .specify directory containing prerequisite scripts that discover FEATURE_DIR and AVAILABLE_DOCS paths, ensuring environment variables are absolute before parsing tasks.md and plan.md for implementation phases.

How are sequential and parallel task dependencies handled during project setup automation?

Project setup automation parses task files to derive execution order from dependency markers, respecting sequential versus parallel execution rules, halting immediately on non-parallel failures, and marking completed tasks directly in the markdown file.

What happens when a non-parallel task fails during TDD-first execution?

TDD-first execution halts immediately upon non-parallel task failures, reports progress after each completed step, and suggests actionable next steps to help developers resolve blockages before resuming the implementation workflow.