Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Most software engineers using AI coding agents today prompt the agent to write code, then write a spec to match the code (or skip the spec entirely), wire a custom prompt template per AI agent (one template for Claude Code, another for Gemini CLI, another for Cursor, another for Copilot), scatter the project's non-negotiable principles across scattered docs, and rebuild the spec workflow on every
Who should use it
Who should skip it
Skip Spec Kit: GitHub's Official Spec-Driven Development Toolkit (Define the What Before the How) if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
Spec Kit: GitHub's Official Spec-Driven Development Toolkit (Define the What Before the How) is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-08 and last updated on 2026-07-08. The current verdict is 'try now' with a Gold tier and easy setup difficulty. Across RepoRadar's eight signals, Spec Kit: GitHub's Official Spec-Driven Development Toolkit (Define the What Before the How) is strongest on workflow potential (9.7) and practical usefulness (9.0) and weakest on maturity (6.7) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Spec Kit: GitHub's Official Spec-Driven Development Toolkit (Define the What Before the How) a composite score of 8.6 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 0.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The 118633* / last-pushed-2026-07-07 / MIT / not-archived repo is at active maintenance but the project is in active development -- the consumer SHOULD pin the spec-kit version and review the changelog; the consumer SHOULD note the slash commands require an AI coding agent (Claude Code + Gemini CLI + Cursor + Copilot) -- spec-kit is the meta-toolkit; the AI agent does the actual code generation; the consumer SHOULD note the shared constitution is a single file (`memory/constitution.md`) -- the consumer SHOULD review the constitution before scaffolding a new project.