Clarify ambiguity in user requests, strategies, or approaches. Routes to the appropriate sub-skill. Trigger on "clarify", "명확히", "뭘 원하는 건지", "뭘 놓치고 있지", "blind spots", "관점 전환", "다른 방법 없을까", "/clarify". Sub-skills — vague (requirement clarification, "요구사항 정리", "spec this out"), unknown (strategy blind spots with Known/Unknown quadrants, "4분면 분석", "assumption check", "가정 점검"), metamedium (content vs form reframing, "내용 vs 형식", "diminishing returns", "형식을 바꿔볼까").
Route to the correct sub-skill based on the user's need. All sub-skills share a common principle: hypothesis-driven questioning via AskUserQuestion (never open questions in plain text).
| Sub-skill | When | Read |
|---|---|---|
| vague | Ambiguous requirements need concrete specs | vague/SKILL.md |
| unknown | Strategy/plan needs blind spot analysis (Known/Unknown quadrants) | unknown/SKILL.md |
| metamedium | Stuck optimizing content, need form-level reframing | metamedium/SKILL.md |
vagueunknown (surface what you don't know you don't know)metamedium (change the medium, not just the message)If unclear which sub-skill fits, use AskUserQuestion: