grill-me

Interrogate plans and design choices until shared understanding is reached.

Updated Aug 23, 2026

Search Tags:#architecture #interview #software #design-review #decision-tree #grill

Ready to run

npx skills add https://github.com/Dedalus-ERP-PAS/hexagone-foundation-skills --skill grill-me-dedalus-erp-pas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/Dedalus-ERP-PAS/hexagone-foundation-skills/tree/main/skills/grill-me
Command: npx skills add https://github.com/Dedalus-ERP-PAS/hexagone-foundation-skills --skill grill-me-dedalus-erp-pas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams reach clear, shared understanding of complex plans by relentlessly questioning assumptions, decisions, and trade-offs until gaps are resolved.

Core Features & Use Cases

Structured interrogation: guides users through planned architectures and workflows, recursively exploring each design branch.
Dependency and risk awareness: surfaces hidden dependencies, conflicts, and uncertainties across decisions.
Iterative alignment: aligns stakeholders by recording decisions and clarifying priorities so teams can move forward confidently.

Quick Start

Explain your plan and I will grill you until we converge on a shared understanding.

Frequently Asked Questions about grill-me

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

FAQPage Schema

How do I interrogate a software architecture plan to find design flaws?▼

To interrogate software architecture plans, use structured questioning to recursively explore design branches, surface hidden dependencies, and resolve trade-off gaps until stakeholders reach a shared understanding.

What is structured interrogation in a design review?▼

Structured interrogation in a design review is a deterministic questioning process that recursively explores planned architectures and workflows, seeking to clarify user intent, priorities, and technical constraints.

Can I use this for strategy sessions and architecture planning?▼

Yes, you can use this for strategy sessions and architecture planning. It applies rigorous critique to decisions, records priorities, and aligns stakeholders so teams can move forward confidently.

How do I surface hidden dependencies and risks in a software design?▼

Surface hidden dependencies and risks by applying deterministic questioning to your plan. This process explores the codebase when possible and recursively checks each design branch for conflicts and uncertainties.

What is the best way to align stakeholders on complex software decisions?▼

The best way to align stakeholders on complex software decisions is through iterative interrogation that relentlessly questions assumptions, records decisions, and clarifies priorities until a shared understanding is reached.

When should I not use a deterministic questioning approach for plans?▼

Avoid using a deterministic questioning approach when a plan is already finalized, requires no stakeholder alignment, or when rapid prototyping is prioritized over rigorous critique and resolving trade-off gaps.