From workflow
Resets failed coding approaches: re-analyzes core problem, identifies missing context, proposes 2-3 alternatives with trade-offs, recommends production-ready path forward. Activates on 'wrong' or dead ends.
How this skill is triggered — by the user, by Claude, or both
Slash command
/workflow:wrongThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
The current approach isn't working as expected. Step back and re-examine the problem from the beginning.
The current approach isn't working as expected. Step back and re-examine the problem from the beginning.
State the problem in clear, simple terms. What exactly are we trying to solve?
Determine what additional information is needed about:
Suggest 2-3 alternative solutions that:
For each proposed approach, briefly explain:
Which approach is most appropriate and why?
Ask clarifying questions before proceeding.
npx claudepluginhub umputun/cc-thingz --plugin workflowOne-shot perspective reset that scans your current work, generates an abstract reframing question, and runs 3 quick checks (scope drift, side effects, better approach) in under 10 lines.
Dispatches structured techniques for coding stuck points: simplification for complexity spirals, inversion for assumptions, scale testing for mismatches, minimal reproduction for failures.
Challenges agent's recent claims and forces genuine re-examination using code-reading tools when users push back with 'wtf are you thinking', 'that's wrong', or similar.