The outcome

Learn the interaction loop using a small task with a clear outcome.

Kiro is a agentic integrated development environment from AWS. Turning feature ideas into requirements, design, tasks, and implementation while preserving repository guidance and explicit review of agent changes. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Install Kiro, sign in with the approved identity, and open a clean branch containing no exposed credentials.

  2. 02

    Create a spec for one feature and review its requirements, design, and implementation tasks before coding.

  3. 03

    Use supervised mode with a narrow trusted-command list while Kiro implements one task at a time.

  4. 04

    Review and accept each diff, run trusted tests, and use checkpoints before any merge or deployment.

Working standard

What good use looks like.

  • State the outcome before the background.
  • Provide the real source material.
  • Review the result before expanding the task.

Supervised and Autopilot modes have similar underlying file and command access; supervised mode adds a review-and-revert workflow rather than a stronger sandbox. Use repository-scoped authentication, temporary AWS credentials, carefully bounded trusted-command prefixes, protected paths, reviewed extensions and MCP servers, human-approved specs, checkpoints, and independent tests. Never use a universal command trust pattern on untrusted content.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.