grilling

Interviews plans one question at a time with recommended answers.

345|9|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/dmmulroy/skills --skill grilling-dmmulroy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grilling
Source: https://github.com/dmmulroy/skills/tree/main/grilling
Command: npx skills add https://github.com/dmmulroy/skills --skill grilling-dmmulroy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you uncover weak assumptions, missing decisions, and hidden dependencies in a plan or design before you invest in building it.

Core Features & Use Cases

  • Relentless Design Interviewing: It walks through a plan one decision at a time, asking focused questions until the design is fully understood.
  • Recommended Answers: Each question comes with a suggested answer so you can quickly converge on a sensible direction.
  • Evidence-Driven Exploration: When a question can be answered by inspecting the codebase, it switches from asking to investigating.
  • Use Case: A developer preparing a new architecture can use this Skill to pressure-test the proposal, expose risks, and clarify tradeoffs before implementation begins.

Quick Start

Use the grilling skill to challenge my plan one question at a time and recommend answers as you go.

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 software architecture plan before implementation?

A design review interviews a plan one question at a time to expose hidden dependencies and weak assumptions. It applies relentless scrutiny to surface tradeoffs and validate architecture decisions before implementation begins.

What is the best way to validate design assumptions and tradeoffs?

Validating design assumptions requires focused, sequential questioning that probes each decision individually. By investigating the codebase for evidence and providing recommended answers, this approach clarifies tradeoffs and surfaces missing decisions.

How do I conduct a design review for hidden dependencies in a plan?

Conducting a design review for hidden dependencies involves interviewing the plan with relentless, one-question-at-a-time scrutiny. Each question includes a recommended answer to quickly converge on a sensible direction.

Can I use automated questioning to surface missing decisions in a workflow?

Automated questioning surfaces missing decisions by enforcing sequential prompts that address assumptions and tradeoffs. When evidence can be gathered directly, it defers to codebase exploration to investigate the answer.

Does plan validation require switching to codebase exploration for evidence?

Plan validation switches to codebase exploration when a question can be answered by inspecting the code directly. This evidence-driven approach ensures answers are grounded in actual project data rather than assumptions.