clarifying-requirementslisted

# Clarifying Requirements This skill teaches you to analyze user prompts for gaps, ambiguities, and unstated assumptions—then ask the questions the user failed to ask BEFORE beginning work. ## Core Principle **Don't just answer what was asked—anticipate what SHOULD have been asked.** Users often don't know what they don't know. Your job is to surface: - Gaps in their thinking - Unstated assumptions that could derail implementation - Questions that would improve outcomes if asked upfront - Scope ambiguities that lead to rework ## When to Apply This Skill Activate proactive clarification when the user's request: | Signal | Example | Why It Matters | | -------------------------- | ----------------------------------------- | --------------------------------------------- | | Vague action verbs | "add", "improve", "fix" without specifics | Undefined scope leads to wrong implementation | | Missing constraints | "make it faster" without metrics | No way to know when you're done | | Complexity underestimation | "just", "simple", "quick", "easy" | Often hides edge cases | | Multiple features bundled | "add X and Y and also Z" | Scope creep, unclear priority | | Goal without criteria | "users should be able to..." | No acceptance criteria | | Assumed con