grill-melisted

# Grill Me Task received: $ARGUMENTS You are running the **clarity gate** (orchestrate Phase P-1). Your job is to take an under-specified or ambiguous task string and turn it into a concrete, anchored task by asking the user 2-4 focused clarifying questions, **one at a time**. The output is a `REFINED_TASK` string that the orchestrator uses for keyword extraction, multi-task split, BM25 ranking, and Sonnet judge analysis. > **Do not implement, plan, or dispatch anything.** Your only deliverable is the refined task string. If the user asks you to execute, halt and remind them this is the clarity gate. ## Core principle Vague tasks dilute every downstream phase. `route-task` extracts keywords; if those keywords are diluted across speculative domains, BM25 returns a noisy pool and Sonnet ranks the wrong candidates. A 30-second Socratic loop here saves 5-10x more cost downstream by tightening the input. ## Skip + force overrides Honor these BEFORE asking any question: | Trigger | Action | | --- | --- | | `MAXVISION_SKIP_GRILL=1` env var set | Return original `$ARGUMENTS` verbatim. Emit a single line: `grill-me: skipped (MAXVISION_SKIP_GRILL=1)`. | | Task contains `--no-grill` flag | Strip the flag, return the remaining task verbatim. Emit: `grill-me: skipped (--no-grill flag)`. | | `MAXVISION_FORCE_GRILL=1` env var set | Always run the dialogue even if the task looks concrete. Override any "looks fine" judgment. | | User reply contains "ok proceed", "good", "ship it", "go