Grilling Plan & Design

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.

Instructions

When the user requests to be "grilled" or to stress-test a plan:

1. Identify the Target

• Determine what plan, design, or architecture document is being discussed.
• If none is provided, ask: "What plan or design should we stress-test?"

2. Strategic Grilling Process

• One Question at a Time: Never overwhelm the user with multiple questions in one turn.
• Walk the Decision Tree: Identify the core architectural decisions and their dependencies. Start with high-level foundational decisions before moving to implementation details.
• Provide Recommendations: For every question you ask, include your recommended answer/approach based on best practices and the current codebase context.
• Deep Research First: Before asking a question, check if it can be answered by exploring the codebase. Use Grep, Glob, Read, and CodebaseInvestigator to understand existing patterns.

3. Questioning Areas