grilling

Systematically question design assumptions and dependencies in architectural plans.

63|9|Updated Jun 15, 2025

Search Tags:#design #planning #architecture #review #logic #stress-test

Ready to run

npx skills add https://github.com/willdady/platypus --skill grilling-willdady

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grilling
Source: https://github.com/willdady/platypus/tree/main/.agents/skills/grilling
Command: npx skills add https://github.com/willdady/platypus --skill grilling-willdady

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common pitfall of building plans based on unexamined assumptions or incomplete logic by forcing a rigorous, step-by-step review of your design.

Core Features & Use Cases

Systematic Interrogation: Breaks down complex plans into individual branches of the design tree to ensure every dependency is resolved.
Fact-Based Verification: Automatically prioritizes codebase exploration for factual data, reserving human input for critical decision-making.
Use Case: Use this before starting a major refactor or architectural change to ensure you have considered all edge cases and potential failure points.

Quick Start

Activate the grilling skill and ask it to review the current project architecture plan.

Frequently Asked Questions about grilling

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

FAQPage Schema

How do I stress-test an architecture plan before implementation?▼

To stress-test an architecture plan, you can use this skill to systematically question design assumptions and dependencies, resolving every branch of the design tree before coding begins.

Why does my project refactor plan have unexamined assumptions?▼

Project plans often contain unexamined assumptions due to incomplete logic, which requires a rigorous step-by-step review to break down complex plans and validate edge cases.

How do I review system design dependencies systematically?▼

Reviewing system design dependencies systematically requires breaking down complex plans into individual branches of the design tree to ensure every dependency is resolved through iterative feedback loops.

Can I use this for project management workflows or is it limited to software architecture?▼

You can use this for project management workflows as well as software development and system design, applying structured feedback loops to validate complex logic wherever shared understanding is required.

Does this planning review require human input for all decisions?▼

No, the planning review prioritizes codebase exploration for factual data automatically, reserving human input only for critical decision-making during the architectural validation process.

When should I not use a systematic interrogation approach for design review?▼

You should avoid systematic interrogation for design review when you do not need to validate complex logic or ensure shared understanding, as it enforces structured iterative feedback loops that may be unnecessary for simple tasks.