grill-me

Interrogate task requirements to align human intent with implementation.

15|5|Updated May 17, 2026
One-click install
npx skills add https://github.com/cropsgg/skills --skill grill-me-cropsgg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/cropsgg/skills/tree/main/skills/planning/grill-me
Command: npx skills add https://github.com/cropsgg/skills --skill grill-me-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Relentless interrogation session to ensure alignment between human intent and agent output by forcing explicit trade-offs, scope boundaries, and failure-mode analysis before any code is written.

Core Features & Use Cases

  • Adversarial questioning to surface hidden assumptions and disagreements.
  • Forced definition of scope, success criteria, and risk mitigation before implementation.
  • Use Case: When a user provides vague or ambitious requirements, apply grill-me to lock down concrete details and guardrails.

Quick Start

Ask the user to describe the task in detail and surface explicit trade-offs, scope boundaries, and failure modes before any implementation begins.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I disambiguate vague software requirements before implementation?

Surface hidden assumptions and disagreements in ambiguous plans through adversarial questioning that forces explicit scope boundaries and trade-offs before coding begins. This interrogation protocol locks down concrete details and guardrails.

What is requirements disambiguation for multi-file subsystems?

Requirements disambiguation for multi-file subsystems is a structured interrogation protocol that elicits scope, success criteria, trade-offs, and failure modes to force explicit alignment between human intent and agent output.

When should I use adversarial questioning for scope definition?

Use adversarial questioning for scope definition when users provide vague or ambitious requirements touching multiple files or subsystems. It forces explicit trade-offs, scope boundaries, and failure-mode analysis before implementation begins.

Can I force explicit trade-offs and failure-mode analysis before coding?

Yes, you can force explicit trade-offs and failure-mode analysis by applying a rigorous interrogation protocol that requires defining scope, success criteria, and risk mitigation before any implementation begins.

What's the best way to align human intent with agent output on ambitious tasks?

Align human intent with agent output through relentless interrogation that forces explicit scope boundaries, trade-offs, and failure-mode analysis. This locks down concrete details and guardrails before any implementation begins.