spec-driven-development

Name: spec-driven-development
Availability: InStock
Author: shirulot

Enforce a gated specification workflow before software implementation.

Updated Jul 6, 2026

Search Tags:#workflow #planning #development #architecture #specification #engineering

Ready to run

npx skills add https://github.com/shirulot/codex-skill --skill spec-driven-development-shirulot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/shirulot/codex-skill/tree/main/spec-driven-development
Command: npx skills add https://github.com/shirulot/codex-skill --skill spec-driven-development-shirulot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity and architectural drift by forcing the creation of a validated, structured specification before any code is written, ensuring the AI and the human engineer are perfectly aligned on project goals.

Core Features & Use Cases

Structured Specification: Generates a comprehensive spec covering objectives, tech stack, commands, project structure, and boundaries.
Gated Workflow: Enforces a four-phase process (Specify, Plan, Tasks, Implement) that requires human validation at every stage.
Use Case: When starting a complex new feature, use this skill to define success criteria and architectural boundaries, preventing wasted effort on misaligned implementation.

Quick Start

Initiate a new project specification by asking the skill to help you draft a spec document for the new feature you are about to build.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

What is spec-driven development and how does it structure the software lifecycle?▼

Spec-driven development standardizes the software lifecycle by mandating a formal specification phase before implementation. It applies to new projects and complex features, enforcing a gated workflow of specification, planning, task breakdown, and incremental implementation.

How do I create a structured specification for a complex software feature?▼

To create a structured specification, initiate a project specification phase to define objectives, tech stack, commands, project structure, and boundaries. This ensures engineers and AI are aligned on goals before writing code.

When should I use a gated workflow for software architecture changes?▼

Use a gated workflow for software architecture changes when requirements are ambiguous or drift is likely. It enforces human validation across four phases—specify, plan, tasks, and implement—preventing wasted effort on misaligned development.

What's the best way to prevent architectural drift in new project initialization?▼

The best way to prevent architectural drift during new project initialization is enforcing a validated, structured specification before coding. This aligns human engineers and AI on project goals, tech stack, and architectural boundaries.

Can I use spec-driven development for incremental implementation of existing projects?▼

Yes, you can use spec-driven development for incremental implementation of existing projects. It enforces a gated workflow requiring human validation at the planning, task breakdown, and implementation stages to maintain alignment.

Why does my software development workflow suffer from ambiguity and misaligned implementation?▼

Software development workflows suffer from ambiguity and misaligned implementation when they skip a validated specification phase. Forcing the creation of a structured spec before coding ensures all contributors share the same project boundaries and success criteria.