Fahsl describes how Kiro aims to make AI-assisted coding more predictable by turning a prompt into requirements, a design, and implementation tasks. Each phase is saved as a Markdown file, and tasks link back to the requirements.
Spec-Driven-Development With Kiro.dev
Speaker
Eric Fahsl, a product manager in Amazon’s Devices group focused on TV apps, presents Kiro.dev’s AI-assisted development workflow at the AI Meetup in Wrocław.
Fahsl demonstrates the approach with a React 19, Vite, and Three.js app that shows the International Space Station above Earth. Moving the experience to TV means accounting for slower devices, larger text, fewer on-screen items, remote-control navigation, and visible focus.
Fahsl uses Kiro’s Spec mode to plan D-pad camera controls and zoom for TV mode. Kiro creates user stories, describes components and TypeScript interfaces, then generates tasks that can be reviewed or started with their prior context.
The first zoom behavior feels awkward, so Fahsl updates the existing spec to use a zoom mode toggle. Kiro revises the requirements, design, and tasks; Fahsl also describes steering documents for project guidance and hooks that can run actions such as tests after code changes. He recommends using spec and vibe modes together, depending on the work.
Takeaways
- Use requirements, design, and linked tasks to give AI coding work a reviewable plan.
- When adapting an app for TV, account for device performance, remote navigation, focus, and screen layout.
- Treat specs as editable: update the plan when a prototype reveals a better interaction.
- Keep project guidance in steering documents so new AI work can reuse it.
- Use hooks to automate recurring actions such as running tests after changes.
Mentioned in this talk
Search inside this talk
What was claimed 8
- role atEric Fahsl is product manager in the Devices group, focusing on TV apps at Amazon
“I'm a product manager in Amazon's Devices group, focusing on TV apps.”
YouTube Unverified1 source· Talk
- previously atEric Fahsl previously at Amazonsolutions architect in the Alexa group
“I used to be a solutions architect in our Alexa group”
YouTube Unverified1 source· Talk
- feature
Kiro: based on VS Codebased on VS Code“It's based on VS Code”
YouTube Unverified1 source· Talk
- featureKiro: Supports hooks, steering documents, and MCP servers
“additional features like hooks, steering documents, and MCP server support”
YouTube Unverified1 source· Talk
- featureKiro: Includes Vibe and Spec modes
“it has both Vibe and Spec modes”
YouTube Unverified1 source· Talk
- launchedKiro: Public preview about a month and a half before the talk
“Kiro launched in public preview a month and a half ago”
YouTube Unverified1 source· Talk
- featureKiro: Spec mode breaks a prompt into requirements, design, and tasks
“turning a prompt into three distinct phases: requirements, design, and tasks”
YouTube Unverified1 source· Talk
- featureKiro: Hooks can run tests automatically after changes
“Anytime you make a change, it automatically runs the tests.”
YouTube Unverified1 source· Talk
