AI coding without luck: the complete guide to replicating Kiro's Spec workflow
· 7 min read
After more than a year of AI-assisted coding, my biggest lesson is this: vibe coding feels great in the moment, but it falls apart the moment a project gets complex. A one-line requirement, AI starts coding on its own assumptions, and what comes out is always a bit off. You ask it to fix something, it fixes that and breaks something else. A few rounds of this and your codebase has tripled in size while the number of working features barely grew.
Eventually I figured it out: the problem isn't that AI writes bad code. It's that I don't say clearly what I want.
Kiro's Spec workflow is built to solve exactly that. Let's walk through it from scratch.