Turn fuzzy intent into one clear problem statement and a small question handle. Use when the user is not ready to ask yet, feels mentally foggy, or needs the question boundary tightened before decomposition or reframing.
Convert a vague thought into a bounded problem statement with a few stable question anchors.
[stages: preflight>detect>analyze>handoff>audit | scope: repo|diff|paths(glob,...) | policy: evidence,quality-gates{docs},deterministic-output | lens: inversion-focus | output: md(contract=v1)]
This skill uses inversion-focus because it keeps the work aligned with: Reduce cognitive load, define by exclusions and one dominant constraint, then state the problem plainly.
RAW_TOPIC (string; required): Messy topic, rough thought, or problem statement draft.AUDIENCE (string; optional): Who the future answer or decision is for.CONSTRAINTS (list; optional; shape: {CONSTRAINT}): Known time, resource, domain, or evidence constraints.FOG_KEYS (list; required; shape: {KEYWORD}): Three concrete anchor words that represent the core issue.NEGATIVE_SPACE (list; required; shape: {AVOID}): What the future question should avoid or not become.PRIMARY_CONSTRAINT (string; required): Single dominant constraint that most limits the question.PROBLEM_STATEMENT (string; required): One clear problem-definition sentence.NEXT_RECOMMENDED_SKILL (string; required): Smallest useful next question-design step.primary_lens: inversion-focuswhy: Question clarification should lower cognitive load, define the negative boundary first, and collapse ambiguity into one usable problem statement.artifacts_in: noneartifacts_out: ask-clarify-question.v1Think and operate in English, but deliver the final response in Korean. 쉽고 간결한 한국어로 답하라. 전문 용어 금지. 핵심만 간단하게.
Output the PROBLEM_STATEMENT as a single sentence up front.
Then show:
Follow immediately with the NEXT_RECOMMENDED_SKILL.