speckit-implement

Execute implementation tasks from tasks.md and plan.md with prerequisite checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-implement turns an implementation plan into executed work by orchestrating prerequisite checks, checklist validation, context loading, and task execution, while honoring optional extension hooks.

Core Features & Use Cases

  • Extension hook orchestration: Runs configured before/after hooks from .specify/extensions.yml when enabled.
  • Prerequisite and checklist validation: Verifies repo prerequisites and computes checklist pass/fail status before proceeding.
  • Context-driven implementation: Loads tasks.md and plan.md (and optional spec docs) to guide execution in a plan-consistent order.
  • Repository hygiene: Verifies or creates ignore files (.gitignore, .dockerignore, etc.) based on detected technologies.

Quick Start

Use the speckit-implement skill with an optional guidance argument to start executing the implementation tasks from tasks.md.

Frequently Asked Questions about speckit-implement

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

FAQPage Schema
How do I execute implementation tasks from tasks.md and plan.md safely?

To execute implementation tasks safely, run prerequisite validation, checklist status checks, and task execution defined in tasks.md and plan.md. The process applies deterministic, plan-driven work including setup verification and context loading for spec-kit projects.

What are extension hooks in spec-kit implementation and how do they work?

Extension hooks in spec-kit implementation are optional before_implement and after_implement hooks configured in .specify/extensions.yml. They run during task orchestration with safe YAML parsing, allowing you to inject custom logic before or after implementation tasks execute.

Do I need a spec-kit project structure to run plan-driven task execution?

Yes, plan-driven task execution applies to spec-kit projects. You need tasks.md and plan.md files for context loading and task execution, with optional data-model.md, contracts, research, and quickstart.md files available for additional implementation context.

How does checklist gating work during repository implementation?

Checklist gating works by computing pass or fail status from prerequisite and checklist validation before proceeding with task execution. This deterministic approach ensures repository prerequisites are verified and all required checklist items pass before implementation tasks run.

Can I verify repository hygiene like .gitignore and .dockerignore files during implementation?

Yes, repository hygiene is verified during implementation by checking for or creating ignore files such as .gitignore and .dockerignore. This happens automatically based on detected technologies during the prerequisite validation phase of task execution.

What's the best way to orchestrate plan-driven work with optional spec docs?

The best way to orchestrate plan-driven work is loading tasks.md and plan.md for execution order, optionally reading data-model.md, contracts, research, and quickstart.md for context, then updating task completion status while handling before_implement and after_implement hooks.