specs-setup

Initializes a spec-driven project structure with templates for requirements and governance.

2|Updated Mar 11, 2026

Search Tags:#architecture #templates #spec-driven #requirements #PRD #project-setup #Vision

Ready to run

npx skills add https://github.com/b12consulting/skills --skill specs-setup

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Auto-detects missing specs folder and missing core documents (PRD.md, Vision.md, Architecture/).
Creates a standardized folder and document structure (specs/, specs/decisions, specs/tickets, etc.) using templates.
Validates prerequisites and prompts to establish coding standards before proceeding.
Serves as a reusable bootstrap for new projects requiring a formal specs-driven workflow.

Quick Start

Run the specs-setup skill to initialize the specs/ structure and template documents for a new project.

Frequently Asked Questions about specs-setup

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

FAQPage Schema

How do I set up a spec-driven project structure with a PRD and architecture documents?▼

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.

What is a spec-driven workflow for project requirements 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.

Do I need an existing specs folder to initialize spec-driven project templates?▼

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.

What's the best way to bootstrap a new project lacking formal requirements and architecture specs?▼

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.

What directories and files are created when bootstrapping a spec-driven project?▼

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.

When should I not use a spec-driven template workflow for project setup?▼

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.