grill-me

Interview users through decision branches to clarify plans and designs.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/RemseyMailjard/superpowers --skill grill-me-remseymailjard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/RemseyMailjard/superpowers/tree/main/.github/skills/grill-me
Command: npx skills add https://github.com/RemseyMailjard/superpowers --skill grill-me-remseymailjard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interview the user relentlessly about a plan or design to ensure shared understanding, surfacing assumptions and dependencies by traversing each branch of the decision tree.

Core Features & Use Cases

  • Guided questioning that probes for missing requirements and potential conflicts.
  • Branch-aware reasoning that tracks dependencies between decisions and surfaces gaps.
  • Structured documentation of the rationale and recommended next steps for each decision.

Quick Start

Begin by asking targeted, branch-aware questions about the plan until every decision is clarified.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I validate a product plan to ensure stakeholders have shared understanding?

You validate a plan for shared understanding by applying structured, branch-aware questioning that traverses the decision tree to surface hidden assumptions, dependencies, and potential conflicts among stakeholders.

What is decision-tree exploration for design reviews?

Decision-tree exploration for design reviews is a structured questioning method that iterates through every branch to clarify requirements, track dependencies between decisions, and document the rationale for recommended next steps.

How do I surface assumptions and dependencies in a roadmap before implementation?

You surface assumptions and dependencies in a roadmap by relentlessly interviewing the plan across every decision branch, probing for missing requirements and conflicts until every decision is fully clarified.

Does branch-aware questioning work for engineering strategy validation?

Yes, branch-aware questioning works for engineering strategy validation by applying structured decision-tree exploration across strategy contexts to iterate toward shared understanding and document recommended next steps.

What is the best way to grill a design plan for missing requirements?

The best way to grill a design plan for missing requirements is to use targeted, branch-aware questions that probe for conflicts, track dependencies between decisions, surface gaps, and document structured rationale.

When should I not use structured questioning for stakeholder alignment?

You should avoid structured questioning for stakeholder alignment when a decision tree cannot be mapped, or when rapid consensus is needed without documenting rationale and recommended next steps for each decision branch.