Amazon launched Kiro in 2025 with a waiting list and a clear thesis: the problem with AI coding tools is not that they write bad code, it is that they write code with no connection to your requirements. Kiro's answer is spec-driven development — you write a spec, the tooling generates from it, and the spec stays authoritative.
Kiro is a good idea. But it is also a proprietary IDE you have to install, sign in to, and trust with your codebase.
I built the same concept as a set of open-source CLI tools: one per ecosystem, published to the registry your team already uses. No IDE. No account. No network calls. A text file goes in, a working application comes out.
Here is what I built, how it works, and why the architecture matters more than the code.
Try it right now — pick your stack
