rubber-duck

Structured problem articulation prevents premature solutions by forcing you to answer three essential questions first: what is the actual problem, what have you tried, and what is your real goal. This process clarifies vague descriptions and catches XY problems where the stated request hides the underlying issue.

Rubber-duck debugging is a method where you explain a problem aloud or in writing to clarify your thinking before solving it. Use it when facing vague problem descriptions, frustration signals, or when you suspect the real goal differs from what was initially stated.

XY problems occur when someone asks how to do X, but their real need is Y. Detection happens through targeted questioning that probes the actual goal. This Skill guides you to reflect back what you heard, confirm alignment with the user's intent, and only then propose solutions.

Follow five steps: first, resist solving immediately; second, ask three clarifying questions to define the problem; third, probe deeper if answers remain unclear; fourth, reflect back what you understood; fifth, propose solutions only after the user confirms alignment with their actual goal.

Yes, when problems are vaguely described or frustration is evident. Taking time to ask structured questions upfront prevents wasted effort on wrong solutions and ensures both parties align on the actual problem before attempting fixes.