Interrogate plans one question at a time to surface assumptions and dependencies.
npx skills add https://github.com/darkmatter/skills --skill grill-me-darkmatter
Please help me install this Agent Skill. Skill: grill-me Source: https://github.com/darkmatter/skills/tree/main/skills/grill-me Command: npx skills add https://github.com/darkmatter/skills --skill grill-me-darkmatter
This Skill helps you pressure-test a plan or design by systematically uncovering assumptions, missing details, and unresolved branches before you commit to implementation.
Ask the grill-me skill to challenge your plan or design and guide the discussion one question at a time until the approach is fully understood.
High-intent search queries and answers about installing and using this skill.
A design review identifies missing assumptions and unresolved dependencies in a proposed workflow. It systematically interrogates your plan to expose weak decisions, ensuring your approach is fully understood before you commit to implementation.
Finding missing assumptions requires codebase-aware clarification that checks existing project files instead of relying on user speculation. This resolves dependent choices branch-by-branch, surfacing unresolved dependencies through systematic interrogation.
Yes, a branch-by-branch decision tree supports implementation planning by resolving each fork in the design tree one question at a time. This structured interrogation keeps complex dependent choices manageable and fully resolved.
Design review works without manual file inspection by applying codebase-aware clarification. It checks existing project files directly to answer questions from context, eliminating the need for manual inspection or user speculation.
The best way to challenge a proposed workflow is through structured interrogation that applies rigorous pressure-testing one question at a time. This verifies the approach against the codebase and resolves each fork in the decision tree before implementation.
Avoid a one-question-at-a-time approach when your design lacks complex dependent choices or branch-by-branch forks. It is designed for rigorous interrogation of intricate plans, so simple designs without decision trees may not require this structured exploration.
tomholfordInterrogate plan assumptions to reveal hidden risks and dependencies.
tonehqIdentify decision branches and map dependencies in a plan.
lasswelltAnalyze a codebase across technology, architecture, quality, and concerns to generate CODEBASE-MAP.md.
babuallyInterrogate plans and designs to expose missing assumptions and weak decision points.
