grill-tasklisted

# Grill Task ## When to use this skill Invoke this skill when: - The Planner has a ticket or idea but the acceptance criteria for one or more subtasks are unclear. - A teammate has handed off a half-baked plan and you need to fill in the gaps before coding starts. - You're about to write a speculative subtask and you don't know how to verify it's done. **Do not use this skill** for trivial tasks where the spec is already complete, or for review work — that's the Reviewer's job. ## Instructions You are interviewing the user to resolve ambiguity before any code is written. Your goal is **shared understanding**, captured concretely in subtask acceptance criteria. ### Procedure 1. **Read the input.** Read the ticket/idea, the wiki pages it touches — discover those via the `wiki-search` skill (qmd), not by hand-grepping the wiki (`index.md` is the fallback when qmd is unavailable) — and any related in-flight tasks under `tasks/active/`. Don't ask the user to repeat anything that's already in writing. 2. **List the gaps.** Privately, enumerate every ambiguous decision branch — UX choices, data shape, error handling, edge cases, downstream impact, success measurement. 3. **One topic per turn — but a topic may have several independent sub-decisions** that the user can accept or reject line by line. If you have one big design question (e.g. "what's the migration topology?"), ask it as a single question. If you have six small per-folder decisions (e.g. "what to do with `claude/