spec-driven-development

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

Define detailed software specifications with six core sections and a four-phase workflow.

13|3|Updated May 12, 2026

Search Tags:#workflow #planning #specification #requirements #spec #software-development

Ready to run

npx skills add https://github.com/kevinnft/ai-agent-skills --skill spec-driven-development-kevinnft

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams define a clear, testable specification before writing code, reducing misinterpretations and rework.

Core Features & Use Cases

Four-phase gated workflow (SPECIFY → PLAN → TASKS → IMPLEMENT) to align stakeholders and drive orderly delivery.
A complete spec template covering Objective, Tech Stack, Commands, Project Structure, Code Style, Testing, and Boundaries.
Open-question handling and living documentation to keep decisions current and auditable.

Quick Start

Draft a spec using the template before coding to align goals and define acceptance criteria.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

What is a spec-driven development workflow and when do I need it?▼

Spec-driven development defines a detailed specification document before writing code. You need it for early-stage projects, ambiguous requirements, or architectural decisions to reduce misinterpretations and rework.

How do I write a software specification document before coding?▼

Write a software specification using a template covering Objective, Tech Stack, Commands, Project Structure, Code Style, Testing Strategy, and Boundaries. This ensures structured planning and explicit success criteria before implementation.

What is the best way to manage software development requirements and tasks?▼

The best way to manage software requirements is a four-phase gated workflow: Specify, Plan, Tasks, and Implement. This aligns stakeholders and drives orderly delivery through open-question handling and living documentation.

Can I use specification planning for early-stage projects with ambiguous requirements?▼

Yes, specification planning applies directly to early-stage projects and ambiguous requirements. It enforces structured validation and defines explicit success criteria to align goals before any coding begins.

What should a software specification template include to align stakeholder goals?▼

A software specification template should include six core sections: Objective, Tech Stack, Commands, Project Structure, Code Style, and Testing Strategy. It must also define explicit boundaries and acceptance criteria to align stakeholders.

Why does codeless specification planning reduce rework in software engineering?▼

Specification planning reduces rework by enforcing a gated Specify to Implement workflow. It captures open questions and maintains living documentation to keep architectural decisions current, testable, and auditable before coding.