grill-me

Stress-test plans through structured decision-tree questioning with codebase-aware answers.

Updated May 26, 2026
One-click install
npx skills add https://github.com/XWIlluDelu/agent-share --skill grill-me-xwilludelu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/XWIlluDelu/agent-share/tree/main/lib/grill-me
Command: npx skills add https://github.com/XWIlluDelu/agent-share --skill grill-me-xwilludelu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you find gaps, hidden assumptions, and weak dependencies in a plan by forcing a structured, branch-by-branch alignment until you reach shared understanding.

Core Features & Use Cases

  • Relentless decision-tree questioning: Walks through every relevant branch of the design until dependencies are resolved one-by-one.
  • Clarified, actionable answers: For each question, produces a recommended answer to move the plan forward.
  • Codebase-aware exploration: If a question can be answered by reviewing the codebase, it will do so instead of guessing.
  • Use cases: Stress-testing a product design, grilling an engineering approach, or validating a plan when someone says "grill me".

Quick Start

Ask an AI to run the grill-me interview to break down your plan question-by-question until all decision dependencies are clarified.

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 design to find hidden assumptions and weak dependencies?

You can stress-test a plan by applying a relentless, one-at-a-time questioning framework that forces branch-by-branch alignment, clarifying tradeoffs and dependency mapping until shared understanding is reached.

What is the best way to validate architecture decisions and resolve tradeoffs?

Validating architecture decisions works best through a structured decision-tree walkthrough that elicits one-at-a-time answers, resolving tradeoffs and dependency mapping until all branches reach shared understanding.

Can I use a decision tree questionnaire to map dependencies in an engineering plan?

Yes, you can use a decision tree questionnaire to map dependencies by walking through every relevant branch of your engineering plan and resolving dependencies one-by-one until the design is fully validated.

Does requirements gathering work with codebase-aware exploration to validate existing implementation facts?

Requirements gathering works with codebase-aware exploration by reviewing the codebase to answer implementation questions directly instead of guessing, ensuring plan validation relies on factual codebase data.

How do I conduct a design review to ensure plan validation uncovers all gaps?

You can conduct a design review for plan validation by using a single-question interaction rhythm that forces structured, branch-by-branch alignment, uncovering gaps and weak dependencies until all decisions are clarified.

When should I not use a single-question interview approach for dependency mapping?

Avoid using a single-question interview approach for dependency mapping when your plan requires rapid, unstructured brainstorming rather than a strict, branch-by-branch decision tree walkthrough to resolve tradeoffs.