It's 2026. Where's your Spec Kit? 🧰 Instead of coding first and writing docs later, spec-driven development flips the script. Start with a spec, a clear contract for how your code should behave. This makes it easier for your AI agents to generate, test, and validate high-quality code. 🤖 Get started with this new open source toolkit. ⬇️ github.blog/ai-and-ml/gene…

@github spec kit is just the README we were too lazy to write in 2024

this actually makes sense with AI tools i've noticed claude code and cursor work way better when you give them clear specs upfront. they can reason about the whole system instead of just generating isolated functions. it's less about formal documentation and more about being clear on what you're building before you build it

@github That's great

@github Totally agree! Spec-driven dev helps avoid so many headaches down the road. 👏

@github to start with a thing called 'specification'? whats that?? sounds like the 80s, the days of the waterfalls.. a gen-z programmer doesn't need a 'specification' - he's agile, he deploys 3*times a day

@github Spec Kit was excellent inspiration for what’s possible if you customize your workflow. I’m running a customized version that’s tapped into DAP iQ’s domain context.

@github I found this overwhelming so I built my own simpler version… npmjs.com/package/cycles…

@github Well, it’s great and missing an important like my issue here github.com/github/spec-ki…

@github I don’t see many people using sdd but worth trying. Maybe would be better to write prd or specs first

@github I see you github. Start with a foundation for me on signing up

@github Spec-driven development in 2026? We've been saying "docs first" for decades, yet here we are still shipping hotfixes for features that were never scoped. Tools don't fix broken workflows, they just automate the chaos. 📉 @github

@github hey github whats this guy called