Systematic questioning to clarify requirements, goals, and constraints. Use when there's ambiguity about what the user wants, hidden complexity needs uncovering, or you need to understand before proceeding. Triggers on unclear requirements, vague goals, or when other skills encounter fundamental ambiguity.
Probes for clarity when requirements are ambiguous or hidden complexity might derail implementation. Triggers on vague goals, unclear constraints, or when other skills encounter fundamental ambiguity.
/plugin marketplace add dhruvbaldawa/ccconfigs/plugin install essentials@ccconfigsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
reference/examples.mdSkip when requirements are already clear or user wants to proceed without clarification.
Probe deeper than surface-level:
Dig deeper when answers reveal complexity. Don't jump topics when current one has unexplored depth.
Use AskUserQuestion with questions array for 2-4 related questions exploring different angles of the same area.
Stop when:
Summarize what you've learned:
**Clarified Requirements:**
- **Goal**: [specific goal]
- **Constraints**: [hard limits]
- **Success criteria**: [how we'll know it worked]
- **Key tradeoffs**: [prioritizing vs deprioritizing]
- **Open questions**: [if any]
| Skill | When to use interviewing first |
|---|---|
| Brainstorming | User unclear about what they want (not just how) |
| Technical Planning | Requirements too vague to plan |
| Debugging | Problem description unclear |
| Blog Writing | Topic or purpose unclear |
For writing, also ask: What's the core message? Who's the audience? What triggered this?
See reference/examples.md for project and writing interview flows.
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.