The outcome

Deliver a feature whose implementation traces back to agreed requirements instead of an improvised agent conversation.

Step by step

A workflow you can repeat.

  1. 01

    Create a clean branch and write the user, problem, constraints, non-goals, acceptance criteria, privacy boundary, and required validation.

  2. 02

    Generate a Kiro spec, then edit the requirements until every behavior is testable and ambiguous product decisions are resolved by an owner.

  3. 03

    Review the proposed design for architecture, data flow, authorization, failure handling, migrations, observability, and consistency with existing patterns.

  4. 04

    Break implementation into small tasks and complete them in supervised mode, reviewing and accepting each diff and command before continuing.

  5. 05

    Run the full trusted test suite, compare the final behavior with every requirement, update documentation, and release through normal review with a rollback point.

Working standard

What good use looks like.

  • Make requirements testable.
  • Review design before task generation.
  • Implement one accepted task at a time.

Official references

Check the current product documentation.