Generating Specs

Once you’ve submitted your prompt in Spec mode, Kiro begins generating structured specification documents.

1. Kiro starts generating specs

   After submitting the prompt, Kiro begins creating specs — structured artifacts that formalise the development process for your application.

   

2. Review the requirements document

   Specs are structured into three parts:

   • Requirements — User stories and acceptance criteria in structured EARS notation
   • Design — Technical architecture, sequence diagrams, and implementation considerations
   • Task List — A detailed implementation plan with discrete, trackable tasks

   

   Kiro generates the requirements document first. Review it and modify as needed — you have full control over what’s included.

   What is EARS notation?

   EARS (Easy Approach to Requirements Syntax) is a structured format for writing unambiguous requirements:

   • Ubiquitous: “The [system] shall [action]” — Always-on behaviour
   • Event-driven: “When [event], the [system] shall [action]” — Triggered behaviour
   • State-driven: “While [state], the [system] shall [action]” — Conditional behaviour
   • Optional: “Where [feature], the [system] shall [action]” — Feature-dependent behaviour
   • Unwanted: “If [condition], then the [system] shall [action]” — Exception handling

   This notation helps Kiro generate precise, testable requirements that capture edge cases automatically.

3. Move to the design phase

   Once you’re satisfied with the requirements, click the button to proceed to the design phase. Kiro always follows the order: Requirements → Design → Task List.

   

   Kiro works on acceptance criteria and generates the design document based on your approved requirements.

Note

Kiro always generates specs in order: Requirements first, then Design, and finally the Task List. You can review and modify each document before proceeding to the next step.