Synchronizes canonical specs with AWS Kiro format (.kiro/requirements.md, design.md, tasks.md). Supports import, export, bidirectional sync with conflict detection and dry-run.
npx claudepluginhub melodic-software/claude-code-plugins --plugin spec-driven-developmentThis skill is limited to using the following tools:
Synchronize specifications with AWS Kiro IDE format.
Manages AWS Kiro spec files including requirements.md (EARS), design.md, tasks.md, and steering context.md for IDE sync and AI agent workflows.
Guides feature development from idea to implementation: creates EARS requirements, design documents, and task lists in .kiro/specs/.
Transforms ideas into structured specifications (requirements, design, tasks) before implementation. Use when building features, fixing bugs, refactoring, or designing systems.
Share bugs, ideas, or general feedback.
Synchronize specifications with AWS Kiro IDE format.
AWS Kiro uses a specific file structure:
.kiro/
├── steering/
│ ├── requirements.md # Project-wide requirements
│ ├── design.md # Overall design
│ └── tasks.md # Current tasks
├── specs/
│ └── {feature-name}/
│ ├── requirements.md
│ ├── design.md
│ └── tasks.md
└── kiro.json # Configuration
| Direction | Description |
|---|---|
import | Kiro → Canonical (read from Kiro) |
export | Canonical → Kiro (write to Kiro) |
bidirectional | Two-way sync with conflict detection |
Detect Structure
Execute Sync
spec-converter kiro agentHandle Conflicts
Apply Changes
Report
$1 - Specification file or .kiro/ directory--direction - Sync direction: import, export, bidirectional (default)--force - Overwrite without conflict check--dry-run - Show what would change without writing# Export canonical to Kiro
/spec-driven-development:kiro-sync .specs/auth/spec.md --direction export
# Import from Kiro
/spec-driven-development:kiro-sync .kiro/specs/auth/ --direction import
# Bidirectional sync
/spec-driven-development:kiro-sync .specs/auth/spec.md
# Dry run to see changes
/spec-driven-development:kiro-sync .specs/auth/spec.md --dry-run
| Canonical | Kiro |
|---|---|
| Problem Statement | Context |
| Scope | Context/Scope |
| FR-X | REQ-X |
| NFR-X | REQ-NX |
| AC-X.Y | AC-X.Y |
| Canonical | Kiro |
|---|---|
| Design Overview | Overview |
| Components | Components |
| Data Model | Data Model |
| API Design | API Design |
| Canonical | Kiro |
|---|---|
| Task List | Task List |
| TASK-X | TASK-X |
| Dependencies | Dependency graph |
Kiro uses EARS syntax natively, so requirements pass through unchanged:
Canonical:
## FR-1: User Login
WHEN the user submits valid credentials,
the system SHALL authenticate the user.
Kiro (requirements.md):
### REQ-1: User Login
WHEN the user submits valid credentials,
the system SHALL authenticate the user.
Only the ID prefix changes (FR-X → REQ-X).
# Kiro Sync Report
**Direction:** Bidirectional
**Timestamp:** 2024-01-15T10:30:00Z
## Summary
| Type | Added | Updated | Unchanged | Conflicts |
| --- | --- | --- | --- | --- |
| Requirements | 1 | 2 | 5 | 0 |
| Design | 0 | 1 | 0 | 0 |
| Tasks | 3 | 0 | 2 | 0 |
## Changes
### Added
- REQ-8 (new requirement in canonical)
### Updated
- REQ-2: Updated acceptance criteria
- REQ-5: Clarified EARS statement
## Generated Files
- .kiro/specs/auth/requirements.md (updated)
- .kiro/specs/auth/design.md (updated)
- .kiro/specs/auth/tasks.md (created)
/spec-driven-development:convert - General format conversion/spec-driven-development:speckit-run - Full Spec Kit workflow/spec-driven-development:specify - Generate specification