grill-me

Interrogate plans and designs with structured questions to surface ambiguities.

13|3|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/misty-step/harness-kit --skill grill-me-misty-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/misty-step/harness-kit/tree/main/skills/.external/petekp-grill-me
Command: npx skills add https://github.com/misty-step/harness-kit --skill grill-me-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Relentlessly interrogates a plan or design to surface gaps, assumptions, and misalignments, ensuring all decisions are clearly understood and agreed upon.

Core Features & Use Cases

  • Relentless, branch-by-branch questioning to surface dependencies and risks.
  • Provides recommended answers for each question to accelerate stakeholder alignment.
  • Ideal for early product design, architecture reviews, and design stress-testing with key stakeholders.

Quick Start

Ask one clarifying question at a time until a shared understanding of the plan is reached.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I align stakeholders on an architecture decision before implementation?

Early product design stress-testing surfaces gaps and hidden assumptions through relentless interrogation of a plan. Providing recommended answers for each decision branch accelerates stakeholder alignment and clarifies ambiguous design requirements.

How do I interrogate a product plan to surface hidden dependencies?

Questioning proceeds by asking one clarifying question at a time until shared understanding of the plan is reached. This single-question pacing methodically traverses each decision tree branch to resolve ambiguities.

Does this design review method work for early-stage product plans?

Each decision branch includes recommended answers to accelerate stakeholder alignment during the interrogation. These recommendations provide a baseline consensus path, helping stakeholders quickly resolve design ambiguities and move forward.

When should I avoid using a decision tree for design reviews?

You should avoid using a decision tree for design reviews when clear consensus is not required or when the plan is already in late-stage execution. This rigorous interrogation is specifically built for early-stage designs where surfacing misalignments is critical.