What problem does it solve? Passing vague feature ideas directly into Kiro's spec-driven development workflow locks ambiguity into requirements, design, and tasks. This Skill clarifies domain terminology, design decisions, and spec boundaries before anything reaches kiro-discovery or kiro-spec-init. ## Core Features & Use Cases - Pre-spec clarification: Runs grill-with-docs questioning to pin down the problem, current state, desired outcome, and scope boundaries before spec creation. - Context persistence: Records confirmed domain terms in CONTEXT.md and irreversible or trade-off decisions as ADRs under docs/adr/. - Structured Kiro handoff: Produces a standardized handoff document (Problem, Current State, Scope, Boundaries, Domain Context Updates, Kiro Route) instead of forwarding raw user requests. - Use Case: A user says "I want to add a notification feature." The Skill grills the request, updates CONTEXT.md with new terms, drafts an ADR for the delivery-channel decision, then routes a clean handoff to kiro-spec-init. ## Quick Start Ask the assistant to grill this feature idea and prepare it for a Kiro spec before creating any requirements.