grill-me

Guide teams through structured questioning to reach shared understanding of plans.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Alfie728/my-skills --skill grill-me-alfie728
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/Alfie728/my-skills/tree/main/grill-me
Command: npx skills add https://github.com/Alfie728/my-skills --skill grill-me-alfie728

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or explicitly mentions "grill me".

Core Features & Use Cases

  • Relentless, focused questioning that reveals assumptions, constraints, and risks.
  • Systematic traversal of a decision tree to close open branches and align on scope, interfaces, and rollout.
  • Contextual summaries that surface decisions for quick validation or correction.

Quick Start

Ask one sharp question at a time to drive the plan toward explicit decisions, risks, and trade-offs until shared understanding is achieved.

Frequently Asked Questions about grill-me

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress-test a product management plan before rollout?

You stress-test a plan by applying relentless, focused questioning that reveals assumptions, constraints, and risks. This systematic traversal of the decision tree closes open branches and aligns scope, interfaces, and rollout considerations.

What is a decision tree approach for design reviews?

A decision tree approach for design reviews resolves each branch through pointed, sequential inquiries. It drives the plan toward explicit decisions and trade-offs until shared understanding is achieved across the team.

How do I conduct an interactive questioning session to examine trade-offs?

You conduct interactive questioning by asking one sharp question at a time. This prompts structured inquiries into scope, risks, interfaces, and rollout considerations, driving the plan toward explicit decisions.

Can I use focused questioning to define project scope and rollout risks?

Yes, focused questioning systematically traverses the decision tree to define scope and surface rollout risks. Contextual summaries are generated during the process to surface decisions for quick validation or correction.

What is the best way to align teams on explicit decisions during planning discussions?

The best way to align teams is through relentless, focused questioning that resolves each branch of the decision tree. It ensures decisions are explicit and trade-offs are thoroughly examined until shared understanding is reached.

When should I avoid using relentless questioning for plan reviews?

You should avoid relentless questioning when a plan or design is already fully explicit with no open decision branches. It is specifically built for scenarios requiring scope definition, risk examination, and unresolved trade-offs.