grill-me

Stress-test plans by iterating one question at a time through decision branches.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill grill-me-ayehiaa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.agents/skills/grill-me
Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill grill-me-ayehiaa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you uncover unclear assumptions and hidden dependencies in a plan or design by forcing a rigorous, step-by-step examination until you reach shared understanding.

Core Features & Use Cases

  • Relentless decision-tree questioning: Walks through every branch of a design plan to resolve dependencies between choices one-by-one.
  • One-question-at-a-time alignment: Keeps the interaction focused by asking questions sequentially and waiting for your answer.
  • Codebase-aware answers: If a question can be answered by inspecting the repository, it guides you to the relevant parts of the codebase instead of speculating.

Quick Start

Tell the AI: "Grill me on my travel plan design for edge cases, dependencies, and missing assumptions—ask one question at a time until we agree on the full approach."

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 system design for hidden dependencies and unclear assumptions?

To stress-test a system design, you can use iterative question-and-answer sessions that drive through every decision branch until alignment is reached. This approach clarifies ambiguous requirements and resolves dependencies between choices one-by-one.

What is the best way to align on product planning decisions before implementation?

The best way to align on product planning decisions is through relentless decision-tree questioning that walks through every branch sequentially. This forces a rigorous step-by-step examination of choices until shared understanding is achieved.

How do I uncover missing assumptions in a user-experience planning process?

You uncover missing assumptions in user-experience planning by applying sequential single-question prompting to each decision branch. This method keeps the interaction focused and forces a rigorous examination of ambiguous requirements.

Can I use codebase exploration to resolve design review questions instead of speculating?

Yes, you can use codebase exploration to resolve design review questions. If a design question can be answered by inspecting the repository, the stress-testing process guides you to the relevant parts of the codebase rather than speculating.

When do I need assumption testing for ambiguous requirements?

You need assumption testing for ambiguous requirements when dependencies between choices must be resolved before implementation. It is necessary for product, system, or user-experience planning where hidden dependencies could derail the design.