# GitHub Spec Kit

39 Hacker News commenters recommended GitHub Spec Kit and 22 criticized it, November 2025 to November 2026. It was recommended in 10 of 13 months.

**Verdict:** 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.

## Why people recommend it

- Structured planning before implementation (3 comments): "It helps tremendously for facilitating a process around gathering requirements, doing research, planning, breaking into tasks, and finally implementing." ([source](https://news.ycombinator.com/item?id=46257559)) "It is setting a baseline of how the LLM should engage with a project which is pretty critical to getting the highest quality output" ([source](https://news.ycombinator.com/item?id=45941617)) "It's a project out of Microsoft/Github that encodes a rigorous spec-then-implement multi pass workflow." ([source](https://news.ycombinator.com/item?id=46542058))
- Works on brownfield codebases (2 comments): "tools like spec kit give reliably good results in brownfield codebases" ([source](https://news.ycombinator.com/item?id=46864964)) "spec-kit is very helpful for both green/brown field projects" ([source](https://news.ycombinator.com/item?id=46899664))
- Saves tokens and time (2 comments): "Helps me save tokens as well. Again, the discipline is the important bit" ([source](https://news.ycombinator.com/item?id=49735944)) "Saves a ton of tokens and is reasonably quick" ([source](https://news.ycombinator.com/item?id=47216938))
- Consistent output across features (2 comments): "I can give it two fairly simple prompts & get a reasonably complex result." ([source](https://news.ycombinator.com/item?id=45936347)) "It has been great at keeping the code consistent across features." ([source](https://news.ycombinator.com/item?id=48090951))

## What people warn about

- Heavy-handed and unwieldy workflow (2 comments): "I think spec-kit is an interesting idea but too heavy handed" ([source](https://news.ycombinator.com/item?id=45938232)) "I think I just found this experience with SDD quite heavy-handed and the workflow unwieldy." ([source](https://news.ycombinator.com/item?id=45935925))
- Lots of markdown, little code (2 comments): "every PR has hundreds, if not thousands, of lines of markdown comitted to the repo per ticket" ([source](https://news.ycombinator.com/item?id=47392053)) "spec-kit produces a lot of markdown files and little source code" ([source](https://news.ycombinator.com/item?id=47477819))
- Ambiguity moved rather than removed (2 comments): "Spec driven development tools like SpecKit, Kiro that promise English as being sufficient for LLM generated code" ([source](https://news.ycombinator.com/item?id=46745820)) "You are just moving ambiguity and code review from one place to another without really gaining anything." ([source](https://news.ycombinator.com/item?id=49736366))

## Alternatives hackers recommend

- [OpenSpec](https://hackerapproved.com/p/openspec.md): 49 recommend
- [Verified Spec-Driven Development (VSDD)](https://hackerapproved.com/p/verified-spec-driven-development.md): 5 recommend

## Cite as

Hacker Approved, "GitHub Spec Kit", https://hackerapproved.com/p/spec-kit/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).