From vp-guided-focus
Guided focus questioning to align on requirements before planning or complex tasks. Use when asked to "focus first", "ask me questions before planning", "guided focus", "help me clarify requirements", "let's align before starting", or proactively when detecting complex/ambiguous tasks that would benefit from requirement clarification before entering plan mode or execution. Always ask the user whether to activate before starting proactively. Boundary: not for simple, unambiguous tasks with clear requirements.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vp-guided-focus:guided-focusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Structured, one-at-a-time questioning to converge on requirements and decisions before planning or execution. Each question presents options with descriptions, trade-off differences, and a recommended choice with reasoning.
Structured, one-at-a-time questioning to converge on requirements and decisions before planning or execution. Each question presents options with descriptions, trade-off differences, and a recommended choice with reasoning.
/guided-focus
/guided-focus 5
Help me clarify before we plan
Ask me questions first, then plan
When NOT to use: Single-file edits, bug fixes with clear reproduction steps, tasks where the user provides explicit requirements, or when the user has already described a clear plan.
/guided-focus or asks to clarify firstDefaults (user can override via arguments or during the session):
| Parameter | Default | Override Example |
|---|---|---|
| Question count | 10 | /guided-focus 5 or /guided-focus --questions 5 |
| Min options per question | 3 | /guided-focus --min-options 4 |
Ask questions one at a time. Wait for user response before proceeding.
Question format (use bullet list, not table — safe for narrow terminals):
### Question [current]/[total] — [Topic]
[Context sentence explaining why this question matters]
**A. [Option name]**
- Description: [what this option means]
- Difference: [how it differs from other options]
- Recommendation: Weak / Moderate / Strong
**B. [Option name]**
- Description: ...
- Difference: ...
- Recommendation: ...
**C. [Option name]**
- Description: ...
- Difference: ...
- Recommendation: ...
**Recommended: [letter] — [option name]**: [1-2 sentence reasoning]
Recommendation scale: Weak = viable but not ideal, Moderate = good fit, Strong = best fit for this context.
Question behavior rules:
[current]/[total] and update total if it changesUser response flexibility:
If any questions were skipped/deferred during Phase 2:
Generate a structured summary of all decisions:
## Focus Summary
**1. [Topic]**: [Decision] [confidence]
**2. [Topic]**: [Decision] [confidence]
...
### Uncertain Decisions
- **[Topic]**: [Decision marked as uncertain] — may need revisiting during implementation
### Undecided
- **[Topic]**: Deferred — [reason or context]
Confidence markers: [confirmed] | [uncertain] | [undecided]
After presenting the summary:
[current]/[total]npx claudepluginhub vdustr/vp-claude-code-marketplace --plugin vp-guided-focusOrchestrates structured Socratic interviews to clarify ambiguous requirements using a dedicated interviewer agent and Ambiguity Score. Useful for vague ideas; invoke via /deep-interview or keywords.
Clarifies vague requests via Socratic questioning, focusing on one key uncertainty (goals, scope, constraints, completion criteria) at a time to produce actionable requirements. Activates on deep-interview requests or unclear specs.
Leads Socratic discussions to clarify ideas, challenge assumptions, and surface blind spots before implementation. Activates on '/discuss' or phrases like 'discuss this'.