spec-kit

# Specification-Driven Development (SDD)

Comprehensive implementation of GitHub's [spec-kit](https://github.com/github/spec-kit) methodology where specifications become executable, directly generating functional implementations.

**Source**: This skill is based on the official [GitHub spec-kit](https://github.com/github/spec-kit) project - an open-source toolkit that implements Specification-Driven Development.

## Quick Start

When a user needs to develop a feature or start a project, follow this workflow:

1. **Constitution** - Establish project principles (`/speckit.constitution`)
2. **Specification** - Define requirements (what and why, not how) (`/speckit.specify`)
3. **Clarification** - Address ambiguities with 5 targeted questions (`/speckit.clarify` - optional)
4. **Planning** - Create technical implementation strategy (`/speckit.plan`)
5. **Tasks** - Generate executable task breakdown (`/speckit.tasks`)
6. **Implementation** - Execute according to plan (`/speckit.implement`)

**Note**: The official spec-kit includes slash commands for Claude Code integration. This skill provides the same workflow without requiring the CLI installation.

## Decision Tree

```text
SDD Request → What stage?
    │
    ├─ New Project / Feature
    │   ├─ Create constitution.md (principles)
    │   ├─ Write spec.md (requirements)
    │   ├─ Run clarification (5 questions)
    │   ├─ Generate plan.md (technical)
    │   ├─ Create tasks.md (breakdown)
    │   └─ Implement according to tasks
    │
    ├─ Existing Specifications
    │   ├─ Analyze consistency across artifacts
    │   ├─ Identify gaps or ambiguities
    │   └─ Suggest improvements
    │
    └─ Documentation Only
        ├─ Extract specifications from code
        └─ Generate reverse-engineered docs
```

## Core Philosophy

Spec-Kit inverts traditional development:

- **Traditional**: Write code → Document later
- **Spec-Driven**: Write specifications → Generate code

Specifications are the **first artifact**, and cod