grill-me

Interrogate plans and designs to uncover decisions and dependencies.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Liz2Z/oh-my-skills --skill grill-me-liz2z
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/Liz2Z/oh-my-skills/tree/main/skills/grill-me
Command: npx skills add https://github.com/Liz2Z/oh-my-skills --skill grill-me-liz2z

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Relentlessly interview and challenge a plan or design to surface assumptions, dependencies, and risk, guiding stakeholders toward a shared understanding.

Core Features & Use Cases

  • Systematically walk through each design decision, identifying dependencies and potential failure points.
  • When applicable, explore the codebase to verify assumptions and reveal implementation details.
  • Use for design reviews, architecture validation, and thorough plan stress-testing.

Quick Start

Present your plan and have the assistant grill every decision to reach alignment.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I interrogate a design to uncover hidden dependencies and risks?

To interrogate a design and uncover risks, you systematically walk through each decision branch-by-branch, challenging assumptions until stakeholders reach a shared understanding of dependencies and potential failure points.

What is a decision-tree interrogation workflow for architecture plans?

A decision-tree interrogation workflow for architecture plans is an interactive process that systematically questions every design choice, ensuring branch-by-branch resolution of dependencies and thorough risk assessment before implementation.

Can I use this to explore a codebase and verify assumptions during a design review?

Yes, you can explore the codebase during a design review to verify assumptions, reveal implementation details, and confirm that the proposed architecture aligns with existing dependencies and structural constraints.

What's the best way to stress-test a solution proposal before stakeholder alignment?

The best way to stress-test a solution proposal is to relentlessly interview and challenge the plan, surfacing underlying assumptions and dependencies to guide stakeholders toward a thoroughly scrutinized, shared understanding.

How do I conduct a risk analysis on a plan with multiple design decisions?

Conduct risk analysis on a plan by systematically walking through each design decision, identifying dependencies and potential failure points through interactive questioning until all branches are fully resolved.

When do I need a systematic design review instead of a simple plan presentation?

You need a systematic design review when a plan involves complex architecture, multiple stakeholders, or significant risk, requiring thorough scrutiny and stress-testing to surface assumptions and achieve alignment.