github/spec-kit

💫 Toolkit to help you get started with Spec-Driven Development

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 11 minutes ago
Added to GitGenius on August 3rd, 2026
Created on August 21st, 2025
Open Issues & Pull Requests: 318 (+0)
GitHub issues: Enabled
Number of forks: 12,065
Total Stargazers: 134,075 (+0)
Total Subscribers: 691 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.6 hours
Mean response time: 6.4 days
90th percentile: 10.3 days
Tracked items: 1,417

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 93% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 27% of tracked open issues have had no activity in three months. Only 9% of issues opened in the past year have been closed. Three people close 81% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 150
New in 7 days: 34
Closed in 7 days: 29
Avg open age: 93 days
Stale 30+ days: 65
Stale 90+ days: 36

Recent activity

Opened in 7 days: 30
Closed in 7 days: 16
Comments in 7 days: 63
Events in 7 days: 193

Top labels

  • stale (433)
  • enhancement (291)
  • validation-passed (149)
  • extension-submission (123)
  • bug-assess (55)
  • preset-submission (50)
  • needs-verification (33)
  • needs-author-response (31)

Detailed Description

Spec Kit is an open source toolkit designed to enable Spec-Driven Development, a methodology that prioritizes defining specifications before implementation. The toolkit helps teams work with AI coding agents to build software by establishing clear requirements and technical plans upfront, then using those specifications to guide automated code generation. The project is written in Python and maintained by GitHub, with comprehensive documentation available through its GitHub Pages site.

The core philosophy of Spec-Driven Development, as presented in the repository, inverts traditional software development practices by making specifications executable and primary rather than treating them as secondary scaffolding. Instead of code being the main artifact, specifications become the foundation from which working implementations are directly generated. This approach is designed to work with any AI coding agent, whether CLI-based tools or IDE-integrated assistants.

Spec Kit provides a structured workflow through a series of slash commands that guide users through the development process. The essential commands include `/speckit.constitution` for establishing project principles, `/speckit.specify` for defining requirements, `/speckit.plan` for creating technical implementation plans, `/speckit.tasks` for breaking work into actionable items, and `/speckit.implement` for executing the planned work. Additional optional commands like `/speckit.clarify`, `/speckit.analyze`, and `/speckit.checklist` provide enhanced validation and quality assurance capabilities.

The toolkit supports integration with over 30 AI coding agents, accommodating both traditional slash-command interfaces and skills-based modes depending on agent capabilities. Users can install the Specify CLI through multiple methods, with the primary installation requiring the uv package manager. The project includes self-management capabilities for checking updates and upgrading the CLI.

Customization is a central feature of Spec Kit, enabled through two complementary systems: extensions and presets. Extensions allow teams to add new capabilities and commands, while presets enable customization of core templates and terminology. Project-local overrides provide a way to make one-off adjustments specific to individual projects. The repository maintains a community-driven ecosystem where users can contribute and share extensions, presets, bundles, and walkthroughs through the official documentation site.

The repository overlaps with other GitHub projects including gh-aw, solo-io/gloo, and microsoft/vscode through shared contributors, suggesting integration points and complementary tooling within the broader development ecosystem. The toolkit is positioned as an extensible, community-driven solution designed to scale across entire organizations, with role-based setup bundles available to accommodate different team structures and workflows.