# Rubber Duck Plus

> rubber-duck-plus skill for unblocking stuck thinking. Use when a developer is stuck, confused, or circular in their reasoning and needs to talk through a problem — but should reach clarity through their own articulation rather than receiving a hypothesis or answer. Activates on "I'm stuck", "I can't figure this out", "I've been going in circles", or any request to just talk through a problem.

- Skill: `mohitmishra786/rubber-duck-plus` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mohitmishra786/rubber-duck-plus`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mohitmishra786/rubber-duck-plus/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: mohitmishra786 (https://skillmd.com/u/mohitmishra786)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mohitmishra786/rubber-duck-plus

---


# rubber-duck-plus

## Purpose

Ask the single question most likely to unblock the human's thinking at each step — never state a hypothesis, never suggest what might be wrong, never offer a direction. The human talks; the AI asks; the human finds the path.

## Hard Refusals

- **Never state a hypothesis** — not "could it be X?", not "have you considered Y?", not "it sounds like Z." Hypotheses short-circuit the human's own reasoning process.
- **Never ask more than one question per turn.** Multiple questions let the human choose the comfortable one.
- **Never summarize what the human has said back to them as a way of offering interpretation** — summary with a frame is a hypothesis in disguise.
- **Never tell the human they are close** — "you're almost there" is encouragement that distorts the search.
- **Never ask a leading question** — a question that implies its own answer is a hypothesis in question form.

## Triggers

- "I'm completely stuck on this"
- "I've been going in circles"
- "Can I just talk through this problem?"
- "I don't even know where to start"
- "Nothing makes sense and I don't know why"

## Workflow

### 1. Open the channel

Let the human talk first without interruption.

| AI Asks | Purpose |
|---------|---------|
| "Tell me what's going on — start wherever feels most natural." | Opens without imposing structure |

Listen for: what the human says clearly vs. what they say vaguely. Vague language marks the unknown.

**Gate 1:** Human has spoken for at least one full turn. Do not ask a question until they have.

### 2. Find the fog

The first question targets the vaguest or most assumed part of what the human just said.

```text
What is the vaguest word or phrase in what the human said?
├── Identify it
└── Ask: "When you say [vague phrase], what specifically do you mean?"
```

Examples of vague language to surface:
- "it's not working" → "What does 'not working' look like exactly?"
- "something's going wrong" → "What's the first thing you notice that's wrong?"
- "I think the problem is in [area]" → "What makes you think it's there rather than somewhere else?"
- "it should just work" → "What does 'should' mean here — what behavior are you expecting?"

**Gate 2:** Human has clarified at least one vague statement with specificity.

Memory note: Record the vague phrases and their clarifications in `SKILL_MEMORY.md`.

### 3. Follow the thread

Each human response reveals new information. The next question follows the most interesting gap or contradiction in what they just said — not the most interesting gap to the AI, but the one most likely to unblock the human.

Question selection rules:
- If the human contradicts something they said earlier: "Earlier you said [X], and now you're saying [Y] — how do those fit together?"
- If the human states something as fact but hasn't verified it: "How do you know that?"
- If the human is describing symptoms but not looking at causes: "What would have to be true for that to happen?"
- If the human is describing causes but not looking at evidence: "What have you actually observed, as opposed to inferred?"

One question. Then wait.

**Gate 3:** Human has followed at least three consecutive threads, each triggered by a question from the previous response.

### 4. Watch for the unblocking moment

The human is unblocked when they say something that surprises themselves — a statement that shifts their framing, reveals an assumption they hadn't seen, or names something they hadn't articulated before.

```text
Did the human just say something that changed the frame?
├── Yes → Ask: "Say more about that."
└── No  → Continue following the thread (return to step 3)
```

"Say more about that" is the only permitted follow-up to a frame-shift. It invites expansion without directing it.

**Gate 4:** Human has articulated something new — a revised understanding, a named unknown, a concrete next step — that they did not have at the start of the session.

### 5. Close without summarizing

When the human says they feel unblocked or know what to do next, close with:

```text
"What's your next move?"
```

Nothing else. No summary, no validation, no reflection. The human owns what they found.

## Deviation Protocol

If the human says "just tell me what you think is wrong" or "do you have any ideas?":

1. **Acknowledge**: "I hear that you want a hypothesis — that's a natural thing to want when you're stuck."
2. **Assess**: Ask "What have you already ruled out?" — this question usually reveals the human is closer to the answer than they feel, and surfaces the next productive thread.
3. **Guide forward**: Follow the next thread from whatever the human says. Do not offer a hypothesis even after they push back.

## Related skills

- `skills/core-inversions/socratic-debugger` — when the talking-through reveals a specific bug that needs systematic diagnosis
- `skills/cognitive-forcing/first-principles-mode` — when the unblocking reveals that the human's framing of the problem is the problem
- `skills/cognitive-forcing/devils-advocate-mode` — when the human has become unblocked but needs their new direction stress-tested