Help us improve
Share bugs, ideas, or general feedback.
From unstuck
Use when entering Strike 2 of the unstuck protocol — initial diagnosis failed and you need a fundamentally different approach
npx claudepluginhub jugrajsingh/skillgarden --plugin unstuckHow this skill is triggered — by the user, by Claude, or both
Slash command
/unstuck:pivotingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Strike 2 of the unstuck protocol. The diagnosis fix didn't work — try a fundamentally different approach.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Strike 2 of the unstuck protocol. The diagnosis fix didn't work — try a fundamentally different approach.
NEVER repeat what Strike 1 already tried. The diagnosis failed — doing it again won't help.
If a knowledge pack was loaded:
Search the codebase for similar code that works:
# Find similar patterns in the codebase
grep -rn "{RELEVANT_PATTERN}" --include="*.{EXT}" | head -20
List every difference between the working code and the broken code:
| Aspect | Working | Broken |
|--------|---------|--------|
| ... | ... | ... |
Focus on: imports, configuration, argument order, types, async/sync mismatch, middleware/decorator order.
Question what Strike 1 took for granted:
Pick ONE alternative approach:
| If Strike 1 tried... | Pivot to... |
|---|---|
| Fixing the current code | Using a different library/API |
| Debugging data flow | Rewriting the function from scratch |
| Config changes | Hardcoding values to isolate the issue |
| Async approach | Sync equivalent (or vice versa) |
| Complex solution | Simplest possible implementation |
Implement the alternative. Test with the same verification as Strike 1.
Report to the orchestrator:
Pivot:
Approach: {WHAT_WAS_TRIED}
Differs from Strike 1: {HOW}
Result: { resolved | not resolved }
Evidence: {WHAT_WAS_LEARNED}
If resolved, include the alternative that worked and why. If not resolved, include what was ruled out — this narrows the search for Strike 3.