Clarify

Resolve ambiguity before action. This skill turns vague, incomplete, or contradictory implementation requests into precise, actionable scope through structured clarification or documented assumptions.

Invocation posture: hybrid. Prefer explicit invocation. Automatic activation should stay limited to high-confidence implementation ambiguity, not general idea exploration.

When To Activate

• The user explicitly asks to clarify requirements, disambiguate a request, or spec a change before implementation
• An implementation request contains direct contradictions or mutually exclusive constraints
• Acceptance criteria or scope boundaries are missing in a way that would materially change what gets built
• The user asks you to proceed with assumptions and those assumptions need to be made explicit
• Multiple plausible implementations exist and choosing among them would change files, APIs, or user-visible behavior

When Not To Use

• Open-ended option exploration, strategy work, or direction-finding; use brainstorming
• Requests that mainly ask "what should we do?" rather than "what exactly should we build?"
• Specific actionable tasks with clear files, error messages, or expected outcomes