clarifying-requirementslisted

# Clarifying Requirements 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. Surface gaps in their thinking, unstated assumptions that could derail implementation, and scope ambiguities that lead to rework. The one test that matters: "Can I implement this without making assumptions?" If not, ask about the assumptions you'd have to make. ## When to Apply Activate proactive clarification when the request shows: | 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 add a button", "simple form", "quick" | Often hides error/loading/permission states | | Multiple features bundled | "add X and Y and also Z" | Scope creep, unclear priority | | Goal without criteria | "users should be able to..."