SDD Catalog
Execution Workflow AWS Proprietary

AWS Kiro Spec-Driven Development

Kiro is an agentic IDE whose spec workflow turns a prompt into a three-file spec — requirements (EARS notation), design, and tasks — then implements task by task. Modeled from published documentation and the IDE (no public source repository), so the on-disk detail is lower-confidence than repo-modeled tools.

Modeled from published documentation (no inspectable source repository); on-disk detail is lower-confidence than repo-modeled tools.

Documentation Homepage

Detection

A project uses Kiro when any of these exist:

  • .kiro/specs/
  • .kiro/steering/
  • .kiro/specs/*/requirements.md

Status Model

Method: task-checkboxes

Percent complete = checked over total tasks in tasks.md. Phase is inferable from which of requirements.md / design.md / tasks.md exist for a feature.

Lifecycle

  1. 1
    Steering

    Optional standing guidance the agent applies across specs.

  2. 2
    Requirements

    Capture requirements in EARS notation from a feature prompt.

  3. 3
    Design

    Produce the technical design from the approved requirements.

  4. 4
    Tasks

    Break the design into discrete implementation tasks.

  5. 5
    Implement

    Execute tasks one at a time, updating task status.

On-Disk Artifacts

.kiro/steering/ constitution Steering documents — standing project conventions and guidance.
.kiro/specs/<feature>/requirements.md requirement Feature requirements in EARS notation (user stories + acceptance criteria). Maps to PRD.
.kiro/specs/<feature>/design.md design Technical design — architecture, components, data models, sequencing. Maps to TRD.
.kiro/specs/<feature>/tasks.md tasks Discrete, checkboxed implementation tasks linked to requirements. Maps to PLAN.
./ output Source code implemented task by task from tasks.md.