spec-driven

Organize project requirements and decisions within a specs/ folder.

2|Updated Mar 11, 2026

Search Tags:#architecture #spec-driven #adr #vision #tickets #prd #specs

Ready to run

npx skills add https://github.com/b12consulting/skills --skill spec-driven-b12consulting

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven project management standardizes how projects organize requirements, decisions, and governance within a specs/ folder, serving as the project’s single source of truth.

Core Features & Use Cases

Defines a consistent specs folder structure and governance for artifacts (Vision.md, PRD.md, Goals.md, Architecture, Glossary, Changelog, ADRs, and Tickets).
Enables traceability and accountability by documenting decisions in Architecture Decision Records and linking them to tickets.
Provides drift-detection guidance for keeping code and specs aligned and facilitating ADR-driven changes.

Quick Start

Create a specs folder in your project and start documenting Vision, PRD, Goals, Architecture, Glossary, Changelog, ADRs, and Tickets using the folder structure described.

Frequently Asked Questions about spec-driven

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

FAQPage Schema

What is spec-driven project management and how does it organize project artifacts?▼

Spec-driven project management organizes requirements, decisions, and governance within a specs/ folder to serve as the project’s single source of truth. It standardizes artifacts like Vision.md, PRD.md, Goals.md, Architecture, Glossary, Changelog, ADRs, and Tickets.

How do I structure a specs folder to maintain a single source of truth for my project?▼

To structure a specs folder, create files for Vision.md, PRD.md, Goals.md, Architecture, Glossary, Changelog, ADRs, and Tickets. This defined folder structure supports governance, accountability, and traceability across the project lifecycle.

How do Architecture Decision Records (ADRs) link to tickets in a specs-driven workflow?▼

Architecture Decision Records (ADRs) document decisions within the specs/ folder to enable traceability and accountability. They are explicitly linked to tickets, facilitating governance and tracking ADR-driven changes throughout the project.

How do I manage drift between code and specs in a spec-driven methodology?▼

To manage drift between code and specs, apply drift-detection guidance within the spec-driven methodology. This keeps code and specs aligned while facilitating structured, ADR-driven changes to maintain project consistency.

Does spec-driven project management work for projects without a pre-existing specs folder?▼

Spec-driven project management applies to projects that create a specs/ folder. If your project lacks this directory, you must establish it first to begin documenting artifacts and applying the governance structure.

Why use a spec-driven approach over informal project documentation?▼

A spec-driven approach provides a consistent folder structure and governance for artifacts, unlike informal documentation. It establishes a single source of truth, ensuring accountability, traceability, and alignment between code and project specifications.