grill-me

Interrogate plans across five dimensions and generate an Ambiguity Report with a gate verdict.

8|1|Updated Apr 10, 2026

Search Tags:#ambiguity #interview #spec #scoring #gate #grill

Ready to run

npx skills add https://github.com/max4c/skills --skill grill-me-max4c

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/max4c/skills/tree/main/skills/grill-me
Command: npx skills add https://github.com/max4c/skills --skill grill-me-max4c

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interview relentlessly about a plan, spec, or ticket until every branch of the decision tree is resolved, yielding a per-dimension ambiguity report and an aggregate gate to guide handoffs and execution.

Core Features & Use Cases

Active interrogation across Goals, Acceptance, Boundaries, Alternatives, and Assumptions to surface hidden dependencies and risks.
Reusable subroutine for other skills (e.g., max:write-prd, max:tech-spec, max:improve-codebase, bugbook flows) to ensure shared understanding.
Generates an Ambiguity Report with a final gate assessment to determine whether work can proceed or needs revision.

Quick Start

Start an interactive grilling session against the current artifact to surface ambiguity and determine a gate.

Frequently Asked Questions about grill-me

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

FAQPage Schema

How do I find ambiguities in a project spec before implementation?▼

To find ambiguities in a project spec, you interrogate the plan across Goals, Acceptance, Boundaries, Alternatives, and Assumptions. This exposes decision-tree gaps that could block implementation and generates a per-dimension ambiguity report.

What is a gate verdict in spec analysis and when do I need it?▼

A gate verdict in spec analysis determines whether a plan can proceed to handoff or needs revision based on an ambiguity assessment. You need it when evaluating if a technical spec has resolved all decision branches to ensure shared understanding.

How do I surface hidden risks and dependencies in a product plan?▼

You surface hidden risks and dependencies in a product plan by applying an active interrogation process to uncover unresolved branches in the decision tree. This yields a scored ambiguity report highlighting areas that require further definition.

Can I use an interrogation routine to check if a ticket is ready for handoff?▼

Yes, you can use an interrogation routine to check if a ticket is ready for handoff. It applies an active questioning process across five dimensions, producing an aggregate gate assessment to determine if the spec is clear enough to execute.

What are the limitations of using ambiguity reports for technical specs?▼

The limitation of using ambiguity reports for technical specs is that they only surface gaps across Goals, Acceptance, Boundaries, Alternatives, and Assumptions. They do not automatically resolve the missing branches, requiring manual revision before implementation can proceed.