Interrogate decision branches to clarify and validate plans or designs.
npx skills add https://github.com/tabesink/deepdoc-agent --skill grill-me-tabesink
Please help me install this Agent Skill. Skill: grill-me Source: https://github.com/tabesink/deepdoc-agent/tree/main/.cursor/skills/grill-me Command: npx skills add https://github.com/tabesink/deepdoc-agent --skill grill-me-tabesink
It removes ambiguity from plans and designs by forcing explicit decisions, surfacing hidden assumptions, and reconciling conflicting branches until both you and the system share the same understanding.
Ask the AI to grill you on your plan and explicitly resolve each open decision branch, e.g., "Grill me on my system design for recursive RAG retrieval and synthesis with citations, and keep drilling until we agree on every dependency and assumption."
High-intent search queries and answers about installing and using this skill.
Design interrogation works by breaking a plan into a decision tree and asking targeted questions for each branch. This relentless questioning forces explicit decisions and surfaces hidden assumptions during architecture planning.
Dependency-driven clarification resolves dependencies between decisions one-by-one to prevent downstream surprises. It applies stepwise question traversal and branch reconciliation to ensure every interrelated choice is explicitly validated.
Yes, code-first verification switches to exploring the codebase rather than guessing. If a design review question can be answered by reading the repository, the system explores the code directly to verify the assumption.
Yes, requirements clarification works for recursive architecture planning by applying relentless design interrogation. It drills into every dependency and assumption until both you and the system explicitly agree on every open decision branch.
Avoid using a decision tree for assumption testing when your plan lacks explicit decision branches or interrelated choices. The stepwise question traversal requires a structured plan to break down and reconcile conflicting branches effectively.
Liz2ZInterrogate plans and designs to uncover decisions and dependencies.
adolfoaranaes12Create interactive checklists with decision trees and progress tracking.
SeemSeamAdd and run tests for affected code behaviors to prevent regressions.
maxenergyInterview plans or designs to reveal hidden assumptions and dependencies.
