vibespec-init

Analyze a codebase and generate an initial specification suite with domain docs and ADR templates.

15|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/v0lka/skills --skill vibespec-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibespec-init
Source: https://github.com/v0lka/skills/tree/main/development/sdd/vibespec-init
Command: npx skills add https://github.com/v0lka/skills --skill vibespec-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize a specification system for a project from scratch. Analyzes the codebase to identify architectural layers, domains, boundaries, and key decisions, then generates the initial set of specs (META.md, WORKFLOW.md, INDEX.md, domain specs, contracts, architecture docs, ADR template). Use when bootstrapping specs for a new project, setting up documentation governance, or creating a spec system for an existing codebase that has none.

Core Features & Use Cases

  • Analyze the codebase to identify layers, domains, boundaries, and key decisions.
  • Generate the initial spec suite (META.md, WORKFLOW.md, INDEX.md, domain specs, contracts, architecture docs, ADR templates).
  • Use cases: bootstrapping specs for a new project, establishing documentation governance, or adding a spec system to an existing codebase with no specs.

Quick Start

Run vibespec-init at the repository root to bootstrap the complete specification system for your project.

Frequently Asked Questions about vibespec-init

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

FAQPage Schema
How do I bootstrap a specification system for an existing codebase?

Bootstrapping a specification system for an existing codebase involves analyzing the source code to identify architectural layers, domains, and boundaries, then generating the initial spec suite including META.md, WORKFLOW.md, and ADR templates.

What is the best way to generate architecture documentation from source code?

Generating architecture documentation from source code is done by analyzing the codebase to detect architectural layers and key decisions, then automatically generating domain specs, contracts, and ADR templates to establish documentation governance.

Can I use this to create ADR templates for new projects?

Yes, you can create ADR templates for new projects by running the initialization tool at the repository root, which bootstraps the complete specification system including architecture docs and decision records alongside domain specs.

Does this specification bootstrap tool work for projects with no prior documentation?

Yes, this specification bootstrap tool works specifically for existing codebases lacking governance or new projects with no prior documentation, analyzing the code to generate the initial deterministic spec suite from scratch.

When do I need to initialize a spec system using domain boundaries?

You need to initialize a spec system using domain boundaries when you want to establish deterministic documentation governance that accurately reflects your software architecture, ensuring specs and contracts map directly to identified domains.