skills/grill-me/SKILL.md
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 skillsauth add bjornmelin/dev-skills grill-meInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one and applying your deep reasoning and domain expertise. For each question, provide your recommended answer and include custom weighted decision framework scores from 0.0 to 10.0 for all viable options, and target 9.0+ decisions when realistically achievable.
Ask questions one at a time using functions.request_user_input. Put the recommended option first, and keep options mutually exclusive. Batch multiple non-dependent questions into a single functions.request_user_input whenever safe.
If a question can be answered by exploring the codebase, explore the codebase instead.
If a question can be answered by researching the web, GitHub, or package source code, use web search tools, context7, gh cli/api, or opensrc skills.
For pre-mortem plan-challenge work, run the /pre-mortem skill.
development
Pre-PR multi-model review, parallel opus and codex exec adversarial lanes, then adversarial verification of merged findings. Read-only. Use before shipping nontrivial diffs.
tools
Independent gpt-5.6 diff review via the Codex CLI, normal or steerable adversarial with JSON findings. Use before shipping nontrivial changes.
development
Delegate implementation, investigation, or bulk work to gpt-5.6 codex via pinned codex exec. Use for clear-spec builds, migrations, debugging, or any task MODELS.md routes to codex.
development
Adversarial pre-mortem: imagine the plan failed, work backwards to surface risky assumptions + irreversible bets, then harden them. Proactively offer it (after the current request; confirm first) before a hard-to-reverse or one-way-door call (API, schema, framework, a hire), an all-upside plan, or unvalidated assumptions. Also on request.