grill-me

Sharpens plans and designs through a rigorous interview process.

2|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/IsKenKenYa/skills --skill grill-me-iskenkenya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/IsKenKenYa/skills/tree/main/skills/productivity/grill-me
Command: npx skills add https://github.com/IsKenKenYa/skills --skill grill-me-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions, vague requirements, and unexamined trade-offs. This Skill subjects your plan or design to a relentless interview that exposes weaknesses before implementation begins. ## Core Features & Use Cases - Plan Interrogation: Challenges every assumption in your plan through pointed follow-up questions. - Design Stress-Testing: Probes design decisions for gaps, contradictions, and unhandled edge cases. - Use Case: Before starting a major refactor, invoke this Skill to have your migration plan grilled, surfacing risks like data loss scenarios or rollback gaps you had not considered. ## Quick Start Ask the assistant to grill your current plan or design document to find its weaknesses.

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 implementing it?▼

Invoke the grill-me skill manually to start a structured interview about your plan. The assistant asks probing questions about assumptions, edge cases, and trade-offs to reveal weaknesses before you write code.

What is the grill-me skill used for?▼

It runs a relentless interview that challenges your plan or design. It is a thin entry point that delegates to the underlying grilling skill, which conducts the actual question-and-answer session.

Can the grill-me skill trigger automatically?▼

No. The skill sets disable-model-invocation to true, so it only runs when you explicitly invoke it. This prevents unwanted interrogation during normal coding sessions.

When should I not use an interview-based plan review?▼

Avoid it for trivial changes or well-understood tasks where questioning adds no value. It is most useful for complex, ambiguous, or high-stakes plans where hidden assumptions carry real risk.