grilling

Interrogate plans and designs to expose gaps, assumptions, and unresolved dependencies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you uncover gaps, assumptions, and unresolved dependencies in a plan or design before you commit to building it.

Core Features & Use Cases

  • Relentless Clarification: It walks through the design or implementation tree one branch at a time until the approach is well understood.
  • Recommended Answers: For every question, it suggests a strong default answer so the discussion stays productive.
  • Codebase-Aware Probing: When an answer can be inferred from the repository, it explores the codebase instead of guessing.
  • Use Case: Use it when you have a draft plan, architecture idea, or feature proposal and want to pressure-test it before execution.

Quick Start

Ask the grilling skill to interview you about your plan or design one question at a time.

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

Stress-testing a design plan involves interrogating your approach one question at a time to expose gaps, assumptions, and unresolved dependencies before implementation begins.

What is the best way to clarify requirements for a codebase-informed feature proposal?

Clarifying requirements for a codebase-informed feature proposal is done through relentless clarification, walking through the implementation tree one branch at a time while exploring the repository to infer answers.

Can I use automated questioning to find unresolved dependencies in my architecture design?

Yes, you can use automated questioning to find unresolved dependencies in architecture design by having the system interview you about your plan one question at a time and provide recommended answers.

Does design review questioning provide answers or only ask questions?

Design review questioning provides a recommended strong default answer for every question it asks, ensuring the discussion stays productive while it probes your plan for gaps and assumptions.

When do I need to interrogate a technical plan before writing code?

You need to interrogate a technical plan before writing code when you have a draft plan, architecture idea, or feature proposal and want to pressure-test decisions and uncover unresolved dependencies before execution.