speckit-implement

Execute Spec-kit implementation plans with checklist validation and hook handling.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-implement-d0whc3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-implement
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.trae/skills/speckit-implement
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-implement-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you safely and systematically execute a Spec-kit implementation plan by running prerequisite checks, validating task and checklist readiness, and then following the ordered tasks defined in the project’s plan.

Core Features & Use Cases

  • Pre-implementation hook execution: Discovers and prepares extension hooks from .specify/extensions.yml, printing clear instructions for optional and mandatory hooks without evaluating hook conditions.
  • Checklist readiness validation: Scans checklists/ for completion status, summarizes results in a pass/fail table, and can stop for confirmation when items are incomplete.
  • Implementation context loading: Reads tasks.md and plan.md (and optional context like data-model.md, contracts/, research.md, and quickstart.md) to ensure execution matches the defined architecture and requirements.
  • Project setup verification: Detects repository structure and ensures ignore files (e.g., .gitignore, .dockerignore, .eslintignore, .prettierignore, etc.) exist and include essential patterns based on the tech stack.
  • Task-driven execution: Executes tasks phase-by-phase with dependency awareness, TDD guidance (tests before implementation), parallel task handling, file-based coordination, and progress/error checkpoints.
  • Post-implementation hook execution: After validation, discovers after_implement hooks and prints instructions for optional/mandatory hooks while skipping condition evaluation.

Quick Start

Run the speckit-implement skill in your Spec-kit project to validate checklists, verify ignore files, load tasks and plans, then execute the defined implementation steps.

Frequently Asked Questions about speckit-implement

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

FAQPage Schema
How do I execute a Spec-kit implementation plan phase by phase?

To execute a Spec-kit implementation plan, you run a workflow that validates prerequisite checklists, verifies project setup, and reads tasks.md and plan.md to process ordered implementation phases with dependency awareness and TDD guidance.

What happens if my Spec-kit checklists are incomplete before implementation?

When checklists are incomplete, the implementation workflow scans the checklists directory, summarizes results in a pass/fail table, and enforces stop-on-failure behavior to halt execution for confirmation before proceeding with tasks.

Does Spec-kit implementation support parallel tasks and file coordination?

Yes, Spec-kit implementation handles parallel task execution and enforces file-based coordination constraints by reading ordered implementation phases defined in your project's plan.md and tasks.md files.

How do pre-implementation and post-implementation hooks work in Spec-kit?

Spec-kit implementation discovers pre and post hooks from .specify/extensions.yml, printing clear instructions for optional and mandatory hooks without evaluating hook conditions, ensuring you know what to run before and after task execution.

Can I verify repository setup and ignore files before running Spec-kit tasks?

Yes, project setup verification detects the repository structure and ensures ignore files like .gitignore, .dockerignore, .eslintignore, and .prettierignore exist and include essential patterns based on your tech stack before executing tasks.

What context files are loaded during Spec-kit implementation?

Implementation context loading reads tasks.md and plan.md, along with optional files like data-model.md, contracts, research.md, and quickstart.md to ensure task execution matches the defined architecture and requirements.