grilling

Interrogate project plans and design architectures through iterative questioning.

45|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/hachej/boring-ui --skill grilling-hachej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grilling
Source: https://github.com/hachej/boring-ui/tree/main/.agents/skill-library/mattpocock/grilling
Command: npx skills add https://github.com/hachej/boring-ui --skill grilling-hachej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the common pitfall of proceeding with incomplete or poorly vetted plans by forcing a rigorous, systematic review of every design decision.

Core Features & Use Cases

  • Systematic Interrogation: Breaks down complex plans into individual components to ensure no dependency or edge case is overlooked.
  • Fact-Based Verification: Automatically cross-references the codebase to verify existing facts, allowing the user to focus on high-level strategic decisions.
  • Use Case: Use this before starting a major refactor or architectural change to ensure you have considered all potential failure points and design trade-offs.

Quick Start

Initiate the grilling skill to review the current project plan and identify any missing dependencies or design flaws.

Frequently Asked Questions about grilling

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

FAQPage Schema
How do I validate my software architecture design before starting a refactor?

Validate software architecture design by applying systematic interrogation to break down complex plans, cross-referencing the codebase to verify facts, and reviewing design decisions iteratively to identify missing dependencies and failure points.

What is the best way to stress-test project plans for missing dependencies?

Stress-test project plans by executing a rigorous, one-by-one questioning process that evaluates every design decision against codebase context, ensuring no dependency, edge case, or design trade-off is overlooked before implementation.

How does fact-based verification work when evaluating technical decisions?

Fact-based verification works by automatically parsing codebase context to distinguish between verifiable facts and subjective design choices, allowing you to focus on high-level strategic planning while systematically confirming existing technical constraints.

Can I use iterative questioning to review architectural changes in my codebase?

You can use iterative questioning to review architectural changes by facilitating critical evaluation through one-by-one inquiries, systematically breaking down complex components to ensure thorough validation of all technical decisions and potential failure points.

When do I need systematic interrogation for software development planning?

You need systematic interrogation for software development planning when proceeding with major refactors or architectural changes, ensuring rigorous review of design architectures to avoid the common pitfall of proceeding with incomplete or poorly vetted plans.