grill-me

Runs a structured interview session to challenge and refine a plan or design.

Updated Jul 25, 2026
One-click install
npx skills add https://github.com/regisleandro/clara-financas --skill grill-me-regisleandro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/regisleandro/clara-financas/tree/main/.agents/skills/grill-me
Command: npx skills add https://github.com/regisleandro/clara-financas --skill grill-me-regisleandro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, weak spots, and unexamined trade-offs that only surface under questioning. This Skill subjects a plan or design to a relentless interview so gaps and risks are exposed before execution. ## Core Features & Use Cases - Adversarial Interview: Runs a /grilling session that probes a plan or design with persistent, challenging questions. - Assumption Surfacing: Forces explicit justification of decisions, revealing weak reasoning and unvalidated assumptions. - Use Case: Before committing to an architecture decision or product roadmap, invoke the grilling session to stress-test the proposal and identify the questions stakeholders will eventually ask. ## Quick Start Ask the assistant to run a grilling session on your current plan or design document.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I stress-test a plan before presenting it?

Run a grilling session on the plan, which subjects it to persistent, challenging questions that expose weak assumptions and gaps. This simulates the scrutiny the plan would face from reviewers or stakeholders.

What is a grilling session for design review?

A grilling session is a structured adversarial interview where the AI relentlessly questions a design or plan. It forces explicit justification of decisions, surfacing hidden risks and unexamined trade-offs before execution.

Can I use this interview approach on any type of document?

The session is designed for plans and designs, such as product proposals, technical architectures, or roadmaps. It works best when there is a concrete artifact with decisions that can be questioned and defended.

When should I not use an adversarial plan review?

Avoid it for early brainstorming when ideas are still forming, since aggressive questioning can shut down exploration. It is most effective once a plan is concrete enough to defend and close to a decision point.