Design Concept Grilling

Sources#

• Full Walkthrough: Workflow for AI Coding — Matt Pocock

Summary#

Matt Pocock's grill-me skill — a relentless interviewer prompt that walks down decision-tree branches one question at a time, with recommended answers — replaces "ask the agent for a plan" with "reach a shared understanding before any plan exists." The point is alignment, not output. The goal-state is what Frederick P. Brooks calls the design concept in The Design of Design: a shared idea held by all participants in the work. A PRD or a plan is downstream of the design concept; producing one without alignment first guarantees rework.

The skill (verbatim)#

"Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies one by one. For each question provide your recommended answer. Ask the questions one at a time…"

That's it. The skill is short on purpose — minimum surface area, maximum behavior change.

Why grill before plan#

Pocock observed that agents in plan mode "really eagerly try to produce a plan" — say "I think I've got enough" and ship a plan that papers over open questions. The plan reads fine, but it is wrong in ways that don't surface until implementation. Forcing the agent to interview first exposes the open questions while there is still time to answer them cheaply.

The recommendation-with-each-question pattern is load-bearing: it lets the user say "yes, agreed" most of the time, only debating where they actually disagree. A pure question-only interview wastes user attention on obvious calls.

Counter to the "specs to code" movement#

Pocock's strongest negative thesis: specs-to-code is vibe coding by another name. Defenders say "write a careful spec, hand to AI, fix the spec when the code is wrong, never look at the code." Pocock has tried it: it doesn't work.

Reasons:

• The code is the battleground, not the spec
• Specs that don't engage with code degrade into wish-lists
• The feedback loop runs through a layer (spec ⇄ AI ⇄ code) instead of where the bugs actually live (code ⇄ tests)
• Without code engagement, the developer's mental model of the system rots

Grilling sits on the opposite discipline: spec is downstream of alignment, alignment is upstream of any artifact, the developer keeps a hand in the code throughout.

Outputs of a grilling session#

A grilling session can run anywhere from 10 to 100 questions; Pocock has had sessions that went an hour. The artifact at the end is the conversation history itself — kept around as raw material for the PRD step. Pocock's write-a-PRD skill consumes this history (along with another short interview) to produce a destination document.

He explicitly does not review the PRD afterwards:

"What am I testing at this point? What are the failure modes I'm trying to test for? I know that LLMs are great at summarization. I have reached the same wavelength as the LLM. So all I'm doing is checking the LLM's ability to summarize."

This is only safe because the grilling session did the alignment work. Skip grilling and you must read the PRD.

Two essential documents#

After grilling, Pocock generates exactly two documents:

1. PRD (destination doc) — what the finished thing looks like, user stories, definition of done, out-of-scope list, implementation decisions, testing decisions, modules to be modified
2. Kanban (journey doc) — vertical slices into independently grabbable tickets (see Vertical Slice Tracer Bullets)

He then deletes (or closes) the PRD after implementation completes — see doc rot.

Module map appears in the PRD#

The PRD includes "modules to be modified" — concrete identification of which existing modules change and which new ones are introduced. This connects planning to architecture (see Deep Modules for Agents). The point is to keep the codebase shape in mind throughout planning, not as an afterthought during implementation.

When to skip grilling#

Grilling is for human-in-the-loop tasks. For a short well-scoped change ("rename this function across the codebase"), the overhead is wasted. The discipline scales with stakes: bigger feature, fuzzier brief, higher cost of going the wrong way → grill harder.

Connections#

• Matt Pocock — author of the skill
• Vertical Slice Tracer Bullets — the Kanban that follows the PRD
• Deep Modules for Agents — module map in PRD ties planning to architecture
• Agent Loop Pattern — grilling sits at the human-in-loop top of the funnel; loop drains the AFK bottom
• Context Window Smart Zone — grilling uses sub-agents to keep parent context small
• Agent Harness Engineering — "enforce invariants" at the planning layer is "reach alignment before any plan"
• Claude Code Best Practices — the explore→plan→code workflow has the same shape; grill-me is the more aggressive variant of the "explore" step
• Interaction Models — grilling is collaborative real-time iteration; turn-based interfaces are precisely what makes it clunky today, and an interaction model is the substrate that would make grilling-style collaboration feel native

Open questions#

• Can grilling be run AFK against another agent that holds the user's preferences? Pocock's answer in 2026 is "no, this part has to be human-in-the-loop" — but the question is open as agents get better at modeling their principal.
• How does grilling change for team work where multiple humans need to align? Pocock's hint: pair-program with the agent in the room, treat it as a third interlocutor.

Sources#

• Full Walkthrough: Workflow for AI Coding — Matt Pocock