What problem does it solve? When starting new work in a spec-driven project, it is unclear whether a request needs a new spec, an update to an existing spec, a multi-spec decomposition, or no spec at all. This Skill removes that ambiguity by scanning project state and guiding a structured discovery dialogue before any spec work begins. ## Core Features & Use Cases - Action Path Routing: Scans .kiro/specs and .kiro/steering metadata to classify requests into five paths: existing spec update, no spec needed, new single spec, multi-spec decomposition, or mixed decomposition. - Structured Discovery Dialogue: Asks sequential clarifying questions about users, outcomes, boundaries, and constraints, then proposes 2-3 approaches with trade-offs and a viability check. - Persistent Artifacts: Writes brief.md files for new specs and roadmap.md for decomposed projects to disk so discovery results survive session boundaries. - Use Case: A user asks to add real-time collaboration to an existing app. The Skill detects overlapping specs, decomposes the work into three ordered specs, writes a roadmap and briefs, then suggests running the batch spec command. ## Quick Start Ask the assistant to run discovery for your new feature idea so it can determine the right spec path and produce an actionable brief.
