speckit-implement

Execute tasks.md phases with dependency-aware sequencing in spec-kit projects.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/nalthoff/spec-kit-prep-specify --skill speckit-implement-nalthoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-implement
Source: https://github.com/nalthoff/spec-kit-prep-specify/tree/main/.cursor/skills/speckit-implement
Command: npx skills add https://github.com/nalthoff/spec-kit-prep-specify --skill speckit-implement-nalthoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end implementation process by executing the task plan defined in tasks.md within a Spec Kit project, ensuring consistent progress and traceability.

Core Features & Use Cases

  • Orchestrates Setup, Tests, Core development, Integration, and Polish phases in strict order
  • Respects task dependencies and parallel execution markers, enabling safe concurrent work
  • Provides progress updates, error reports, and completion status to support delivery discipline

Quick Start

Provide a full tasks.md and trigger the speckit-implement workflow to begin implementing the plan.

Frequently Asked Questions about speckit-implement

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

FAQPage Schema
How do I automate task execution from a tasks.md plan?

Automating task execution from a tasks.md plan requires a workflow that orchestrates setup, tests, core development, integration, and polish phases in strict order. The speckit-implement workflow executes this end-to-end implementation automatically.

What is dependency-aware sequencing in task implementation?

Dependency-aware sequencing in task implementation coordinates phases by respecting task dependencies and parallel execution markers. This enables safe concurrent work while enforcing pre-checks and validation checkpoints throughout the development lifecycle.

Can I use TDD workflow with automated task implementation?

TDD workflow is supported with automated task implementation by executing tasks defined in tasks.md. The system enforces test phases alongside core development, integration, and polish phases with validation checkpoints.

Do I need a full tasks.md file to start automated implementation?

A full tasks.md file is required to start automated implementation. You provide the complete task plan and trigger the workflow to begin implementing setup, tests, core development, integration, and polish phases in strict order.

How does automated implementation handle progress reporting and errors?

Automated implementation handles progress reporting and errors by providing updates, error reports, and completion status throughout execution. This supports delivery discipline by coordinating validation checkpoints and extension hooks across all phases.

When should I not use automated end-to-end implementation?

Automated end-to-end implementation should not be used without a complete tasks.md file defining your task plan. The workflow requires dependency-aware sequencing, pre-checks, and validation checkpoints to properly coordinate the implementation phases.