speckit

Routes development pipeline tasks through specify-to-retro stages with governance checks.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ranvirsingh/speckit --skill speckit-ranvirsingh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit
Source: https://github.com/ranvirsingh/speckit/tree/main
Command: npx skills add https://github.com/ranvirsingh/speckit --skill speckit-ranvirsingh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit provides a structured, issue-backed development pipeline by routing work through a minimal set of pipeline skills: speckit-specify, speckit-research, speckit-plan, speckit-implement, speckit-test, speckit-e2e, speckit-retro, with governance checks and automatic progression when steps succeed.

Core Features & Use Cases

  • Route to the appropriate sub-skill based on the current project phase (specify, research, plan, implement, test, e2e, retro).
  • Verify governance constraints via the constitution and extension hooks before each transition.
  • Auto-continue through pipeline steps on success to streamline the workflow.
  • Maintain living docs and issue-backed specs with living-docs integration for research and retro states.
  • Suitable for greenfield or brownfield projects and supports extension via sub-skills and subagents.

Quick Start

Give Speckit a feature description and let it route you through the best-fit skill sequence.

Frequently Asked Questions about speckit

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

FAQPage Schema
How do I structure an AI-assisted coding workflow with governance gates and automated progression?

An AI-assisted coding workflow with governance gates uses a pipeline router to sequence work through specify, research, plan, implement, test, e2e, and retro phases. It verifies compliance constraints before each transition and auto-continues on successful execution to streamline development.

How do I maintain living docs and issue-backed specs during AI development?

Living docs and issue-backed specs are maintained by routing research and retro states through a structured pipeline. This integration ensures documentation stays synchronized with project phases, preserving traceability from specification through implementation and testing.

Can I use a pipeline router for both greenfield and brownfield projects?

A pipeline router for AI-coding workflows supports both greenfield and brownfield projects. It adapts the workflow by routing tasks based on the current project phase, applying governance checks and extension hooks regardless of the existing codebase maturity.

What is the best way to ensure traceability across AI coding pipelines?

Traceability across AI coding pipelines is ensured by routing work through issue-backed steps with governance checks before each transition. This enforces compliance and maintains a verifiable record from initial specification through end-to-end testing and retro.

How do I extend a development pipeline with custom sub-skills and subagents?

A development pipeline can be extended with custom sub-skills and subagents by leveraging its extension hooks. These hooks allow you to inject specialized routing logic or governance constraints, adapting the specify through retro workflow to specific project needs.

When should I not use an automated governance pipeline for AI coding?

An automated governance pipeline for AI coding may be unsuitable for highly exploratory or ad-hoc tasks that do not benefit from structured phase routing. If your work does not require issue-backed traceability or compliance checks, the overhead of specify through retro steps may be unnecessary.