grill-me

Interview plans or designs to reveal hidden assumptions and dependencies.

Updated May 2, 2026
One-click install
npx skills add https://github.com/maxenergy/skills --skill grill-me-maxenergy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/maxenergy/skills/tree/main/skills/productivity/grill-me
Command: npx skills add https://github.com/maxenergy/skills --skill grill-me-maxenergy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Relentlessly interrogate a plan or design to reveal hidden assumptions, dependencies, and gaps, ensuring alignment before execution.

Core Features & Use Cases

  • Relentless questioning that covers all branches of a design.
  • Step-by-step dependency resolution to avoid overlooked consequences.
  • Use in product planning, architecture reviews, and design critiques.

Quick Start

Ask the AI to grill your plan until all decisions are understood and agreed.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I interrogate a design or plan to reveal hidden dependencies?

To interrogate a design and reveal hidden dependencies, use a relentless, one-question-at-a-time interview workflow that covers all decision tree branches and exposes overlooked consequences.

What is the best way to conduct an architecture review for hidden assumptions?

An architecture review for hidden assumptions benefits from a structured, stepwise questioning workflow that provides recommended answers for each question to ensure total alignment before execution.

Can I use stepwise questioning for scenario planning and product alignment?

Yes, you can apply stepwise questioning to scenario planning and product alignment by relentlessly interviewing plans to resolve dependencies and achieve one-question-at-a-time clarity.

How does a decision tree questioning workflow work for design critiques?

A decision tree questioning workflow for design critiques works by relentlessly covering all branches of a design step-by-step, ensuring dependencies are resolved and gaps are identified.

When do I need to relentlessly interview a plan before execution?

You need to relentlessly interview a plan before execution when scenario planning, architecture reviews, or design discussions require alignment and dependency resolution to avoid overlooked consequences.

Should I use a structured questioning workflow for small planning decisions?

A structured questioning workflow is useful for planning decisions of any scale where hidden assumptions and dependencies must be revealed, ensuring alignment and stepwise dependency resolution.