grill-me

Interrogate plans one question at a time to resolve assumptions and dependencies.

1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/tho/skills --skill grill-me-tho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/tho/skills/tree/main/skills/grill-me
Command: npx skills add https://github.com/tho/skills --skill grill-me-tho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you replace vague or unexamined plans with shared, decision-tree-consistent understanding by forcing every assumption, dependency, and branch to be clarified.

Core Features & Use Cases

  • Relentless plan probing: Walks through each part of a plan and asks targeted questions one at a time.
  • Branch-by-branch resolution: Resolves dependencies between decisions in sequence to reach consensus on tradeoffs.
  • Codebase-aware answers: Uses the codebase when a question can be answered by inspecting existing implementation.

Quick Start

Ask the AI to "grill me on this plan: [paste your plan/design here]" and respond only to the next question it asks.

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 plan to find hidden assumption conflicts?

To stress-test a product plan, you interrogate every assumption and dependency one question at a time until shared understanding is reached. This resolves conflicting branches by clarifying vague requirements across the decision tree.

What is the best way to align stakeholders on conflicting decision tree branches?

Aligning stakeholders on decision trees requires branch-by-branch resolution, walking through dependencies in sequence to reach consensus on tradeoffs. One-at-a-time questioning clarifies conflicting plan logic and resolves dependencies.

Can I review a design by having the AI inspect my codebase for existing implementation logic?

Yes, design review can be codebase-aware. When a question about your plan can be answered by inspecting existing implementation, the tool explores the codebase to validate assumptions and resolve dependencies accurately.

How do I start a requirements elicitation session to interrogate my product planning assumptions?

Start requirements elicitation by pasting your plan and asking to be grilled. The system will ask targeted interrogation questions one at a time, requiring you to resolve each assumption before moving to the next branch.

Does assumption testing work for resolving dependencies across complex plan branches?

Assumption testing works for complex branches by resolving dependencies between decisions in sequence. It interrogates each part of a plan individually to ensure your decision tree remains consistent and fully aligned.