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.
Start a fresh conversation. Replace the highlighted placeholders.
Use grilling to stress-test [plan or design] before implementation by asking one question at a time and waiting for my answer before continuing.
Required inputs
[plan or design]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: grillingdescription: 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.category: "productivity"risk: "safe"source: "community"source_repo: "mattpocock/skills"source_type: "community"date_added: "2026-06-19"author: "Matt Pocock"license: "MIT"license_source: "https://github.com/mattpocock/skills/blob/main/LICENSE"tags: - productivity - workflow - coding-agentstools: - claude-code - codex-cli - cursor
When to Use
Use when this workflow matches the user request: 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.
_Source: mattpocock/skills (MIT)._Interview the user about relevant uncertainties in the supplied plan until the stated decision criteria are resolved or the user ends the interview. 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.
Example
User request:
Use @grilling for this task: Interview the user relentlessly about a plan or design.
Limitations
Requires the upstream tool, account, API key, or local setup when the workflow names one.
Does not authorize destructive, production, paid, or external-message actions without explicit user approval.
Validate generated artifacts or recommendations against the user's real sources before treating them as final.