grill-me

Interview users one question at a time to resolve plan and design ambiguities.

2|Updated Feb 12, 2024

Search Tags:#architecture #decision tree #interview #design review #product planning #requirements clarification

Ready to run

npx skills add https://github.com/adibfirman/dotfiles --skill grill-me-adibfirman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/adibfirman/dotfiles/tree/main/claude/.claude/skills/productivity/grill-me
Command: npx skills add https://github.com/adibfirman/dotfiles --skill grill-me-adibfirman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves ambiguity in plans and designs by forcing the user to confront decision dependencies and unanswered questions until both sides agree on the final approach.

Core Features & Use Cases

Relentless interview-by-branches: Iteratively asks one question at a time while walking through the decision tree.
Dependency-aware clarification: Resolves how earlier choices constrain later decisions, step-by-step.
Codebase-first answers: If a question can be answered by examining the repository, it does that instead of guessing.
Recommended answers: For each question, provides a suggested answer that moves the plan forward.
Use Cases: Stress-testing a project plan, reviewing system design tradeoffs, and debugging unclear requirements when someone says “grill me”.

Quick Start

Tell the AI: "Grill me on this plan: [paste your plan/design] and explain what I’m missing until you and I have 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 stress-test a project plan to find missing requirements?▼

To stress-test a project plan, you drive an interview that asks one question at a time to resolve branching decisions and dependencies. This clarifies incomplete requirements and identifies tradeoffs until a shared understanding is reached.

What is the best way to review system design tradeoffs and dependencies?▼

Reviewing system design tradeoffs requires iteratively walking through the decision tree to expose how earlier choices constrain later decisions. This dependency-aware clarification reveals gaps and validates the architecture step-by-step.

Can I clarify ambiguous product planning requirements before implementation?▼

Yes, clarifying ambiguous product planning requirements involves resolving branching decisions through a relentless interview process. It provides recommended answers for each question to move the plan forward and confirms shared understanding.

How does codebase exploration work during a design review?▼

Codebase exploration during a design review examines the repository to answer questions about the plan instead of guessing. This codebase-first approach ensures dependency-aware clarification is grounded in actual architecture constraints.

When should I use a decision tree interview for requirements clarification?▼

You should use a decision tree interview for requirements clarification when tradeoffs are uncertain or requirements are incomplete. It forces you to confront unanswered questions and dependency constraints until both sides agree on the final approach.