grilling

Interrogate plans and designs to surface assumptions, dependencies, and missing decisions.

1|Updated Mar 19, 2026

Search Tags:#planning #requirements #interview #design review #risk analysis #grilling

Ready to run

npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill grilling-ian-pascoe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grilling
Source: https://github.com/ian-pascoe/dotfiles-chezmoi/tree/main/dot_agents/skills/grilling
Command: npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill grilling-ian-pascoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you pressure-test a plan or design before implementation by systematically exposing assumptions, dependencies, and unresolved decisions.

Core Features & Use Cases

Relentless Design Review: Walks through every branch of a plan one question at a time so you can resolve ambiguity early.
Recommended Answers: Provides a suggested answer for each question to help you move faster and compare options.
Codebase-Aware Probing: Looks for answers in the codebase when the question can be resolved from existing files instead of asking blindly.
Use Case: Before launching a feature, use this Skill to uncover missing requirements, integration risks, and implementation order.

Quick Start

Use the grilling skill to interview my plan for a new feature one question at a time and recommend answers until we have a shared understanding.

Frequently Asked Questions about grilling

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

FAQPage Schema

How do I stress-test a product plan before implementation?▼

To stress-test a product plan, you systematically interrogate the design to surface hidden assumptions, dependencies, and unresolved decisions one question at a time. This exposes integration risks and missing requirements before you build.

What is a design review interview for uncovering missing requirements?▼

A design review interview is a process of walking through every branch of a plan sequentially to resolve ambiguity. It probes your design to expose unresolved decisions and missing requirements before development begins.

How do I identify dependencies and risks in a technical design?▼

You identify dependencies and risks by applying relentless one-question-at-a-time probing to your technical design. This method exposes hidden assumptions and integration risks early in the planning phase.

Can I automate design review questions using my existing codebase?▼

Yes, codebase-aware probing looks for answers in existing files instead of asking blindly. It explores your codebase to resolve questions automatically when answers can be derived from current implementations.

Does this one-question-at-a-time interviewing method work for workflow designs?▼

Yes, this interviewing method applies to product, technical, and workflow designs. It walks through every branch of your workflow to resolve ambiguity and surface missing decisions before implementation.

What is the best way to pressure-test ideas before building a feature?▼

The best way to pressure-test ideas is conducting a systematic interview that provides recommended answers for each question. This helps you move faster, compare options, and reach a shared understanding before implementation.