←back to thread

Kiro: A new agentic IDE

(kiro.dev)
1013 points QuinnyPig | 1 comments | 14 Jul 25 14:24 UTC | HN request time: 0.206s | source
Show context
manbash ◴[15 Jul 25 00:05 UTC] No.44566625[source]▶
> 2. Technical design based on requirements > Kiro then generates a design document by analyzing your codebase and approved spec requirements. It creates data flow diagrams, TypeScript interfaces, database schemas, and API endpoints—like the Review interfaces for our review system. This eliminates the lengthy back-and-forth on requirements clarity that typically slows development.

This is nice for documentation but really having a design document after-the-fact doesn't really help much. Designing is a decision-making process before the code is written.

replies(4): >>44566645 #>>44566655 #>>44566676 #>>44567106 #
1. danbeaulieu ◴[15 Jul 25 01:44 UTC] No.44567106[source]▶
Kiro takes the requirements and the existing code to create a spec.

Otherwise the spec may cover requirements that are already met in the existing code and needs to understand integration points it needs to include in the spec.

Having used Kiro myself I think it does what you expect.