Menu
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Drive and read Ionwake's `__ionwake*` window instrumentation hooks (`__ionwakeScene` on /play, `__ionwakeShipyard` on /shipyard, and the dev-only `__ionwake` debug flags) from outside the page via the Chrome DevTools MCP. Use to read live sim/scene/clock state, screenshot the running app, drive the shipyard, load ship models, inspect a ship schema, log the WebTransport wire, or keep a backgrounded tab stepping.
Compact the current conversation into a handoff document for another agent to pick up.
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
Interview the user relentlessly about a game design concept or design until reaching shared understanding, stress-testing the concept and resolving each branch of the decision tree.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Based on SOC occupation classification
| description | Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases. |
| metadata | {"github-path":"skills/productivity/grilling","github-ref":"refs/tags/v1.0.1","github-repo":"https://github.com/mattpocock/skills","github-tree-sha":"ab318c66a36253e872b5d0bd271b3df8f6ef816f"} |
| name | grilling |
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.
If a question can be answered by exploring the codebase, explore the codebase instead.
