grill-me

Interrogate plans or designs to reveal assumptions and decision gaps.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/ResearchMonkey/Foundation_template --skill grill-me-researchmonkey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/ResearchMonkey/Foundation_template/tree/main/.claude/skills/grill-me
Command: npx skills add https://github.com/ResearchMonkey/Foundation_template --skill grill-me-researchmonkey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grill Me interrogates a plan or design to reveal assumptions and decision gaps, forcing a path to shared understanding and robust design.

Core Features & Use Cases

  • Relentless questioning to uncover hidden assumptions and risks in plans or designs.
  • Branch-by-branch interrogation to ensure dependencies are resolved and trade-offs understood.
  • Effective during design reviews, architecture discussions, and Jira issue discussions to improve quality and buy-in.

Quick Start

Provide your plan or design and ask the assistant to grill it to shared understanding, branch by branch.

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 uncover hidden assumptions?

Stress-testing a plan involves interrogating its design branch by branch to reveal hidden assumptions and decision gaps. This resolves dependencies and trade-offs, guiding you to a shared understanding and robust design.

What is branch-by-branch interrogation for design reviews?

Branch-by-branch interrogation is a decision-making process that questions each part of an architecture diagram or design document to resolve dependencies. It ensures trade-offs are understood and outcomes are documented for traceability.

How do I identify decision gaps in architecture diagrams during early design reviews?

You identify decision gaps in architecture diagrams by applying relentless questioning to the design. This interrogates the plan to reveal hidden assumptions and risks, ensuring dependencies are resolved and trade-offs are understood.

Can I use this to improve requirements gathering for Jira issues?

Yes, you can use it to improve requirements gathering for Jira issues during early design discussions. It interrogates the issues to reveal assumptions and decision gaps, forcing a path to shared understanding and robust design.

What is the best way to document outcomes for decision traceability in planning?

The best way to document outcomes for decision traceability is to guide the planning process through branching questions that resolve dependencies. This interrogates the plan to reveal gaps and documents the results for shared understanding.