grill-me

Runs a structured interview session to challenge and refine a plan or design.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/j172/bid --skill grill-me-j172
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/j172/bid/tree/main/.agents/skills/grill-me
Command: npx skills add https://github.com/j172/bid --skill grill-me-j172

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, gaps, and weak points that go unnoticed until implementation. This Skill subjects your plan to a relentless question-and-answer session that exposes flaws before they become costly mistakes. ## Core Features & Use Cases - Adversarial Interviewing: Runs a grilling session that probes your plan or design with tough, targeted questions. - Assumption Testing: Forces you to articulate and defend the reasoning behind each decision. - Use Case: Before presenting a product roadmap to stakeholders, run a grilling session to anticipate objections, uncover missing details, and strengthen weak points in your proposal. ## Quick Start Ask the assistant to run a grilling session on your current plan or design document.

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 plan before presenting it?

Run a grilling session on your plan to receive relentless, targeted questions that expose weak assumptions and gaps. You answer each challenge, refining the plan iteratively until it holds up under scrutiny.

What is a grilling session for design review?

A grilling session is an adversarial interview where the AI questions your design decisions one by one. It forces you to justify choices, revealing hidden risks and unstated assumptions before implementation begins.

Can I use this for documents other than plans?

The Skill is designed for plans and designs, but the interview format works for any artifact with defensible reasoning, such as proposals or architectures. Results depend on how clearly your input states its decisions.

When should I not use an adversarial plan review?

Avoid it for early brainstorming when ideas are still forming, since aggressive questioning can shut down exploration. It works best once a plan is concrete enough to defend with specific reasoning.