Spec-Driven Development

Each preset ships a library of worked example specs as .kiro/specs/example-<feature>/ — each with a .config.kiro marker so it shows up in Kiro's Specs panel.

These are fully-written requirements.md / design.md / tasks.md trios demonstrating:

• EARS acceptance criteria
• Out of Scope boundaries
• Files & Interfaces sections
• Mermaid diagrams
• Task-to-requirement traceability
• An end-to-end verification and documentation task

The full list per preset is in the preset reference, generated from the presets themselves.

Steering

A spec-driven-development.md steering file teaches the EARS patterns and the requirements → design → tasks approval gates.

Scaffolding your own

kiro-kit spec new my-feature            # from the installed template
kiro-kit spec new my-feature --from backend