grill-me

Resolve ambiguous plans through iterative, dependency-aware questioning.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/Soham407/studio-kickstart --skill grill-me-soham407
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/Soham407/studio-kickstart/tree/main/architecture/matt-pocock-grill-me
Command: npx skills add https://github.com/Soham407/studio-kickstart --skill grill-me-soham407

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns vague or uncertain plans into a shared, well-reasoned design by forcing explicit decisions and resolving contradictions through iterative questioning.

Core Features & Use Cases

  • Relentless plan interrogation: Works through every branch of a decision tree until the plan has no unresolved dependencies.
  • Dependency-aware clarification: Resolves one-by-one how earlier choices constrain later decisions to avoid hidden gaps.
  • Shared understanding outcome: Produces recommended answers that align stakeholders on what to do next and why.

Quick Start

Tell the AI to “Grill me on my plan for [project]—ask one question at a time and resolve every dependency until you and I have a 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 resolve ambiguous requirements and align stakeholders on a project plan?

To resolve ambiguous requirements, you can use an iterative, dependency-aware questioning sequence that forces explicit decisions and resolves contradictions to achieve stakeholder alignment.

What is dependency-aware clarification for product decision trees?

Dependency-aware clarification is a process that resolves decision trees one question at a time, ensuring earlier choices constrain later decisions to eliminate hidden gaps in architecture reviews.

How do I stress-test an architecture plan to find unresolved dependencies?

You stress-test an architecture plan by conducting an iterative interrogation of every branch in the decision tree until the plan has no unresolved dependencies and provides recommended answers.

Does this approach work for validating design decisions and branching choices?

Yes, this approach applies to product, architecture, and design decision trees where choices branch and require explicit justification to drive consensus among stakeholders.

What is the best way to document recommended answers from a plan validation session?

The best way to document recommended answers is to resolve each decision explicitly through questioning, producing a shared, well-reasoned design outcome that aligns stakeholders on what to do next.

Can I use iterative interviewing to resolve contradictions in a vague technical plan?

Yes, you can use iterative interviewing to resolve contradictions in a vague technical plan by asking one question at a time, exploring the codebase when possible, and providing recommended answers for each resolved decision.