spec-kit-workflow

Runs GitHub Spec Kit's gated spec-driven workflow from constitution through implementation convergence.

3|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/marcmarti9/agentit --skill spec-kit-workflow-marcmarti9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-kit-workflow
Source: https://github.com/marcmarti9/agentit/tree/main/skills/spec-kit-workflow
Command: npx skills add https://github.com/marcmarti9/agentit --skill spec-kit-workflow-marcmarti9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague feature prompts lead agents to code before requirements are settled, causing drift, rework, and unreviewable changes. This Skill enforces GitHub Spec Kit's gated spec-driven flow so a reviewed spec, plan, and task list exist before implementation begins. ## Core Features & Use Cases - Gated Workflow: Walks features through constitution, specify, clarify, plan, tasks, analyze, implement, and converge gates, blocking implementation while a gate is open. - Authority Order: Resolves conflicts between user constraints, project constitution, reviewed specs, plans, and existing code with an explicit precedence chain. - Host-Agnostic Operation: Uses /speckit.* slash commands when the host provides them, or writes the same Markdown artifacts directly when they do not. - Use Case: A user asks to build a multi-capability feature from a rough idea in a repo containing .specify/. The Skill writes a constitution, produces one spec per capability, resolves open questions, generates an ordered task list, and implements task by task with verification. ## Quick Start Ask the agent to run the Spec Kit gated workflow for the new feature, starting with a constitution and spec before any code is written.

Frequently Asked Questions about spec-kit-workflow

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

FAQPage Schema
How do I use GitHub Spec Kit for spec-driven development?▼

Run the gated flow in order: constitution, specify, clarify, plan, tasks, analyze, implement, then converge. Each gate produces a reviewable Markdown artifact, and implementation does not start until the spec and plan are reviewed and open questions are resolved.

What is the difference between Spec Kit workflow and generic spec-driven development?▼

Spec Kit workflow uses GitHub Spec Kit's artifact layout (.specify/, specs/<feature-id>/spec.md) and its specific gates and commands. The generic spec-driven-development skill applies when Spec Kit is not initialized; both may be selected but never as competing formats for one feature.

Does Spec Kit workflow require the specify-cli installation?▼

No. The CLI install via uv tool install specify-cli is an optional user choice. If the host lacks /speckit.* commands, the same gates run by writing the Markdown artifacts directly, since the gate is the contract, not the slash command.

When should I not use the Spec Kit workflow?▼

Skip it for typo fixes, one-line patches, and changes whose acceptance criteria are already explicit and local. Loading the full gated flow for a 20-minute change produces unnecessary overhead like a 40-task list.

Why does Spec Kit workflow block implementation on open questions?▼

Unresolved [NEEDS CLARIFICATION] items that affect architecture, data, auth, scope, or success criteria change what gets built. Guessing them away causes drift, so the clarify gate folds answers into the spec before planning begins.