grilling

Interrogate plans one question at a time to expose missing decisions.

Updated May 28, 2026
One-click install
npx skills add https://github.com/haryelramalho/skills --skill grilling-haryelramalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grilling
Source: https://github.com/haryelramalho/skills/tree/main/skills/community/grilling
Command: npx skills add https://github.com/haryelramalho/skills --skill grilling-haryelramalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn an under-specified plan or design into a fully examined decision set by forcing assumptions, dependencies, and tradeoffs into the open.

Core Features & Use Cases

  • One-question-at-a-time interviewing: It asks a single focused question, waits for the answer, and then continues.
  • Recommendation-driven prompts: Each question includes a suggested answer to speed up alignment and decision-making.
  • Codebase-aware validation: When a decision can be checked in the repository, it inspects the codebase instead of guessing.
  • Use Case: Use it before starting a feature, system redesign, or workflow change to uncover gaps early and reduce rework.

Quick Start

Use the grilling skill to interrogate my plan one question at a time until every major decision and dependency is resolved.

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 plan before implementation to expose hidden assumptions?

Stress-test a plan before implementation by systematically interrogating the design to surface hidden assumptions, missing decisions, and unresolved dependencies. This validation process forces tradeoffs into the open through focused, sequential questioning.

What's the best way to validate assumptions during architecture review?

Validate assumptions during architecture review by applying rigorous interrogation to your design. Ask focused questions one at a time, wait for answers, and inspect the codebase when decisions can be verified against repository contents instead of guessing.

How do I interrogate a feature plan to find missing decisions and dependencies?

Interrogate a feature plan to find missing decisions by using a sequential single-question prompting approach. Each question includes a recommended answer to speed up alignment, ensuring all major dependencies are resolved before you build.

Does design validation work with existing codebase contents for verifying decisions?

Design validation works with existing codebase contents by exploring the repository when a decision can be derived from existing code. This codebase-aware checking prevents guessing and grounds the validation in actual repository contents.

When do I need to stress-test a plan before building a feature?

You need to stress-test a plan before building a feature when you want rigorous validation to uncover gaps early. Apply this interrogation to pre-build planning, system redesigns, architecture reviews, and workflow changes to reduce rework.

Can I use sequential questioning to validate an under-specified design?

You can use sequential questioning to validate an under-specified design by asking one focused question at a time and waiting for the answer. This turns an incomplete plan into a fully examined decision set by forcing tradeoffs into the open.