What problem does it solve? Starting new work without scoping leads to mis-sized specs, duplicated features, and silent drift between specs and code. This Skill analyzes a raw idea against existing specs, steering documents, and learnings to determine the right action path before any code or spec is written. ## Core Features & Use Cases - Action Path Routing: Classifies each request into update-existing-spec, no-spec-needed, new single spec, multi-spec decomposition, or mixed decomposition based on project state. - Architect Critique Dialogue: Pressure-tests problem framing, scope boundaries, and blast radius through one-question-per-turn dialogue grounded in the actual codebase. - Durable Briefs and Roadmaps: Writes brief.md files for new specs and roadmap.md for multi-spec decompositions so discovery analysis survives session boundaries. - Use Case: You type an idea like "add user notifications". The Skill scans existing specs, asks targeted scoping questions, proposes approaches with trade-offs, writes a brief, and recommends whether to run spec-quick or spec-init next. ## Quick Start Ask the assistant to run kiro-discovery with a description of your idea, such as "add dark mode toggle to settings page", and answer the scoping questions it asks.
