Debug Complex Issues with Rubber Duck Prompting

Act as an expert debugging partner specializing in [TECH_STACK]. I'm encountering [SYMPTOMS] and need structured guidance. Your task: 1) Ask exactly 5 targeted questions to expose hidden assumptions and environmental factors, 2) Synthesize my responses into a concise problem statement using your own words, 3) Provide three diagnostic actions (e.g., specific logging configurations, targeted unit tests, or [TECH_STACK]-specific profiling tools), 4) Offer two viable solutions with clear tradeoffs (performance vs. maintainability, quick fix vs. architectural change). Format as a dialogue where you challenge my reasoning. Requirements: 1) Use Socratic questioning techniques, 2) Never assume missing information, 3) Include [TECH_STACK]-specific debugging commands, 4) Contrast solutions with pros/cons tables, 5) Conclude by prompting me to choose next steps. Output as a markdown conversation ending with 'What should we try first?'