kiro-integration

# Kiro Integration

AWS Kiro specification patterns, file structure, and synchronization with canonical model.

## When to Use This Skill

**Keywords:** Kiro, AWS Kiro, requirements.md, design.md, tasks.md, steering files, Kiro IDE, Kiro agent, Kiro sync, spec generation, agentic development, Kiro hooks

**Use this skill when:**

- Working with AWS Kiro IDE or Kiro-compatible tools
- Syncing between Kiro format and canonical specifications
- Creating or updating Kiro specification files
- Configuring steering files for agent context
- Integrating Kiro with existing spec-driven workflows
- Converting between Kiro and other specification formats

## Kiro Overview

Kiro is an agentic IDE developed by AWS that uses specification-driven development. It generates three interconnected files:

```text
.kiro/
├── specs/
│   ├── requirements.md    # EARS-formatted requirements
│   ├── design.md          # Technical implementation design
│   └── tasks.md           # Executable task breakdown
└── steering/
    └── context.md         # Agent steering context
```

## Key Concepts

### Specification Files

| File | Purpose | Format |
| --- | --- | --- |
| `requirements.md` | Requirements using EARS patterns | EARS syntax in markdown |
| `design.md` | Technical design and architecture | Markdown with diagrams |
| `tasks.md` | Executable task checklist | Markdown checkboxes |

### EARS Integration

Kiro uses EARS (Easy Approach to Requirements Syntax) for requirements. All six patterns are supported:

- **Ubiquitous:** `The system SHALL...`
- **State-Driven:** `WHILE <condition>, the system SHALL...`
- **Event-Driven:** `WHEN <trigger>, the system SHALL...`
- **Unwanted:** `IF <condition>, THEN the system SHALL...`
- **Optional:** `WHERE <feature>, the system SHALL...`
- **Complex:** Combinations of the above

### Steering Files

Steering files provide context to the Kiro agent:

- Project-specific knowledge
- Codebase conventions
- Domain terminology
- Architectural constraints

##