speckit-workflow

# Spec Kit Workflow

GitHub Spec Kit 5-phase specification-driven development workflow.

## When to Use This Skill

**Keywords:** Spec Kit, 5-phase workflow, constitution, specify, plan, tasks, implement, feature.md, design.md, tasks.md, specification workflow, GitHub Spec Kit, constitution.md, phased development

**Use this skill when:**

- Implementing specification-driven development workflows
- Creating or updating project constitution files
- Generating feature specifications from requirements
- Creating implementation plans from specifications
- Breaking down plans into task lists
- Following the full Specify → Plan → Tasks → Implement cycle

## Workflow Overview

```text
Phase 0: Constitution (One-time setup)
    ↓
Phase 1: Specify (Generate feature.md)
    ↓
Phase 2: Plan (Generate design.md)
    ↓
Phase 3: Tasks (Generate tasks.md)
    ↓
Phase 4: Implement (Code with guidance)
```

## Phase 0: Constitution

### Purpose

Establish project-wide principles, constraints, and non-functional requirements that guide ALL specifications.

### File: `.constitution.md`

```markdown
# Project Constitution

## Core Principles
- <principle 1>
- <principle 2>

## Technical Constraints
- <constraint 1>
- <constraint 2>

## Quality Standards
- <standard 1>
- <standard 2>

## Non-Functional Requirements
- Performance: <requirement>
- Security: <requirement>
- Accessibility: <requirement>
```

### Constitution Checklist

- [ ] Core development principles defined
- [ ] Technical constraints documented
- [ ] Quality standards specified
- [ ] Non-functional requirements listed
- [ ] Team conventions captured
- [ ] Dependencies and integration requirements noted

### When to Update

Update the constitution when:

- New non-functional requirements emerge
- Team conventions change
- Architectural decisions impact all features
- Project-wide constraints are added

## Phase 1: Specify

### Purpose

Transform a feature request or user story into a structured specification with EARS re