Skip to content

Pick your style: Denkbaar

Book a conversation

Articles

History

Kiro starts with agreements about the software

·

Amazon introduced Kiro as a coding environment where specifications guide agents.

Two builders compare an agreement on paper with a form.
First record what the software should do. Illustration: Denkbaar.

On 14 July 2025, Amazon introduced Kiro as an early version of a coding environment with agents. Its focus was specification-driven work: first describing what the software must do. Kiro presented features including specs and hooks for this purpose. The introduction focused on moving from an initial working idea to software that can be developed further and maintained. Source. A folder with a flowchart lies beside a laptop.

The difference was the attention given to the brief. A visible result does not answer every question about behaviour and design. Kiro’s introduction made recording those choices a central part of the tool, rather than only a conversation beside the code. An empty input field sits beside a recorded agreement.

For a small or medium-sized business, this is a useful approach to explore, even without choosing a particular editor. Take a simple process, such as a request with a required field. Write down what happens when that field is empty. Ask the builder to demonstrate that behaviour first. Keep the agreement with the change so a colleague can later understand why it exists. Judge the approach by clear choices and working checks.

Sources

  1. AWS Kiro preview (spec-driven IDE)

Topics: devtoolhistory