spec-kit

Route requests to spec-kit sub-skills and enforce artifact-order gates.

5|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/ahgraber/skills --skill spec-kit-ahgraber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-kit
Source: https://github.com/ahgraber/skills/tree/main/skills/spec-kit
Command: npx skills add https://github.com/ahgraber/skills --skill spec-kit-ahgraber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Route requests to the correct spec-kit-* sub-skill and enforce artifact-order gates, simplifying governance and remediation work across complex Spec Kit workflows.

Core Features & Use Cases

  • Routes feature requests to the smallest installed spec-kit-* skill to minimize scope and risk.
  • Enforces artifact-order gates and records deviations or risks when a different route is chosen.
  • Provides a centralized routing capability for governance, specify, clarify, plan, tasks, analyze, and reconcile steps.

Quick Start

Route a feature request to the appropriate spec-kit sub-skill using the router and enforce artifact gates.

Frequently Asked Questions about spec-kit

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

FAQPage Schema
How do I route feature requests to the correct workflow sub-skill?

Route feature requests by directing them to the smallest installed sub-skill to minimize scope and risk. The router evaluates the request and enforces artifact-order gates before allowing downstream workflow steps to proceed.

What is artifact-order gate validation in workflow routing?

Artifact-order gate validation guarantees prerequisites exist before routing to downstream steps. It enforces the correct sequence across governance, specify, clarify, plan, tasks, analyze, and reconcile workflows to prevent process deviations.

How do I enforce prerequisites before running downstream plan and tasks workflows?

Enforce prerequisites by applying the router to validate artifact-order gates before plan and tasks workflows. It checks for required artifacts and documents deviations or risks if a different route is chosen.

Can I document deviations and risks when choosing a different workflow route?

Yes, you can document deviations and risks when choosing a different route. The router records these exceptions during gate validation to maintain governance and ensure consistent routing across the workflow suite.

Does workflow routing require any specific dependencies or environments?

Workflow routing requires no external dependencies. It relies on shared spec-kit resources within your environment to ensure consistent governance and routing across the installed sub-skills.

When should I not use centralized workflow routing for governance tasks?

Avoid centralized routing when your governance tasks fall outside the supported specify, clarify, plan, tasks, analyze, and reconcile workflows. The router is designed specifically to enforce artifact-order gates within these defined steps.