devenv-rubber-duck

To clarify fuzzy ideas, you can use a conversational thinking partner that listens to your reasoning and asks probing questions to expose hidden assumptions. This helps you articulate complex problems and identify a clear path forward.

Surfacing assumptions during debugging involves paraphrasing your logic back to you and asking open-ended questions. This reflective listening technique highlights unverified constraints and gaps in your understanding.

Socratic questioning for architectural trade-offs works by actively engaging with a conversational partner that challenges your reasoning. It requires you to vocalize your thought process so the partner can reflect it back and identify design flaws.

This thinking partner does not generate code or artifacts. It operates strictly as a reflective interface within software development workflows to facilitate reflection and clarify design trade-offs.

Yes, you can use this for implementation planning. Once the Socratic questioning helps you surface assumptions and reach clarity, it identifies appropriate follow-up actions like moving into implementation planning or experimentation.

You should avoid this rubber duck debugging approach if your problem requires immediate code generation or artifact creation, as it strictly functions as a reflective tool for articulating problems and validating reasoning.