Working Wombat 🦫
@workingwombat.rocks
🛠️ Indie dev building with structure, not chaos.
⚡ Beyond vibe coding.
🚀 quietship | social media for devs who hate marketing
🗺️ spotwise | tour app for Sylt island
🧠 thinkmob | AI that challenges your thinking
⚡ Beyond vibe coding.
🚀 quietship | social media for devs who hate marketing
🗺️ spotwise | tour app for Sylt island
🧠 thinkmob | AI that challenges your thinking
I use BMAD for my spec-driven workflow.
It's a framework for structured AI-assisted development:
→ Product briefs before PRDs
→ Architecture before code
→ Epics & stories before implementation
The pattern: think first, then let AI execute.
Been using it for months. Fewer rewrites. More quality 🔥
It's a framework for structured AI-assisted development:
→ Product briefs before PRDs
→ Architecture before code
→ Epics & stories before implementation
The pattern: think first, then let AI execute.
Been using it for months. Fewer rewrites. More quality 🔥
February 8, 2026 at 8:26 AM
I use BMAD for my spec-driven workflow.
It's a framework for structured AI-assisted development:
→ Product briefs before PRDs
→ Architecture before code
→ Epics & stories before implementation
The pattern: think first, then let AI execute.
Been using it for months. Fewer rewrites. More quality 🔥
It's a framework for structured AI-assisted development:
→ Product briefs before PRDs
→ Architecture before code
→ Epics & stories before implementation
The pattern: think first, then let AI execute.
Been using it for months. Fewer rewrites. More quality 🔥
OpenSpec is the open-source SDD framework gaining momentum.
20k+ stars. Works with 20+ AI tools including Claude Code, Cursor, Copilot, and Windsurf.
The pitch: "Agree before you build."
Each feature gets its own folder. Human and AI align before code gets written.
🔗 openspec.dev
20k+ stars. Works with 20+ AI tools including Claude Code, Cursor, Copilot, and Windsurf.
The pitch: "Agree before you build."
Each feature gets its own folder. Human and AI align before code gets written.
🔗 openspec.dev
OpenSpec — A lightweight spec‑driven framework
OpenSpec is a lightweight, spec‑driven framework for coding agents and CLIs — universal, open source, and no API keys or MCP required.
openspec.dev
February 7, 2026 at 8:36 AM
OpenSpec is the open-source SDD framework gaining momentum.
20k+ stars. Works with 20+ AI tools including Claude Code, Cursor, Copilot, and Windsurf.
The pitch: "Agree before you build."
Each feature gets its own folder. Human and AI align before code gets written.
🔗 openspec.dev
20k+ stars. Works with 20+ AI tools including Claude Code, Cursor, Copilot, and Windsurf.
The pitch: "Agree before you build."
Each feature gets its own folder. Human and AI align before code gets written.
🔗 openspec.dev
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
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
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.com
January 31, 2026 at 8:36 AM
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
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.
The flow:
Requirements → Design → Tasks → Code
Not just "generate code from chat." Actual structure.
Interesting to see AWS betting on this approach.
January 30, 2026 at 8:12 PM
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.
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 🔥
→ Kiro (AWS's new IDE)
→ GitHub Spec-Kit
→ OpenSpec
Plus BMAD-Method 🔥
January 28, 2026 at 8:36 AM
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 🔥
→ 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
📝 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
January 26, 2026 at 5:11 PM
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
📝 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. 🛠️
→ 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. 🛠️
January 25, 2026 at 8:26 AM
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. 🛠️
→ 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.
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.
January 24, 2026 at 8:36 AM
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.
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.
👋
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.
👋
January 19, 2026 at 5:11 PM
🚀 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.
👋
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.
👋