speckit-implement

Execute Speckit implementation plans with checklist gates and extension hooks.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/StrangeDaysTech/arborist-cli --skill speckit-implement-strangedaystech
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: speckit-implement
Source: https://github.com/StrangeDaysTech/arborist-cli/tree/main/.claude/skills/speckit-implement
Command: npx skills add https://github.com/StrangeDaysTech/arborist-cli --skill speckit-implement-strangedaystech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a Speckit implementation plan into a guided, checklist-validated execution flow so teams can reliably carry out tasks in the intended order.

Core Features & Use Cases

  • Extension hook orchestration (before/after): Runs configured pre-implement and after-implement hooks from .specify/extensions.yml, respecting optional vs mandatory behavior and silently skipping invalid hook configs.
  • Checklist status enforcement: Scans FEATURE_DIR/checklists/ to compute PASS/FAIL, optionally blocks execution when checklists are incomplete, and prompts the user to continue.
  • Plan and task context loading: Reads tasks.md and plan.md as required sources of execution rules, plus optional context files like data-model.md, contracts/, research.md, and quickstart.md.
  • Project setup verification: Detects project characteristics (git, Docker, JS/TS/ESLint/Prettier, Terraform, Helm, etc.) and ensures ignore files exist and contain essential patterns.

Quick Start

Ask the assistant to run speckit-implement for the current repository after you have a valid Spec-kit structure and tasks.md/plan.md present.

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 implementation plan across my repository with task dependencies?β–Ό

Implementation plan execution validates prerequisites, coordinates phase-by-phase tasks, and enforces dependency rules across your repository. It reads tasks.md and plan.md to guide the execution flow and verify completion.

What's the best way to enforce checklist completion before running implementation tasks?β–Ό

Checklist completion enforcement scans your feature directory's checklists to compute PASS/FAIL status, optionally blocks execution when incomplete, and prompts the user to continue, ensuring validation steps are met before proceeding.

Do I need a .specify directory to run speckit-implement?β–Ό

A .specify directory is required containing tasks.md and plan.md as execution sources. Optional context files like data-model.md, contracts/, research.md, and quickstart.md can be loaded to provide additional implementation context.

How do extension hooks work during task orchestration?β–Ό

Extension hooks run pre-implement and after-implement configurations from .specify/extensions.yml, respecting optional versus mandatory behavior and silently skipping invalid hook configurations to maintain smooth execution flow.

Can I verify project setup and ignore files for Docker, Terraform, or JS/TS before implementation?β–Ό

Project setup verification detects characteristics like git, Docker, JS/TS/ESLint/Prettier, Terraform, and Helm, ensuring ignore files exist and contain essential patterns before task execution begins in your repository.

Why are my implementation tasks not running in parallel?β–Ό

Task execution follows dependency and parallel rules defined in your plan. If prerequisites are unmet or checklist gates block execution, tasks run sequentially or pause until validation requirements are satisfied.