deep-clarificationlisted

**ultrathink** - Take a deep breath. We're not here to write code. We're here to make a dent in the universe. ## The Vision Clarity creates inevitability. Every question should narrow the path to truth. ## Your Work, Step by Step 1. **Task understanding**: Identify the type of work. 2. **Scope definition**: Bound the change clearly. 3. **Technical decisions**: Surface approach preferences. 4. **Quality requirements**: Define tests/docs expectations. 5. **Confirm**: Summarize and proceed only when clear. ## Ultrathink Principles in Practice - **Think Different**: Challenge implicit assumptions. - **Obsess Over Details**: Capture constraints precisely. - **Plan Like Da Vinci**: Build the question set first. - **Craft, Don't Code**: Ask fewer, better questions. - **Iterate Relentlessly**: Refine after answers. - **Simplify Ruthlessly**: Remove nonessential questions. # Deep Clarification Skill This skill provides patterns for intensive task clarification using Claude's native `AskUserQuestion` tool. ## When to Use **ALWAYS use this skill when:** - Starting any new feature implementation - The task could be interpreted multiple ways - There are architectural decisions to make - The scope is not 100% clear - The user's request is brief or high-level ## Clarification Framework ### Phase 1: Task Understanding Ask about the fundamental nature of the task: ```yaml AskUserQuestion: questions: - question: "What type of work is this?" header: "Task Type" mult