Working Wombat 🦫

GitHub - github/spec-kit: 💫 Toolkit to help you get started with Spec-Driven Development 💫 Toolkit to help you get started with Spec-Driven Development - github/spec-kit

GitHub's Spec-Kit has 64k+ stars.

It's a toolkit for spec-driven development:
→ CLI for bootstrapping specs
→ Templates for requirements
→ Works with Copilot and other AI tools

Specs live in your repo. Context doesn't disappear when chat resets.

github.com/github/spec-kit

AWS released Kiro — a spec-driven AI IDE.

The flow:
Requirements → Design → Tasks → Code

Not just "generate code from chat." Actual structure.

Interesting to see AWS betting on this approach.

In the upcoming posts I'll dig into spec-driven development (SDD) and tools I've been exploring:

→ Kiro (AWS's new IDE)
→ GitHub Spec-Kit
→ OpenSpec

Plus BMAD-Method 🔥

Ever heard of Spec-Driven Development (SDD)?

📝 The idea: write specs before code. Let AI implement from clear requirements.

Why it matters:
→ Less "vibe coding"
→ Reproducible results
→ AI understands what you actually want

Exploring:
→ Dev tools for indie makers
→ Better workflows for AI-assisted development

Building:
→ A tour app for a German island (Flutter) + CMS (Next.js 16) — entirely with AI using spec-driven approach

More soon. 🛠️

Why "beyond vibe coding"?

Vibe coding = code and pray. It works for quick prototypes, but I kept hitting walls on real projects.

Now I let write specs first, then let AI implement. Structure beats vibe at scale.

🚀 New here...

Indie dev who likes structure more than chaos.
Building apps, sharing the journey.

Beyond vibe coding — let's see where this goes.
Progress, learnings, and occasional hot takes.

👋