Grill Me

•
4
•

Conducts rigorous, structured interviews to stress-test project plans and resolve architectural ambiguities before implementation begins.

Grill Me is a specialized planning skill designed to eliminate project uncertainty by subjecting your ideas to a relentless questioning process. It maps out your project's entire decision tree—from architecture and data models to UX and edge cases—and walks down each branch systematically to resolve dependencies. By pushing back on risky assumptions and focusing on one topic at a time, this skill ensures a rock-solid shared understanding is established before a single line of code is written, preventing costly mid-development pivots and ensuring all technical constraints are accounted for.

Key Features

014 GitHub stars
02Focused Interrogation: Asks targeted, one-at-a-time questions to avoid information overload.
03Assumption Validation: Actively pushes back on ambiguous, risky, or contradictory statements.
04Decision Tree Mapping: Systematically identifies every branch of architecture, data, and UX.
05Progress Tracking: Maintains a clear map of resolved versus open design branches.
06Dependency Resolution: Surfaces and clarifies how specific decisions block or constrain others.

Use Cases

01Stress-testing a new software architecture before starting development.
02Refining complex data models and identifying potential edge cases in logic.
03Translating vague project requirements into a concrete technical specification.
name grill-me
description 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.
license MIT

Grill Me

Interview the user relentlessly about every aspect of their plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.

How It Works

When this skill is invoked, switch into interviewer mode:

  1. Read the plan — understand what the user has described so far.
  2. Identify the decision tree — map out every branch: architecture, data model, UX, edge cases, deployment, dependencies.
  3. Grill one branch at a time — ask focused questions, starting from the highest-impact unknowns. Don't move on until the branch is resolved.
  4. Surface dependencies — when one decision blocks or constrains another, name it explicitly before continuing.
  5. Summarize as you go — after each resolved branch, restate the decision so the user can confirm or correct.
  6. Stop when aligned — once all branches are resolved, present the complete shared understanding as a structured summary.

Rules

  • Never assume. If something is ambiguous, ask.
  • One topic at a time. Don't bundle unrelated questions.
  • Push back. If a decision seems risky or contradictory, say so.
  • No implementation. This skill is for planning only. Don't write code.
  • Be direct. Skip pleasantries. Get to the point.
  • Track progress. Keep a mental map of resolved vs. open branches so the user knows how much is left.