Initializes a spec-driven project structure with templates for requirements and governance.
npx skills add https://github.com/b12consulting/skills --skill specs-setup
Please help me install this Agent Skill. Skill: specs-setup Source: https://github.com/b12consulting/skills/tree/main/skills/specs-setup Command: npx skills add https://github.com/b12consulting/skills --skill specs-setup
Initialize the spec-driven project methodology when specs/ is absent or critical files like PRD.md, Vision.md, or Architecture/ are missing. This setup creates a structured foundation for requirements gathering, planning, and task management.
Run the specs-setup skill to initialize the specs/ structure and template documents for a new project.
High-intent search queries and answers about installing and using this skill.
To set up a spec-driven project structure, you need to initialize a standardized directory containing template documents like PRD.md, Vision.md, and an Architecture folder. This creates a structured foundation for requirements gathering, planning, and task management.
A spec-driven workflow is a methodology that uses structured specification documents, such as a PRD and Vision, to guide project development. It establishes a formal baseline for requirements gathering, architectural decisions, and governance before coding begins.
No, you do not need an existing specs folder. The initialization process is designed to auto-detect when the specs directory or critical files like PRD.md are missing, and it will automatically create the required folders and template documents.
The best way to bootstrap a project lacking formal specs is to run an automated setup that validates prerequisites and generates a standardized folder structure. This wires in spec-driven templates for requirements, architecture, and governance to guide subsequent work.
Bootstrapping a spec-driven project creates a standardized directory structure including specs/, specs/decisions, and specs/tickets. It also generates core template documents such as PRD.md, Vision.md, and Architecture files to formalize project planning.
You should not use a spec-driven template workflow if your project does not require formal requirements gathering, standardized architecture documentation, or structured task governance. It is specifically designed for new projects needing a formalized, specs-driven foundation.
4tikhonovInitialize a FIRE project by detecting workspace type and generating standards templates.
fcastrilloGenerate governance documents and a knowledge graph for new projects.
SoundBlasterManage SPECS/Workplan.md tasks across phases, backlogs, and dependencies.
Jia-Hong-PengGenerate structured implementation plans from spec.md files using spec-kit workflows.
