What is the WHAT/WHY principle in this skill?

It is a core discipline where specifications define what the feature must do and why it is needed, while intentionally excluding 'how' it is implemented (such as specific algorithms or code) to keep the spec stable.

When should I use 'spec' instead of 'brainstorm'?

Use 'spec' when requirements are already clear and well-defined. Use 'brainstorm' if you need exploratory dialogue to figure out what needs to be built.

What is required to use this skill?

This skill requires the spec-kit plugin to be initialized in your project repository to provide the necessary templates and directory structures.

Does the spec skill generate source code?

No, the spec skill generates markdown-based specifications and contracts. Implementation is handled by separate skills like 'sdd:implement' after the spec is finalized.

Spec-Driven Development Creator

Name: Spec-Driven Development Creator
Author: rhuss

byrhuss

•

Productivity & Workflow

Generates formal, executable specifications from clear requirements following the WHAT/WHY principle to ensure implementation-agnostic standards.

About

The Spec skill empowers Claude Code with Specification-Driven Development (SDD) capabilities, allowing developers to transform clear requirements into structured, formal specifications. By utilizing the spec-kit toolset, it creates a stable source of truth that focuses entirely on functional requirements, behaviors, and success criteria while intentionally omitting implementation details. This approach ensures that specifications remain stable even as the underlying code evolves, facilitating better reviews, clearer architectural alignment, and more predictable feature implementation.

Key Features

Integrated soundness reviews to check for completeness, clarity, and testability
1 GitHub stars
Contextual validation against project-specific 'constitutions' and existing specs
Automated creation of feature directories, checklists, and contract files
Strict enforcement of the WHAT/WHY principle to separate requirements from implementation
Interactive specification generation using standardized spec-kit templates

Use Cases

Establishing stable API contracts and system behaviors before starting implementation
Documenting complex feature requirements to serve as a single source of truth for AI agents
Translating detailed PRDs or tickets into formal technical specifications

About

Key Features

Integrated soundness reviews to check for completeness, clarity, and testability
1 GitHub stars
Contextual validation against project-specific 'constitutions' and existing specs
Automated creation of feature directories, checklists, and contract files
Strict enforcement of the WHAT/WHY principle to separate requirements from implementation
Interactive specification generation using standardized spec-kit templates

Use Cases

Establishing stable API contracts and system behaviors before starting implementation
Documenting complex feature requirements to serve as a single source of truth for AI agents
Translating detailed PRDs or tickets into formal technical specifications