vc-intent-clarify

Output style: lead each question with the recommended option; plain language, no filler, process/development-protocols/communication-standards.md.

Two-mode intent clarification: SIMPLE (direct, 3-5 reads) and DEEP (research subagent first, then questions).

Scores a user request's ambiguity and, when Tier 2 triggers, produces a structured, multi-dimension clarification suite with option-rich questions rather than open-ended prompts. Uses vc-scenario, vc-predict, and vc-sequential-thinking style reasoning to generate questions, not just to answer them.

This is the highest-leverage skill in the system. Poor intent clarification wastes entire phase programs. Invest in the question generation step.

---

When To Invoke

At ORCHESTRATOR before every routing decision for new user requests. Check auto-skip conditions first. If none apply, score the four signals and act on the resulting tier.

---

Auto-Skip Conditions

These conditions force Tier 0 regardless of the ambiguity score. Check these FIRST.

1. Continuation phrases, "go", "continue", "proceed", "just do it", or similar standalone instruction
2. Mid-phase-program execution, active phase plan is selected and approved, user is advancing
3. Trivial fix, single-file, under 15 lines, no schema/API/auth changes
4. Explicit mode command, "ENTER EXECUTE MODE", "ENTER RESEARCH MODE", etc.
5. Resuming active plan, an existing active plan is identified and confirmed
6. Pure information question, "What is X?", "How does Y work?" mapping to a single obvious routing target

When an auto-skip condition matches, produce only a 1-sentence restatement of intent and route immediately per the existing routing protocol. Do not announce the tier. Do not surface any questions.