KUkurtis_reed·Aug 21, 2026
How is it different from https://github.com/github/spec-kit?
In Show HN: Huzzah – a novel approach to coding with AIgithub
spec-kit
Python2025–2026
github / spec-kit
spec-kit
💫 Toolkit to help you get started with SDD or any other process!
41Distinct people
44Mentions
1Explicit recommenders
149.6KGitHub stars
What to know before exploring
What it is
💫 Toolkit to help you get started with SDD or any other process!
GitHub
Where it is used
What people are saying
Yeah, the online Gemini app is not good for long lived conversations that build up a body of decisions. The context window gets too large and things drop. What I’ve learned is…
mattarm used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- gsd-build/get-shit-done · linked in 2 of the same discussions
- obra/superpowers · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month44 dated mentions
Observed mentions: 2025-09-04 09:06:23 UTC to 2026-08-21 00:01:40 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Sep 2025 | 2025-09-01 00:00:00 UTC | 2025-10-01 00:00:00 UTC | 16 | 15 | 1 |
| Oct 2025 | 2025-10-01 00:00:00 UTC | 2025-11-01 00:00:00 UTC | 6 | 1 | 5 |
| Nov 2025 | 2025-11-01 00:00:00 UTC | 2025-12-01 00:00:00 UTC | 5 | 1 | 4 |
| Dec 2025 | 2025-12-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
| Jan 2026 | 2026-01-01 00:00:00 UTC | 2026-02-01 00:00:00 UTC | 1 | 0 | 1 |
| Feb 2026 | 2026-02-01 00:00:00 UTC | 2026-03-01 00:00:00 UTC | 2 | 0 | 2 |
| Mar 2026 | 2026-03-01 00:00:00 UTC | 2026-04-01 00:00:00 UTC | 4 | 0 | 4 |
| Apr 2026 | 2026-04-01 00:00:00 UTC | 2026-05-01 00:00:00 UTC | 1 | 0 | 1 |
| May 2026 | 2026-05-01 00:00:00 UTC | 2026-06-01 00:00:00 UTC | 4 | 1 | 3 |
| Jun 2026 | 2026-06-01 00:00:00 UTC | 2026-07-01 00:00:00 UTC | 1 | 0 | 1 |
| Jul 2026 | 2026-07-01 00:00:00 UTC | 2026-08-01 00:00:00 UTC | 2 | 0 | 2 |
| Aug 2026 | 2026-08-01 00:00:00 UTC | 2026-09-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
44 sourcesInteresting. Still wondering how this is different from a structured app building with let us say https://github.com/github/spec-kit, or using some skills from https://github.com/obra/superpowers. Will try it out.
In Show HN: A primer for non-coders to design software via structured AI dialogueLocation: India (UTC+5:30 / IST)
Remote: Yes (primary preference)
Willing to relocate: Yes, for the right role
Technologies: Java, Spring Boot, Python, REST APIs, PostgreSQL, SQL, Docker, Git. Strong DSA (LeetCode Knight — top 1.7%, 1,157 solved, 226 Hard) and comfortable building from scratch — designed & implemented DhrLang, a small programming language (lexer/parser/interpreter).
Résumé/CV: https://dhruvrastogi.me
Email: dhruvrastogi2004@gmail.com
Backend engineer, ~1 YoE (Associate SWE at MAQ Software). Recently shipped an open-source extension to GitHub's Spec Kit (118k stars) adding EARS requirements support — PR: https://github.com/github/spec-kit/pull/3324
I like backend / platform / developer-tooling work: APIs, data models, and owning services end to end. Looking for a remote backend or full-stack role.
In Ask HN: Who wants to be hired? (July 2026)virgin project:
1/ spec driven dev (https://github.com/github/spec-kit)
2/ then degrade to multiple sessions (no worktrees) debugging various problems until its done
On UI Design (MacOS, Web):
1/ AI does a first pass. Try to give it style guidance on my own (colors, style, etc).
2/ Prompt ChatGPT.com with screenshots and ask for recommendations on how to make it better.
3/ Codex the changes (with minor edits)
4/ loop 2-3, ask Gemini for feedback too
In Ask HN: What is your (AI) dev tech stack / workflow?I am using https://github.com/github/spec-kit and am pretty content. I also tell it in the constitution.md to generate the .fsi files first, then write tests for it before implementation. That might very well be useless superstition since it is soo easy to fool yourself.
In Haskell Foundation 2026 UpdateWhat has really made AI coding be able to continue to work as the project got bigger was using speckit. It has been great at keeping the code consistent across features.
https://github.com/github/spec-kit
In I'm going back to writing code by handWhat makes this better/different than spec-kit? It seems to have a very similar philosophy. I wonder if they could work together? Or would they just be duplicative?
https://github.com/github/spec-kit
In Agent Skillsin addition to Compound Engineering, people in the comments in that thread also suggested the following planning tools to use with git worktrees:
- https://github.com/gsd-build/get-shit-done
- https://github.com/obra/superpowers
- https://github.com/github/spec-kit
I personally haven't used them, but I think any process like these + worktrees is the serious pro-tip/unlock.
In Senior engineer best practice for scaling yourself with Claude CodeHow does your framework compare to spec-driven development e.g. https://github.com/github/spec-kit? In my experience, spec-kit produces a lot of markdown files and little source code.
In Show HN: AI SDLC Scaffold, repo template for AI-assisted software developmentIt’s the style spec-kit uses: https://github.com/github/spec-kit
Working on my first project with it… so far so good.
In 1M context is now generally available for Opus 4.6 and Sonnet 4.6Lately, everyone has been sharing SKILL.md and AGENT.md files.
I think the more important layer is actually SPEC and MEMORY.
That is the idea behind this repo:
Ultimate Project combines two separate disciplines:
Beastmode -> the software engineering discipline
spec-kit -> the structure and organization of specs
Beastmode gives the engineering workflow.
spec-kit gives the project a clear spec foundation.
Putting them together creates a development loop where the system starts from specs, keeps context in memory, and follows a more structured implementation lifecycle.
Combination Repo: https://github.com/senolcolak/ultimate-project
beastmode: https://github.com/BugRoger/beastmode
spec-kit: https://github.com/github/spec-kit
For small project, a simple history file ./store-my-history in a dir works. For bigger projects, I think structured sp
Read the rest
ecs + engineering memory matter much more than prompt files alone.
I’d be curious how others here are handling spec organization, memory, and iteration flow in agent-driven development.
Sounds like the spec driven approach. You should take a look at this https://github.com/github/spec-kit
In If AI writes code, should the session be part of the commit?Nice.
It can work with something like https://github.com/github/spec-kit ?
In Verified Spec-Driven Development (VSDD)Great idea, and some of the tools are already somewhat covering it, e.g. GSD or spec-kit.
https://github.com/gsd-build/get-shit-done
https://github.com/github/spec-kit
In Stop prompting. Let the AI interview you to build specsShowing the 15 most recent of 44 sources. Enable JavaScript to search and browse every indexed mention.