Organize project requirements and decisions within a specs/ folder.
npx skills add https://github.com/b12consulting/skills --skill spec-driven-b12consulting
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
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.
Create a specs folder in your project and start documenting Vision, PRD, Goals, Architecture, Glossary, Changelog, ADRs, and Tickets using the folder structure described.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
b12consultingInitializes a spec-driven project structure with templates for requirements and governance.
CoorpAcademyParse Jira tickets to extract requirements and generate developer summaries.
ccfDocument architectural decisions with a MADR-style template and lifecycle.
NirajkashyapMaintain a persistent Obsidian wiki with frontmatter metadata and cross-linking.
