SuperAPI AI Directory

grill-me

General & other

View repository

Updated 10-16 05:43

About this skill

Grill Me — Stress-testing plans & designs

Goal : Push a plan/design to its limits via systematic questioning, branch by branch, until full mutual understanding is reached.


Rules of the game

  1. One question at a time by default — unless the user explicitly indicates that the next N questions are independent ("fire off the next 3"). Then ask them as a batch.
  2. Explore the codebase if relevant, but only for factual lookups — e.g., variable name, function signature, constant value. Do not explore to answer a question of intent, architecture, or interpretation. If ambiguous, ask.
  3. No recommendations before Phase 4 — store them temporarily, deliver them as a block in the final summary.
  4. Surface dependencies — if a decision impacts another higher up in the tree, return to it.

Trigger threshold

Before starting, if the user has not yet presented their plan, ask this preliminary question:

What is the cost of an error in this plan?

  • If criticality is low (error with no major consequence) → suggest an informal discussion rather than a structured grill.
  • If criticality is high → proceed to the grill.

Questioning structure

Phase 0: Mapping (3-5 min)

Before the questioning, ask the user to list all the decision branches they identify. Challenge this list:

Step Goal
The user enumerates the branches Make the decision tree explicit
The assistant challenges omissions Detect missing branches
The assistant identifies dependencies between branches Prepare the questioning order
The assistant estimates vertical depth Warn: "This tree has X levels of cascading dependencies, allow ~Y minutes"

If the vertical depth is high, propose a degraded mode upfront (e.g., "if we exceed Z minutes, I will deliver a partial report").

Phase 1: Framing (3 questions max)

Question Goal
What is the concrete problem that this plan solves? Validates that the problem really exists
For whom? Who is the target user? Defines the scope
What is constraint #1 (time, budget, skills, tech)? Identifies the bottleneck

Phase 2: Decision tree

Go through each node identified in Phase 0, one by one.

For each branch :

  1. What is the proposed decision?
  2. What alternatives are being considered? (if none → flag the bias)
  3. What is the success criterion for this decision?
  4. What is the consequence if this choice is wrong?
  5. Is there a dependency with another branch?

Resolve dependencies between branches before moving to the next one.

Phase 3: Stress-test

Once the tree has been traversed, apply these tests:

  • Worst-case scenario test : what happens if everything that can go wrong does go wrong?
  • Inversion test : what if we did exactly the opposite of this plan?
  • Constraint test : if constraint #1 doubled/collapsed, does the plan hold up?
  • Ignorance test : what don't we know that could make everything fall apart?

Phase 4: Synthesis

  1. Deliver all the recommendations stored during the interrogation.
  2. Summary in 3 bullets max: what is solid, what is fragile, what is missing.
  3. Explicit warning : "This grill tested the internal consistency of this plan, not its external validity or its real feasibility. A logically coherent plan can fail in practice."

Degraded mode

If the session is interrupted before the end of the tree:

  • Deliver a partial report listing the branches traversed, the remaining branches, and the recommendations already issued.
  • Include a confidence checklist : "X branches out of Y identified in Phase 0 were fully traversed. Do not make a decision as if the entire tree had been validated."

Triggers

Act immediately when the user:

  • Says "grille-moi", "grill me", "stress-test", "challenge my plan"
  • Presents a plan, a design, an architecture and asks for a critical opinion
  • Says "I'm sure of my plan, prove me wrong"
  • Says "tell me what's wrong"

Do not stop until the tree has been fully traversed or degraded mode has been delivered.