deep-clarifylisted

# deep-clarify — Socratic Requirement Clarification A skill that clarifies vague or open-ended requests through conversation to produce **actionable spec documents**. An independent extension of the "direction confirmation" protocol from agent-composer Step 0-a. ## Triggers - `/deep-clarify` - "I don't know what to build", "How should I approach this?" - "Organize the requirements", "Write a spec document" - "What should I do with this?", "The direction is unclear" - When agent-composer detects pre-dispatch clarification is needed and delegates automatically ## Core Principles **Criteria for asking vs inferring**: - Things only the human can know (goal, priorities, constraints, completion criteria) → ask - Things AI can infer (implementation method, file location, technology choices) → infer and present as `(inferred: X)` - Questions: **maximum 3 rounds, maximum 2 questions per round** — do not overuse --- ## Step 1. Request Analysis Quickly identify the following from the user's request. ``` Clarity check: □ Final state (what will be different when done?) — ask if unclear □ Completion criteria (how will it be verified?) — ask if unclear □ Constraints (what must not be done, what must not be touched) — ask if unclear □ Priority (fast vs thorough, now vs later) — ask if unclear ``` **Direct entry conditions** (skip to Step 3 without questions): - Request is specific and completion criteria are clear → draft spec document and confirm - Clarity at the level of "add Y f