GitHub Spec Kit
Ranked 2 of 3 spec frameworks by recommenders
Free GitHub toolkit that makes AI coding agents write a spec and plan before coding, praised for consistent results. Critics find it heavy-handed and generating many markdown files.
Free GitHub toolkit that makes AI coding agents write a spec and plan before coding, praised for consistent results. Critics find it heavy-handed and generating many markdown files.
61 people gave an opinion
- recommend it
- 39
- criticize it
- 22
- approval share
- 64%
Recommended in 10 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: not recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 39 people recommend itNeeds 10 or more, met.
- 1.7 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 10 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Structured planning before implementation
“It helps tremendously for facilitating a process around gathering requirements, doing research, planning, breaking into tasks, and finally implementing.”
Comment from 13 Dec 2025 in “Ask HN: How can I get better at using AI for programming?” “It is setting a baseline of how the LLM should engage with a project which is pretty critical to getting the highest quality output”
Comment from 16 Nov 2025 in “Spec-Driven Development: The Waterfall Strikes Back” “It's a project out of Microsoft/Github that encodes a rigorous spec-then-implement multi pass workflow.”
Comment from 8 Jan 2026 in “Opus 4.5 is going to change everything” Works on brownfield codebases
“tools like spec kit give reliably good results in brownfield codebases”
Comment from 3 Feb 2026 in “Ask HN: Are you still using spec driven development?” “spec-kit is very helpful for both green/brown field projects”
Comment from 5 Feb 2026 in “Ask HN: Are you still using spec driven development?” Saves tokens and time
“Helps me save tokens as well. Again, the discipline is the important bit”
Comment from 17 Sep 2026 in “OpenSpec – A lightweight and configurable AI spec framework” “Saves a ton of tokens and is reasonably quick”
Comment from 2 Mar 2026 in “If AI writes code, should the session be part of the commit?” Consistent output across features
“I can give it two fairly simple prompts & get a reasonably complex result.”
Comment from 15 Nov 2025 in “Spec-Driven Development: The Waterfall Strikes Back” “It has been great at keeping the code consistent across features.”
Comment from 11 May 2026 in “I'm going back to writing code by hand”
What people warn about
Each mark is one comment
Heavy-handed and unwieldy workflow
“I think spec-kit is an interesting idea but too heavy handed”
Comment from 15 Nov 2025 in “Spec-Driven Development: The Waterfall Strikes Back” “I think I just found this experience with SDD quite heavy-handed and the workflow unwieldy.”
Comment from 15 Nov 2025 in “Spec-Driven Development: The Waterfall Strikes Back” Lots of markdown, little code
“every PR has hundreds, if not thousands, of lines of markdown comitted to the repo per ticket”
Comment from 15 Mar 2026 in “Ask HN: How is AI-assisted coding going for you professionally?” “spec-kit produces a lot of markdown files and little source code”
Comment from 22 Mar 2026 on Hacker News Ambiguity moved rather than removed
“Spec driven development tools like SpecKit, Kiro that promise English as being sufficient for LLM generated code”
Comment from 24 Jan 2026 in “After two years of vibecoding, I'm back to writing by hand [video]” “You are just moving ambiguity and code review from one place to another without really gaining anything.”
Comment from 17 Sep 2026 in “OpenSpec – A lightweight and configurable AI spec framework”
Other spec frameworks people recommend
The two most recommended other spec frameworks, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| OpenSpec | 49 | 20 | 71% | 10 | — | Approved |
| GitHub Spec KitThis page | 39 | 22 | 64% | 10 | — | — |
| Verified Spec-Driven Development (VSDD) | 5 | 1 | 83% | 3 | — | — |
What people said
40 of the 68 comments that mention it, newest first. Each links to the original comment.
“SpecKit is a fairly advanced process for changing specs”
“There is a significant variety of spec-driven development approaches.”
“You are just moving ambiguity and code review from one place to another without really gaining anything.”
“Helps me save tokens as well. Again, the discipline is the important bit”
“it is definitely less heavy than SpecKit.”
“I personally use Spec Kit for writing specifications for future AI coding”
“I use SpecKit to create a very detailed plan with a high amount of specificity”
“I am using https://github.com/github/spec-kit and am pretty content.”
“It has been great at keeping the code consistent across features.”
“I have production systems that I wrote using spec-kit, that have been running in production for months, and have been doing spectacularly.”
“I have been using spec-kit (which is basically this style of AI usage) for the last few months and it has been AMAZING in practice.”
“speckit which was ok but not great”
“Spec-kit and similar tools generate a plan and ask you to review it, which is OK.”
“I think any process like these + worktrees is the serious pro-tip/unlock.”
“This is one of the things that GitHub Spec Kit solves for me.”
“There are some good frameworks for this”
“spec-kit is clearly more matrue and wide in features and support”
“spec-kit produces a lot of markdown files and little source code”
“Things like speckit are working in the real world, at corporations.”
“every PR has hundreds, if not thousands, of lines of markdown comitted to the repo per ticket”
“Working on my first project with it… so far so good.”
“they can also largely be mitigated by using frameworks such as Openspec or Spec-Kit”
“it does make it do better, including writing its own checklists”
“Saves a ton of tokens and is reasonably quick”
“Sounds like the spec driven approach. You should take a look at this”
“Speckit is worth trying as it automates what is being described here”
“they are good reference points for starting out”
“spec-kit is very helpful for both green/brown field projects”
“Think the good parts of SpecKit + Beads + Obsidian + Backstage”
“tools like spec kit give reliably good results in brownfield codebases”
“Spec driven development tools like SpecKit, Kiro that promise English as being sufficient for LLM generated code”
“It's a project out of Microsoft/Github that encodes a rigorous spec-then-implement multi pass workflow.”
“It helps tremendously for facilitating a process around gathering requirements, doing research, planning, breaking into tasks, and finally implementing.”
“that looks very promising, I'm interested in trying it”
“I use speckit and have setup to wrap up tasks when at least 20% of context remaining”
“It is setting a baseline of how the LLM should engage with a project which is pretty critical to getting the highest quality output”
“I think spec-kit is an interesting idea but too heavy handed”
“I can give it two fairly simple prompts & get a reasonably complex result.”
“I think I just found this experience with SDD quite heavy-handed and the workflow unwieldy.”
“Version 1 generated by specify was already quite good and we iterated from there.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.