speckit

Dispatch speckit commands to target specs by identifier and execute workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, and includes scripts (resource) components.

What problem does it solve?

Dispatcher intelligent for Speckit commands that targets a spec by its number or partial name and executes the appropriate speckit command workflow automatically.

Core Features & Use Cases

  • Single entry point to run any speckit command (specify, plan, tasks, clarify, analyze, checklist, implement, review) on any feature spec.
  • Shortcut-based routing via /speckit <identifier> or speckit.<command> <identifier> with an automatic spec-resolution flow.
  • Spec status dashboard when no command is provided, showing available artifacts and possible commands.
  • Contextual loading of the corresponding command file from .agents/commands based on user input and a helper script to resolve specs.

Quick Start

Run /speckit 001 to view the spec dashboard, or /speckit specify 'My feature' to start the auto-chain.

Frequently Asked Questions about speckit

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

FAQPage Schema
How do I automate spec management workflows for multiple feature specs?

You can automate spec management by dispatching commands like specify, plan, tasks, and implement to target specs by their identifier. This routing applies workflows across single or multiple specs automatically.

What is the best way to run spec workflows like clarify, analyze, and review from a single entry point?

Running spec workflows is best handled through a single dispatcher that routes shortcuts to internal command files. It loads the appropriate command definition from .agents/commands and executes with necessary context and safety checks.

How do I resolve a spec by its number or partial name to execute a targeted workflow?

To resolve a spec by number or partial name, a helper script maps user shortcuts to internal command files. This resolution flow ensures the correct spec is targeted before executing the specified workflow.

Do I need git and gh installed to dispatch spec commands and check status?

Yes, you need git and gh installed as dependencies to dispatch spec commands. These tools provide the necessary environment for executing workflows and running safety checks during command dispatch.

Can I view a status dashboard of available artifacts when no specific spec command is provided?

Yes, you can view a spec status dashboard by running the dispatcher without a command. It displays available artifacts and possible commands, helping you track progress across your feature specs.

Why is my spec workflow not executing when I target a spec by its identifier?

Your spec workflow might not execute if the corresponding command file is missing from .agents/commands, or if safety checks fail. The dispatcher relies on contextual loading of command definitions to run properly.