grill-me

Ask one question at a time to resolve plan ambiguities and dependencies.

4|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/shushuzn/Rairos --skill grill-me-shushuzn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/shushuzn/Rairos/tree/main/skills/grill-me
Command: npx skills add https://github.com/shushuzn/Rairos --skill grill-me-shushuzn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you clarify and validate a plan or design by exposing hidden assumptions, ambiguous requirements, and unresolved dependencies until you reach shared understanding.

Core Features & Use Cases

  • Relentless plan grilling: Forces step-by-step alignment by asking one question at a time and following the decision tree.
  • Branch-by-branch resolution: Resolves dependencies between decisions so earlier choices don’t contradict later ones.
  • Code-aware questioning: If an answer can be found in the codebase, it instructs you to explore the codebase instead of guessing.

Quick Start

Tell the Skill: “Grill me on this plan: [paste your plan], and keep asking until every branch is resolved and I can confirm the recommended answers.”

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I validate a system design and resolve ambiguous requirements?

Validating system design requires interrogating requirements and assumptions through iterative questioning. This process exposes hidden dependencies and forces step-by-step alignment by asking one question at a time until shared understanding is reached.

What is the best way to stress-test an architecture plan for misalignment?

Stress-testing architecture plans involves branch-by-branch resolution to ensure earlier choices do not contradict later ones. It applies decision-tree style design reviews to expose unresolved dependencies and validate execution planning.

How do I check my codebase to answer design review questions?

During design reviews, if an answer can be found in the codebase, you should explore the codebase directly instead of guessing. This code-aware questioning prevents assumptions and grounds architectural decisions in existing implementation.

Can I use this for early execution planning and dependency resolution?

Yes, it applies directly to dependency resolution during early execution planning. It grills users on their plans to resolve ambiguity, ensuring every branch of the decision tree is addressed and dependencies are fully resolved.

When do I need to use assumption testing for plan validation?

Assumption testing is needed when plans contain hidden ambiguities or unresolved dependencies. It forces iterative convergence by asking questions sequentially, exposing misalignment until you can confirm recommended answers and reach shared understanding.