Skill

grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

npx claudepluginhub dimagi/dimagi-claude-workflows --plugin dev-utils

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Systematically interrogate every aspect of the user's plan or design until all decisions are resolved and documented.

SKILL.md

Similar Skills

grill-me

47.6k

Grills users relentlessly on plans or designs by probing decision tree branches one-by-one with recommendations until shared understanding. Useful for stress-testing ideas or 'grill me' requests.

mattpocock-skills

grill-me

Grills users relentlessly on plans or designs by interviewing branch-by-branch through decision trees to reach shared understanding. Use to stress-test ideas or on 'grill me'.

craft-workspace-webconsulting-skills

grill-me

12.7k

Grills users relentlessly on plans or designs via one-at-a-time questions, resolving decision tree branches with recommendations to reach shared understanding. Use to stress-test ideas or on 'grill me'.

context-mode

Stats

Parent Repo Stars1

Parent Repo Forks3

Last CommitMar 26, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Goal

Systematically interrogate every aspect of the user's plan or design until all decisions are resolved and documented.

Process

Identify the plan. Ask the user to state their plan, or read it from a file/context they provide.
Map the decision tree. Identify all open questions, assumptions, and decision branches.
Walk each branch one question at a time. Ask a single focused question, wait for the answer, then move to the next. Never batch multiple questions.
Answer your own questions when possible. If a question can be resolved by exploring the codebase (reading files, checking existing patterns, grepping for usage), do that instead of asking the user. State what you found and your conclusion.
Track dependencies. If a decision depends on an earlier unresolved one, resolve the dependency first.
Challenge weak answers. If the user's answer is vague, contradictory, or hand-wavy, push back with a specific follow-up.
Maintain a design document. Record every question and its resolution in a design doc. Update it as you go so the user can see the accumulated decisions.

When to stop

Stop when every branch of the decision tree has a concrete resolution and the user confirms the design document reflects the final plan.