{
  "id": "page:library-spec-kit",
  "_kind": "Page",
  "_file": "wiki/library/spec-kit.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "title": "Spec Kit Methodology (Library)",
    "displayName": "Spec Kit Methodology (Library)",
    "slug": "library/spec-kit",
    "articlePath": "wiki/library/spec-kit.md",
    "article": "\n# Spec Kit Methodology\n\n**Source**: [github/spec-kit](https://github.com/github/spec-kit) by GitHub\n**Category**: Spec-Driven Development / Progressive Refinement\n**License**: See upstream repository\n\n## Overview\n\nSpec Kit implements Spec-Driven Development, where specifications define **what** before **how**, with multi-step refinement rather than one-shot generation. The pipeline progressively refines intent into code: constitution -> specification -> plan -> tasks -> implementation, with quality gates and cross-artifact consistency analysis at each transition.\n\n## Core Principles\n\n- **Specifications as first-class dev artifacts**: Specs are not throwaway documents; they govern the entire pipeline\n- **Progressive refinement**: Intent -> spec -> plan -> tasks -> code, each stage adding precision\n- **Technology independence**: Works across any tech stack, framework, or language\n- **Multi-mode support**: Greenfield (0-to-1), brownfield (iterative enhancement), and creative exploration\n- **Quality-gated convergence**: Checklist validation with remediation loops before completion\n- **Human approval gates**: Explicit approval between every major phase transition\n\n## Process Files\n\n| Process | File | Description | Task Count |\n|---------|------|-------------|------------|\n| Orchestrator | `spec-kit-orchestrator.js` | Full pipeline: constitution -> specify -> plan -> tasks -> implement | 8 |\n| Specification | `spec-kit-specification.js` | Constitution + specification + clarification workflow | 7 |\n| Planning | `spec-kit-planning.js` | Planning + task breakdown + analysis | 7 |\n| Implementation | `spec-kit-implementation.js` | Implementation + quality validation + checklist | 7 |\n\n## Skills Catalog\n\n| Skill | Directory | Description |\n|-------|-----------|-------------|\n| constitution-creation | `skills/constitution-creation/` | Establish project governing principles |\n| specification-writing | `skills/specification-writing/` | Write requirements and user stories |\n| planning-design | `skills/planning-design/` | Technical architecture and strategy design |\n| task-decomposition | `skills/task-decomposition/` | Convert plans into actionable dev tasks |\n| implementation-execution | `skills/implementation-execution/` | Execute tasks to build features |\n| cross-artifact-analysis | `skills/cross-artifact-analysis/` | Consistency and coverage assessment |\n| quality-checklist | `skills/quality-checklist/` | Custom quality validation checklists |\n\n## Agents Catalog\n\n| Agent | Directory | Role |\n|-------|-----------|------|\n| constitution-architect | `agents/constitution-architect/` | Governing Principles Architect |\n| specification-writer | `agents/specification-writer/` | Requirements & User Stories Writer |\n| technical-planner | `agents/technical-planner/` | Architecture & Tech Stack Designer |\n| task-analyst | `agents/task-analyst/` | Task Decomposition Analyst |\n| implementation-engineer | `agents/implementation-engineer/` | Code Generation Engineer |\n| consistency-analyzer | `agents/consistency-analyzer/` | Cross-Artifact Consistency Analyzer |\n| quality-auditor | `agents/quality-auditor/` | Checklist Validation Auditor |\n\n## Workflow Lifecycle\n\n```\nConstitution -> Specification -> [Clarification] -> Planning -> Task Breakdown -> Analysis -> Implementation -> Checklist\n     |                |                                 |              |                           |               |\n  (review)        (review)                          (review)       (review)                    (review)       (remediation loop)\n```\n\nQuality gates applied throughout:\n- `cross-artifact-analysis` - Consistency and coverage checked before implementation\n- `quality-checklist` - Custom validation with convergence loop after implementation\n- Human approval at every phase boundary\n\n## Development Modes\n\n| Mode | Description | Use Case |\n|------|-------------|----------|\n| Greenfield | Full pipeline from scratch (0-to-1) | New projects, new features |\n| Brownfield | Iterative enhancement with existing codebase | Enhancements, refactors |\n| Creative | Exploratory specification with flexible constraints | Prototypes, experiments |\n\n## Output Artifacts\n\n- `speckit.constitution` - Project governing principles\n- `speckit.specification` - Feature requirements and user stories\n- `speckit.plan` - Technical architecture and implementation strategy\n- `speckit.tasks` - Actionable development task list\n- `speckit.analysis` - Cross-artifact consistency report\n- `speckit.checklist` - Quality validation results\n\n## Philosophy\n\n- **Define what before how** - Specifications precede implementation\n- **Refine progressively** - Each phase adds precision to the previous\n- **Validate continuously** - Cross-artifact analysis ensures consistency\n- **Scale to any stack** - Technology-independent methodology\n- **Preserve human judgment** - Quality gates are approval points, not blockers\n",
    "documents": [
      "specialization:spec-kit"
    ]
  },
  "outgoingEdges": [
    {
      "from": "page:library-spec-kit",
      "to": "specialization:spec-kit",
      "kind": "documents"
    }
  ],
  "incomingEdges": [
    {
      "from": "page:index",
      "to": "page:library-spec-kit",
      "kind": "contains_page"
    }
  ]
}