rubber-duck

Narrating reasoning exposes assumptions, tradeoffs, and uncertainties in real time, reducing guesswork and catching errors early during debugging. Structured, transparent thinking improves accuracy and auditability for complex coding and planning tasks.

The best way to make decision-making transparent is enabling Rubber Duck mode to articulate every decision, assumption, and rationale before acting. This real-time narration increases traceability and error detection during complex tasks.

To start narrating decisions for code reviews, enable Rubber Duck mode and adhere to the narration protocol by explicitly stating every assumption and rationale before taking action. This exposes tradeoffs and reduces mistakes.

Yes, you can use narrated reasoning for architectural planning without external tooling. The built-in Rubber Duck mode requires no dependencies, allowing you to structure thinking and expose discoveries during strategy sessions.

Transparent reasoning narration might not suit highly routine or trivial coding tasks where exhaustive explanation of assumptions creates unnecessary friction, as its primary value lies in catching errors during complex debugging and design reviews.

The rubber-duck approach helps with strategic planning and design reviews by forcing real-time articulation of rationale and uncertainties, which reduces errors and ensures the decision-making process is fully auditable.