Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · Spec Kit Methodology (Library)
page:library-spec-kita5c.ai
Search record views/
Record · tabs

Available views

II.Record viewspp. 1 - 1
overviewarticlejsongraph
III.Related pagespp. 1 - 1
II.
Page reference

page:library-spec-kit

Reading · 3 min

Spec Kit Methodology (Library) reference

Spec 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.

Pagewiki/library/spec-kit.mdOutgoing · 1Incoming · 1

Spec Kit Methodology

**Source**: github/spec-kit by GitHub **Category**: Spec-Driven Development / Progressive Refinement **License**: See upstream repository

Overview

Spec 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.

Core Principles

  • **Specifications as first-class dev artifacts**: Specs are not throwaway documents; they govern the entire pipeline
  • **Progressive refinement**: Intent -> spec -> plan -> tasks -> code, each stage adding precision
  • **Technology independence**: Works across any tech stack, framework, or language
  • **Multi-mode support**: Greenfield (0-to-1), brownfield (iterative enhancement), and creative exploration
  • **Quality-gated convergence**: Checklist validation with remediation loops before completion
  • **Human approval gates**: Explicit approval between every major phase transition

Process Files

ProcessFileDescriptionTask Count
Orchestratorspec-kit-orchestrator.jsFull pipeline: constitution -> specify -> plan -> tasks -> implement8
Specificationspec-kit-specification.jsConstitution + specification + clarification workflow7
Planningspec-kit-planning.jsPlanning + task breakdown + analysis7
Implementationspec-kit-implementation.jsImplementation + quality validation + checklist7

Skills Catalog

SkillDirectoryDescription
constitution-creationskills/constitution-creation/Establish project governing principles
specification-writingskills/specification-writing/Write requirements and user stories
planning-designskills/planning-design/Technical architecture and strategy design
task-decompositionskills/task-decomposition/Convert plans into actionable dev tasks
implementation-executionskills/implementation-execution/Execute tasks to build features
cross-artifact-analysisskills/cross-artifact-analysis/Consistency and coverage assessment
quality-checklistskills/quality-checklist/Custom quality validation checklists

Agents Catalog

AgentDirectoryRole
constitution-architectagents/constitution-architect/Governing Principles Architect
specification-writeragents/specification-writer/Requirements & User Stories Writer
technical-planneragents/technical-planner/Architecture & Tech Stack Designer
task-analystagents/task-analyst/Task Decomposition Analyst
implementation-engineeragents/implementation-engineer/Code Generation Engineer
consistency-analyzeragents/consistency-analyzer/Cross-Artifact Consistency Analyzer
quality-auditoragents/quality-auditor/Checklist Validation Auditor

Workflow Lifecycle

Code
Constitution -> Specification -> [Clarification] -> Planning -> Task Breakdown -> Analysis -> Implementation -> Checklist
     |                |                                 |              |                           |               |
  (review)        (review)                          (review)       (review)                    (review)       (remediation loop)

Quality gates applied throughout:

  • cross-artifact-analysis - Consistency and coverage checked before implementation
  • quality-checklist - Custom validation with convergence loop after implementation
  • Human approval at every phase boundary

Development Modes

ModeDescriptionUse Case
GreenfieldFull pipeline from scratch (0-to-1)New projects, new features
BrownfieldIterative enhancement with existing codebaseEnhancements, refactors
CreativeExploratory specification with flexible constraintsPrototypes, experiments

Output Artifacts

  • speckit.constitution - Project governing principles
  • speckit.specification - Feature requirements and user stories
  • speckit.plan - Technical architecture and implementation strategy
  • speckit.tasks - Actionable development task list
  • speckit.analysis - Cross-artifact consistency report
  • speckit.checklist - Quality validation results

Philosophy

  • **Define what before how** - Specifications precede implementation
  • **Refine progressively** - Each phase adds precision to the previous
  • **Validate continuously** - Cross-artifact analysis ensures consistency
  • **Scale to any stack** - Technology-independent methodology
  • **Preserve human judgment** - Quality gates are approval points, not blockers

Article source

The article body is owned directly by this record.

Related pages

No related wiki pages for this record.

Shortcuts

Open overview
Open JSON
Open graph