Use Grill Me by Matt Pocock to clarify a plan through a structured interview. Choose the ordinary grilling conversation or the Grill with Docs mode when a software discussion also needs shared terminology and architectural records, then review the decisions before starting implementation.
Bring the plan and the choices that would change what gets built. Frame a design interview around the audience, constraints, and unresolved dependencies, then ask for settled decisions and warranted documentation changes before implementation is planned.
Include current terminology, code references, and the decision you cannot yet make.
Copy the request into a new Floatboat conversation and provide the required material.
Download FloatboatPreview and copy the request. It is not sent automatically from this page.
Reference: Grill Me https://github.com/mattpocock/skills/blob/main/skills/productivity/grill-me/SKILL.md Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding. My task: Use /grill-with-docs to examine partial order cancellation. Check our glossary and current code, clarify the domain rules, and propose only the glossary or ADR changes that are warranted before implementation. Expected deliverable: Resolved and open questions, plus only the glossary or ADR changes justified by the discussion.
Grill Me is Matt Pocock’s user-invoked interview entry, delegating its questioning to the companion grilling Skill. It maps a plan into dependent decisions and asks the choices that can be settled with the information currently available. For software discussions that should also refine project language and durable records, Grill with Docs combines grilling with domain-modeling. That mode checks the glossary, code, and existing architectural decisions, updates resolved terms in GLOSSARY.md, and records an ADR only when a consequential trade-off warrants it. These are two entry points into related methods, so this guide covers them together. Install the collection with its companions, choose the mode that fits the task, and review decisions and any file changes before implementation.
An uncertain product idea, a process change, and a software design discussion need different questions. Compare how Grill Me clarifies consequential choices, dependent decisions, and project terminology before those assumptions reach an implementation plan.
An early product idea benefits from questions that establish its audience, useful outcome, and real constraints. Use the ordinary interview to resolve choices that would change what gets built, rather than rushing into implementation. Record agreed direction-setting decisions and the questions that still prevent a clear plan.
A workflow change affects people and dependencies as well as the steps being edited. Compare the current process with the proposal, identify what must remain possible, and locate decisions that depend on one another. Resolve those questions before distributing implementation work so teams do not proceed on conflicting assumptions.
A software design discussion can use Grill with Docs to compare the proposal with current code, project terms, and existing decision records. Check terminology before updating a glossary or ADR, and change those documents only where the discussion warrants it. The record should reflect settled conclusions rather than speculative documentation churn.
A plan may contain two goals that cannot both be fully satisfied under the existing constraints. Bring the alternatives and their dependencies into the interview, then identify which choice matters first and what evidence can settle it. Record the agreed consequence; in documentation mode, update a durable decision record only when the tradeoff warrants one.
A design interview needs the current plan and the supporting project material. Choose ordinary Grill Me or the documentation mode according to the task, resolve consequential questions, and verify the decisions and warranted document changes before implementation begins.
Provide the plan and known constraints. Invoke /grill-me for the ordinary interview, or /grill-with-docs when project terminology and records should be part of the discussion.
Answer the current questions and correct misunderstandings. In document-aware mode, compare terms and decisions with the glossary, code, and existing ADRs.
Confirm settled choices and remaining gaps. Review any glossary or ADR changes, then decide whether the next task is further discussion, documentation, or implementation.
Read another Skill guide and check its original source before using it.
