grill-me

Interrogates plans and designs through one-question-at-a-time stress-test interviews.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/JoyJoin-Tech-Limited/JoyJoin_app_v0.1 --skill grill-me-joyjoin-tech-limited
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/JoyJoin-Tech-Limited/JoyJoin_app_v0.1/tree/main/.github/skills/grill-me
Command: npx skills add https://github.com/JoyJoin-Tech-Limited/JoyJoin_app_v0.1 --skill grill-me-joyjoin-tech-limited

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often contain hidden assumptions and unresolved decision branches that only surface during implementation. This Skill stress-tests a plan by relentlessly interviewing the user one question at a time, walking every branch of the decision tree until shared understanding is reached. ## Core Features & Use Cases - Structured Interrogation: Asks exactly one question per response, always paired with a recommended answer to keep momentum. - Codebase-Grounded Questions: Explores the codebase to answer questions itself instead of asking when the answer already exists in the code. - Use Case: Before implementing a new API contract, ask the Skill to grill the design. It will walk through ownership, idempotency, state machines, and UX flows one decision at a time until every branch is resolved. ## Quick Start Ask the assistant to grill your plan by saying "grill me on this design" and paste or describe the plan you want stress-tested.

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 implementation?▼

Present your plan and ask to be grilled on it. The Skill interviews you one question at a time, providing a recommended answer with each question, and walks every branch of the decision tree until all assumptions are resolved.

How to review an API design for hidden assumptions?▼

Use a structured interrogation approach that asks targeted questions like who owns the write path, server or client, with recommended answers such as server-side writes with idempotency keys. Each decision branch is resolved one at a time.

When should I not use a plan interrogation approach?▼

Avoid it when no plan exists yet and scope is still ambiguous, when you want open-ended brainstorming, or when you need full kickoff discovery. Use brainstorming or research workflows first, then grill the resulting plan.

What happens if I give vague one-word answers during the interview?▼

The Skill expands the question with concrete options. For example, "server or client?" becomes "server-generated with client cache, or client-driven with server validation?" to force a specific decision.

Does the interview use my codebase to answer questions?▼

Yes. When a question can be answered by exploring the codebase, the Skill investigates the code itself instead of asking you, reducing unnecessary back-and-forth during the review.