requirements-grill

Guide structured questions to elicit unresolved requirements and record decisions.

15|5|Updated May 17, 2026

Search Tags:#planning #requirements #ownership #scope #decision-making #stakeholders #grill

Ready to run

npx skills add https://github.com/cropsgg/skills --skill requirements-grill-cropsgg

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface hidden assumptions and ambiguities in requirements by guiding a structured interrogation that surfaces acceptance criteria, scope, and ownership before design or implementation.

Core Features & Use Cases

Structured interrogation to surface decisions and reduce ambiguity.
Batch questions in 3–5 questions per turn to keep sessions focused.
Decision recording with owner assignment and rationale.
Exit criteria: all critical paths have owners or are clearly parked with ownership.

Quick Start

Restate the goal and begin by asking 3–5 focused questions per turn to surface tradeoffs and ownership.

Frequently Asked Questions about requirements-grill

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

FAQPage Schema

How do I surface hidden assumptions and ambiguities in requirements before development?▼

To surface hidden assumptions in requirements, use structured interrogation to guide focused questions that elicit acceptance criteria, scope, and ownership. This systematic approach reduces ambiguity by exposing unresolved tradeoffs and decision gaps before design or implementation begins.

Can I use structured questioning to assign owners and record decisions during planning sessions?▼

Yes, you can use structured questioning to assign owners and record decisions during planning sessions. The process captures decision rationale alongside owner assignment, ensuring every critical path has clear ownership or is explicitly parked with a designated owner.

What is the best way to elicit unresolved scope and edge cases during early ideation?▼

The best way to elicit unresolved scope and edge cases is by applying batch questions of 3 to 5 items per turn. This keeps early ideation sessions focused while systematically extracting acceptance criteria and edge cases that would otherwise remain hidden.

How do I know when requirements grilling is complete and ready for design?▼

Requirements grilling is complete when defined exit criteria are met: all critical paths have owners or are clearly parked with ownership. This ensures decisions have assigned owners and clear next steps before transitioning to design or implementation.

Does structured requirements interrogation work for early scoping sessions?▼

Yes, structured requirements interrogation works for early scoping sessions. It applies directly to ideation and early planning where acceptance criteria, edge cases, or ownership are unclear, systematically guiding questions to reduce ambiguity before design.