grill

Interrogate project ideas with exhaustive questioning to uncover assumptions and blind spots.

1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/iancleary/dotfiles --skill grill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill
Source: https://github.com/iancleary/dotfiles/tree/main/.agents/skills/grill
Command: npx skills add https://github.com/iancleary/dotfiles --skill grill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of incomplete or poorly defined project ideas by ensuring all details, assumptions, and potential blind spots are thoroughly explored before any planning or implementation begins.

Core Features & Use Cases

  • Deep Questioning: Asks a comprehensive series of questions to uncover hidden assumptions and constraints.
  • Assumption Challenging: Ruthlessly questions vague language and pushes back on unstated requirements.
  • Use Case: Before starting a new software feature, use this Skill to ensure you've considered all edge cases, user needs, and technical limitations, preventing costly rework later.

Quick Start

Use the grill skill to help me build a new feature.

Frequently Asked Questions about grill

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

FAQPage Schema
How do I validate project assumptions and uncover blind spots before planning?

Assumption validation requires a rigorous interrogation process to challenge vague language and extract granular details. By demanding exhaustive questioning before planning, you uncover hidden constraints and ensure all unstated requirements are defined.

What is requirements gathering for product ideation and when do I need it?

Requirements gathering for product ideation is a deep dive process to thoroughly explore new project details. You need it before starting a new software feature to consider edge cases, user needs, and technical limitations, preventing costly rework later.

How do I conduct a deep dive to challenge vague language in new project ideas?

Conducting a deep dive involves asking a comprehensive series of questions to ruthlessly question unstated requirements. This structured interrogation pushes back on incomplete ideas and forces extraction of granular information to fully define the project scope.

Can I use strategic planning to prevent costly rework on new software features?

Strategic planning prevents costly rework by ensuring all details, assumptions, and potential blind spots are thoroughly explored before implementation begins. This exhaustive questioning phase guarantees technical limitations and user needs are identified upfront.

What is the best way to perform risk assessment for undefined project ideas?

The best way to perform risk assessment on undefined ideas is a relentless interrogation that uncovers all details and blind spots. This process challenges assumptions and demands exhaustive questioning before proposing a structured plan.

Why does my requirements gathering process miss hidden constraints and edge cases?

Your requirements gathering misses hidden constraints when it lacks relentless questioning of vague language and unstated assumptions. A rigorous interrogation process is required to uncover all details, edge cases, and technical limitations before planning begins.