grill-me

Interview designs with structured decision-tree forks to reveal hidden assumptions.

5|2|Updated Nov 17, 2025
One-click install
npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill grill-me-outlinedriven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/grill-me
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill grill-me-outlinedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial interview helps teams reveal hidden assumptions and dependencies by forcing a structured, step-by-step questioning approach until a shared understanding is reached.

Core Features & Use Cases

  • Structured decision-tree grilling of designs and plans to surface gaps.
  • Clear recommendation per fork with rationale, ensuring no silent pivots.
  • Works across any domain; triggers when user requests hostile-but-fair scrutiny.

Quick Start

Provide a design or plan and let the process walk every fork until a clear shared recommendation 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 surface hidden assumptions in an architecture design review?

An adversarial design review reveals hidden assumptions by following a structured decision-tree workflow, asking one-question-at-a-time forks, and requiring explicit recommended outcomes with rationale for each branch.

What's the best way to adversarially grill a project plan before stakeholder approval?

Adversarially grilling a project plan involves applying hostile-but-fair scrutiny through a structured decision-tree, forcing step-by-step questioning until shared understanding and clear recommendations are reached across all forks.

When do I need an adversarial interview for product design discussions?

You need an adversarial interview for product design discussions when plans require thorough scrutiny to reveal hidden dependencies, ensuring no silent pivots occur during architecture decisions or stakeholder alignment.

How does a decision-tree workflow work for grilling design plans?

A decision-tree grilling workflow works by asking one-question-at-a-time forks sequentially, requiring explicit recommended outcomes with rationale at each branch to force structured scrutiny until shared understanding is reached.

Does adversarial plan review work across different technical domains?

Adversarial plan review works across any domain requiring thorough scrutiny, including architecture decisions and product design discussions, applying structured decision-tree questioning regardless of the specific technical context.