rubber-duck

Guide developers through Socratic questioning to surface hidden assumptions.

3|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/dpaola2/rubber-duck --skill rubber-duck-dpaola2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rubber-duck
Source: https://github.com/dpaola2/rubber-duck/tree/main
Command: npx skills add https://github.com/dpaola2/rubber-duck --skill rubber-duck-dpaola2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers uncover bugs by guiding them through a structured Socratic questioning process, instead of providing fixes or diagnoses.

Core Features & Use Cases

  • Guided five-phase debugging flow (Symptom, Environment, Workflow, Assumptions, Breakthrough) to surface root causes.
  • Works in Claude Code sessions, adapting to code, deployment, or data problems.
  • Use case: you get stuck on a bug or failing workflow, and the skill helps you articulate the problem clearly.

Quick Start

Describe the problem and start the five-phase questioning flow in your Claude Code session.

Frequently Asked Questions about rubber-duck

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does Socratic questioning help with debugging in Claude Code?

Socratic debugging helps uncover bugs by guiding developers through a structured five-phase questioning process to surface root causes, rather than providing direct fixes or diagnoses. It enforces a strict one-question-at-a-time rhythm to clarify symptoms and hidden assumptions.

What's the best way to find a root cause when my deployment symptoms are unclear?

The best way to find a root cause for unclear deployment symptoms is using an interactive Socratic debugging flow. It guides you through Symptom, Environment, Workflow, Assumptions, and Breakthrough phases to help you articulate the problem and discover the root cause yourself.

Can I use Socratic debugging for data issues or is it only for software bugs?

You can use Socratic debugging for data issues. The interactive questioning process adapts to software bugs, deployments, data issues, or any situation where symptoms are unclear and hidden assumptions must be surfaced to find the root cause.

How do I start a Socratic debugging session to surface hidden assumptions?

To start a Socratic debugging session, describe the problem in your Claude Code session. The interactive flow begins asking targeted questions one at a time, progressing through phases to surface hidden assumptions and guide you to a breakthrough.

Does this debugging approach provide fixes and hints when I get stuck?

This debugging approach does not provide fixes or hints. It strictly avoids giving diagnoses, instead asking targeted Socratic questions one at a time to enforce a structured process where you uncover the root cause yourself.