spec-driven-development

Translate structured specifications into executable artifacts through a seven-phase workflow.

4|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/89jobrien/steve --skill spec-driven-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/89jobrien/steve/tree/main/steve/skills/spec-driven-development
Command: npx skills add https://github.com/89jobrien/steve --skill spec-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill implements SpecKit-based methodology to convert structured specifications into executable artifacts with governance and phase-based execution.

Core Features & Use Cases

  • Seven-Phase Workflow: Initialization to implementation
  • Governance & Quality Gates: Constitution, planning, validation
  • Artifact Generation: Spec, plan, tasks, research outputs
  • Coordination Across Agents: Multi-agent collaboration

Quick Start

Initialize a new project with the 7-phase SpecKit workflow and generate initial specs.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
How do I convert specifications into executable software artifacts?

Spec-driven development translates structured specifications into executable artifacts through a seven-phase workflow—initialization through implementation—with governance gates and cross-artifact validation to ensure quality and consistency across enterprise-scale projects.

What is spec-driven development and when should I use it?

Spec-driven development is a methodology that converts detailed specifications into code and deliverables with built-in governance checkpoints. Use it for enterprise projects requiring multi-agent coordination, phase-based execution, and auditable handoffs from planning to implementation.

How do I coordinate multiple agents across specification phases?

The seven-phase workflow enables multi-agent orchestration by defining clear governance gates and artifact dependencies at each stage—from constitution through implementation—so teams collaborate with structured handoffs and validation rules rather than ad hoc communication.

Can I enforce quality gates on specifications before implementation begins?

Yes. The methodology includes governance and validation gates that verify specifications meet requirements before proceeding to implementation, preventing defects from flowing downstream and reducing rework cycles in multi-phase development.

What artifacts does a spec-driven workflow generate?

The workflow generates specifications, plans, task breakdowns, and research outputs across its seven phases, with cross-artifact validation ensuring each artifact aligns with prior phases and supports downstream implementation teams.