What problem does it solve?
Kiro-discovery helps teams decide the correct next action for a proposed piece of work by quickly scanning repository metadata and steering artifacts to determine whether to update an existing spec, create a new spec, decompose into multiple specs, or proceed with direct implementation. It prevents wasted effort on unnecessary specification, keeps discovery conversations focused, and ensures the next step is actionable.
Core Features & Use Cases
- Lightweight scan: Collects only metadata (file existence and spec.json name/phase/approvals) and a top-level directory listing to classify the project's state without loading full file contents.
- Action path decisioning: Applies clear rules for Path A (existing spec), Path B (no spec), Path C (single new spec), Path D (multi-scope decomposition), and Path E (mixed decomposition) and prompts for confirmation when needed.
- Controlled deep-loading & delegation: For non-trivial cases, it reads steering docs and relevant specs and delegates heavy codebase exploration to subagents to keep main context under budget.
- Authoritative disk writes: For spec creation paths, it writes brief.md and roadmap.md files in the prescribed formats and verifies they exist so discovery results persist across sessions.
- Use cases: onboarding a new feature request, triaging cross-cutting change proposals, and converting stakeholder ideas into scoped briefs and roadmaps ready for implementation.
Quick Start
Use kiro-discovery to evaluate a new feature request and recommend whether to update an existing spec, create one, decompose into multiple specs, or implement directly.
