grill-me

Interview a user's plan with one question per turn and recommendations.

Updated May 25, 2026
One-click install
npx skills add https://github.com/AcendWay/ai-skills-library --skill grill-me-acendway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/AcendWay/ai-skills-library/tree/main/skill-folders/grill-me
Command: npx skills add https://github.com/AcendWay/ai-skills-library --skill grill-me-acendway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grilling the user’s plan exposes hidden assumptions, unclear dependencies, and missing decision criteria so you can reach shared understanding before execution.

Core Features & Use Cases

  • Relentless, branch-by-branch design review: Walk through each decision point in the plan and resolve dependencies between decisions one by one.
  • Single-question-per-turn clarification: Ask one targeted question each turn to avoid skipping the hard parts and to keep progress grounded in specifics.
  • Recommendation with rationale: For every question, provide the recommended answer plus a one-sentence reason to move the plan toward a concrete, agreed direction.
  • Codebase/docs-first guidance: If a question can be answered by checking available codebase or documentation, use that instead of guessing.

Quick Start

Tell the AI: “Grill me on my project plan; challenge every assumption and resolve the dependencies until we have shared understanding.”

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I stress-test a project plan before execution?

To stress-test a project plan, you conduct a relentless, branch-by-branch interview that exposes hidden assumptions and unclear dependencies. This process walks through each decision point to reach shared understanding before execution begins.

What is the best way to validate assumptions in a design review?

Validating assumptions in a design review requires asking one targeted question per turn to avoid skipping hard parts. You provide a recommendation with a one-sentence reason to move the plan toward a concrete direction.

How do I resolve dependencies in my decision tree?

You resolve dependencies in a decision tree by walking through each decision point individually and addressing them one by one. This branch-by-branch walkthrough ensures no dependency is skipped during planning.

Can I use available codebase documentation to answer planning questions?

Yes, you can and should use available codebase or documentation to answer determinable planning questions. Checking existing docs first prevents guessing and keeps progress grounded in specifics.

When do I need assumption checking for my requirements?

You need assumption checking for requirements when you have a rough plan that lacks concrete, agreed directions. It exposes missing decision criteria so you can reach shared understanding before moving forward.