grill-me

Enumerates risks and ambiguities in plans, designs, or discovery documents.

12|2|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/alexandrbasis/claudops --skill grill-me-alexandrbasis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/alexandrbasis/claudops/tree/main/.claude/skills/grill-me
Command: npx skills add https://github.com/alexandrbasis/claudops --skill grill-me-alexandrbasis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pressure-tests a plan, design, or discovery document to surface hidden assumptions, scope gaps, and ambiguous wording, making risks explicit.

Core Features & Use Cases

  • Enumerate candidate risks across scope, flows, assumptions, wording, and decision branches.
  • Surface focused questions in a prioritized order with recommended answers or defaults.
  • Return a concise summary of clarifications, scope cuts, hidden assumptions, and remaining risks.

Quick Start

Upload your discovery document and I will grill it to surface risks, ambiguities, and missing branches.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I identify hidden assumptions and scope gaps in a discovery document?

A risk analysis of your plan enumerates candidate risks across scope, flows, and decision branches to surface ambiguities, hidden assumptions, and wording gaps affecting delivery.

What is the best way to stress-test a project plan for ambiguities and constraints?

Stress-testing a plan involves applying risk analysis to discovery documents to prioritize open questions, expose missing branches, and ensure explicit assumptions and actionable next steps are captured.

How do I prioritize open questions and clarify scope before starting delivery?

You prioritize open questions and clarify scope by evaluating ambiguities in planning documents, returning concise summaries of required clarifications, scope cuts, and remaining delivery risks.

Can I use risk analysis to surface missing decision branches in a design document?

Yes, applying risk analysis to a design document enumerates candidate risks across flows and constraints, highlighting top-priority ambiguities that affect scope and delivery.

What limitations exist when pressure-testing stakeholder assumptions in a plan?

Pressure-testing assumptions relies entirely on the provided discovery or design document, meaning unstated constraints or undocumented flows outside the text cannot be evaluated for risks.