vibespec-create

Organize project-spec documents by automating template selection and registration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to create consistent specification documents across domains, contracts, and ADRs, leading to fragmentation and misaligned references.

Core Features & Use Cases

  • Enforces standard templates for Domain READMEs, Domain Details, Contracts, Architecture notes, and ADRs.
  • Handles naming conventions, file placement, cross-references, and updates INDEX.md automatically.
  • Use case: Create a new Domain Detail spec for a new component and have it automatically registered and cross-linked.

Quick Start

Create a new domain detail spec in specs/domains/<domain>/<component>.md and update specs/INDEX.md accordingly.

Frequently Asked Questions about vibespec-create

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

FAQPage Schema
How do I standardize architecture and domain spec documents across a project?

To standardize architecture and domain spec documents, apply automated template selection to enforce consistent structure for Domain READMEs, Contracts, and ADRs, validating required frontmatter and cross-references automatically across the project.

What is the best way to generate and register a new ADR or domain detail?

The best way to generate and register ADRs or domain details is to apply standard templates that enforce naming conventions and file placement, then automatically update INDEX.md to register and cross-link the new spec document.

How do I keep spec INDEX.md updated when adding new domain documentation?

To keep INDEX.md updated when adding new domain documentation, automate the indexing process during spec creation so that new files are automatically registered and cross-linked according to the project's naming conventions.

Can I validate required frontmatter and section structure for architecture notes automatically?

Yes, you can validate required frontmatter and section structure for architecture notes automatically by applying standardized templates during spec creation, which checks that all required metadata and structural sections are present.

Does this approach work for managing both contracts and domain READMEs together?

Yes, this approach works for managing contracts and domain READMEs together by enforcing a unified template structure that handles cross-references and file placement across all document types within the same specs directory.