DOP 345: From Chat Prompt to Working Software with Kiro

: Vibe coding works fine until your project gets complicated. That's the gap Amit Patel and his team at AWS built Kiro to fill. The tool launched with about six people in mid-2024, hit GA around October 2025, and the team still fits in a single room -- maybe a seven-pizza team by Darin's math. The core idea is spec-driven development, but not the kind where business analysts disappear for five years and come back with a document nobody needs anymore. Amit's version: you tell the agent what you want in a chat prompt, it writes the spec for you, and you iterate on it. Twenty minutes of back and forth and you've got requirements, a design, and a task breakdown. Then the agent executes. Two to three days later, working software. Here's where it gets interesting. Amit frames the human role as bookends. At the front, you define intent -- what needs to exist and why. At the back, you verify that what got built actually matches. Everything in the middle? That's where the tooling lives. And that middle is getting wider every month as agents run longer, handle more turns, and start working in parallel. But the gap between 'I can build it' and 'I built it right' is real. Amit's S3 example nails it. Ask an LLM to build a file upload app and you'll get one that works. Encryption at rest, encryption in transit, KMS, bucket policies -- none of that shows up unless you know to ask for it. The LLM will generate all of it on request. It just won't volunteer it. That's the experience gap, and it's why junior developers still need to become senior developers the old-fashioned way. One story that landed: a product manager on Amit's team used Kiro to go from conversation to working prototype overnight. Not a wireframe. Not a doc. A demo the engineering team could put into production. The roles aren't disappearing -- they're getting more fluid. The value was never in the writing. It was always in knowing what needed to be built. Kiro is now widely adopted inside AWS, with both an IDE and a CLI. Where it's headed next: agents that run in the background, handle multiple tasks at once, and get verified with formal methods instead of just hoping the output is right. But Amit's honest about the limits -- steering file adherence is, in his words, an art in itself. Non-deterministic LLMs will ignore your rules sometimes. Just like humans. Amit's contact information: LinkedIn: YouTube channel: Review the podcast on Apple Podcasts: Slack: Connect with us at:

You can listen to DOP 345: From Chat Prompt to Working Software with Kiro online on Radio and Podcast. Open the player on this page to stream the available audio.

DOP 345: From Chat Prompt to Working Software with Kiro is an episode from DevOps Paradox by Darin Pope.

This episode is 38:56 long.

This episode was published on Apr 8, 2026.

Yes. Use the heart button on the episode page to add it to your favorite episodes list.

Yes. This page shows related episodes from DevOps Paradox when more episodes are available from the podcast feed.