| Crates.io | kiro-radar |
| lib.rs | kiro-radar |
| version | 0.1.0 |
| created_at | 2025-11-24 10:06:39.101342+00 |
| updated_at | 2025-11-24 10:06:39.101342+00 |
| description | A TUI dashboard for tracking Spec-Driven Development progress in AWS Kiro IDE. |
| homepage | https://github.com/mzkmnk/kiro-radar |
| repository | https://github.com/mzkmnk/kiro-radar |
| max_upload_size | |
| id | 1947599 |
| size | 111,685 |
A TUI (Terminal User Interface) dashboard for tracking Spec-Driven Development progress in AWS Kiro IDE.
kiro-radar is a tool that visualizes the Spec-based development process, allowing you to monitor the progress of requirements definition, design, and implementation tasks in real-time from your terminal.
It automatically detects Spec sets under the .kiro/specs directory and tracks task progress in Markdown checklist format.

.kiro/specs directorycargo install kiro-radar
# Clone the repository
git clone https://github.com/mzkmnk/kiro-radar.git
cd kiro-radar
# Build and install
cargo install --path .
# Run in development mode
cargo run
| Key | Action |
|---|---|
j / ↓ |
Move to next item |
k / ↑ |
Move to previous item |
q / Esc / Ctrl+C |
Exit application |
kiro-radar expects the following directory structure:
.kiro/
└── specs/
└── {spec-name}/
├── requirements.md # Requirements definition
├── design.md # Design document
└── tasks.md # Implementation tasks
tasks.md should be written in Markdown checklist format:
# Implementation Plan
- [ ] 1. Task 1
- [x] 2. Task 2 (completed)
- [ ] 3. Task 3
kiro-radar adopts an event-driven architecture and consists of the following modules:
For details, see .kiro/steering/structure.md.
# Run all tests
cargo test
# Display test output
cargo test -- --nocapture
# Apply formatting
cargo fmt
# Check formatting
cargo fmt -- --check
# Run Clippy
cargo clippy
# Stricter linting
cargo clippy -- -D warnings
Copyright (c) mzkmnk mzk.mnk.dev@gmail.com
This project is licensed under the MIT license (LICENSE)