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".
Purpose: Stress-test a plan or design by interviewing the user relentlessly. Walk down every branch of the decision tree, resolving dependencies and ensuring a deep, shared understanding before implementation begins.
When the user requests to be "grilled" or to stress-test a plan:
Grep, Glob, Read, and CodebaseInvestigator to understand existing patterns.Focus on these critical areas of the "decision tree":
| Category | Questions to Explore |
|---|---|
| Assumptions | What must be true for this to work? What if it's not? |
| Dependencies | What does this depend on? What depends on this? |
| Edge Cases | How does it handle failures, empty states, or extreme scale? |
| Trade-offs | Why choose this over alternatives? What are we giving up? |
| Extensibility | How easy is it to change or extend this later? |
| Security & Perf | Are there hidden risks or bottlenecks? |
AskUserQuestion.Example:
Question: How should we handle concurrency for the
ContextBuilderupdates?My Recommendation: I recommend using a mutex-protected singleton pattern, as seen in
TeamManager/utils/state.py, to prevent race conditions during parallel processing.
work skill).