spec

Automates a spec workflow driven by YAML frontmatter validation and DESIGN.md documentation.

77|13|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/KerberosClaw/kc_ai_skills --skill spec-kerberosclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/KerberosClaw/kc_ai_skills/tree/main/spec
Command: npx skills add https://github.com/KerberosClaw/kc_ai_skills --skill spec-kerberosclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven development solves the problem of starting without clear requirements by providing a structured lifecycle that turns fuzzy ideas into concrete, verifiable specifications.

Core Features & Use Cases

  • Unified lifecycle across discovery, spec creation, planning, and verification.
  • Self-review with anti-sycophancy rules to surface gaps and inconsistencies.
  • Reusable templates and persistent design docs to maintain cross-project context.

Quick Start

Start a new spec for a feature by running /spec and describe the goal in one sentence.

Frequently Asked Questions about spec

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

FAQPage Schema
What is spec-driven development and how does it turn fuzzy requirements into trackable deliverables?

Spec-driven development provides a structured lifecycle that converts fuzzy ideas into concrete, verifiable specifications. It automates a rigorous workflow across discovery, design, spec creation, planning, and task execution to produce structured, trackable deliverables.

How do I start a spec for a new software feature?

To start a spec for a new feature, run the /spec command and describe your goal in a single sentence. The workflow then automatically applies frontmatter validation and generates the necessary structured documents.

Can I use this spec workflow for both small features and large multi-module projects?

Yes, this spec workflow applies to both small features and large multi-module projects. It scales across the entire project lifecycle by enforcing frontmatter validation and maintaining a persistent design document for cross-project context.

How does the spec workflow maintain design decisions across different stages of development?

The spec workflow maintains design decisions by creating and updating a persistent docs/DESIGN.md file. This document serves as a reference point throughout the discovery, spec creation, planning, and task execution phases to preserve cross-project context.

Does the spec workflow include any automated checks for requirement gaps or inconsistencies?

Yes, the spec workflow includes a self-review mechanism with anti-sycophancy rules. This automated check surfaces gaps and inconsistencies in your requirements, ensuring fuzzy ideas are accurately converted into verifiable specifications.

What format does the spec workflow use for validating created specifications?

The spec workflow uses YAML-frontmatter-driven validation for created specifications. It automatically generates files under the specs/ directory and enforces this frontmatter structure to maintain rigorous, trackable deliverables.