Skip to main content
GitHub Spec Kit is an open toolkit for spec-driven development. Its core sequence is Specify, Plan, Tasks, and Implement, with a project constitution and optional clarification and analysis. Each feature keeps a directory of Markdown artifacts that feed the next phase. Source stamp: github/spec-kit at 57cc518d, reviewed July 18, 2026. Repository license: MIT.

​
Artifact tree

The official templates cover the constitution, specification, plan, and tasks.

​
Workflow and conventions

The constitution records principles, constraints, quality gates, and governance. The feature specification uses independently testable user stories, scenarios, edge cases, requirement IDs, assumptions, and measurable outcomes. The plan captures technical context and checks the design against the constitution before producing supporting research, data, contract, and quickstart artifacts. Tasks use stable IDs such as T001, optional parallel markers, user-story labels, and exact paths. This makes dependencies and coverage visible without requiring one continuous prose plan.

​
Review and persistence

Specification quality can be checked before implementation planning, and the plan can be analyzed against requirements and the constitution. Spec Kit’s persistence guidance discusses living specs and flow-forward or flow-back updates instead of prescribing one universal maintenance rule.

​
Inspect the same-case output

Inspect the complete generated Spec Kit artifact tree for reliable webhook delivery. It contains the constitution, specification, checklist, plan, research, data model, contracts, quickstart, and 69-task list produced by the planning flow.

​
Choose Spec Kit when

  • a feature directory should be portable across supported coding agents;
  • requirements, design, tasks, and supporting technical artifacts need distinct roles;
  • a project constitution should constrain feature plans; and
  • stable requirement and task IDs help review and traceability.
Spec Kit calls its product-intent artifact a feature specification rather than a PRD. See PRD vs technical specification vs implementation plan for the role-based distinction, GitHub Spec Kit vs Kiro Specs for the framework comparison, and the Plannotator-authored technical specification template. Reviewed July 19, 2026. Researched and maintained by the Plannotator documentation team. GitHub and Spec Kit are named for identification; Plannotator is not affiliated with or endorsed by GitHub.
Last modified on July 20, 2026