What problem does it solve? Vague one-line requests and ambiguous requirement drafts lead to misaligned implementations and wasted development effort. This Skill turns fuzzy asks into a written, verifiable requirement confirmation sheet before any planning or coding begins. ## Core Features & Use Cases - Layered Questioning: Asks at most 3 prioritized questions per round across semantic, value, constraint, and risk layers, each with a proposed default answer the user can simply confirm or correct. - Requirement Confirmation Sheet: Produces a written document covering goal, scope, non-goals, acceptance criteria, key assumptions, and open items (split into blocking vs. defaultable), written into docs/current-plan.md. - Workflow Handoff: After confirmation, hands off to a plan-designer step for implementation planning, keeping requirement clarification strictly separate from coding. - Use Case: A user says "help me build a replay feature" without specifics. The Skill restates its understanding, asks targeted questions about what "replay" means and how success is measured, then outputs an acceptance-ready requirement sheet. ## Quick Start Tell the assistant: "I want to add a damage leaderboard feature but I'm not sure about the details—grill me on the requirements first."