mcpbeat

When Stuck Problem Solving Dispatch

mrgoonie/when stuck - problem-solving dispatch

Dispatch to the right problem-solving technique based on how you're stuck

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
1
copies elsewhere
how many repositories repackaged it
2189
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/mrgoonie/claudekit-skills --skill When Stuck - Problem-Solving Dispatch

The instruction itself

7 sections, as written by the author

When Stuck - Problem-Solving Dispatch

Overview

Different stuck-types need different techniques. This skill helps you quickly identify which problem-solving skill to use.

Core principle: Match stuck-symptom to technique.

Quick Dispatch

digraph stuck_dispatch {
    rankdir=TB;
    node [shape=box, style=rounded];

    stuck [label="You're Stuck", shape=ellipse, style=filled, fillcolor=lightblue];

    complexity [label="Same thing implemented 5+ ways?\nGrowing special cases?\nExcessive if/else?"];
    innovation [label="Can't find fitting approach?\nConventional solutions inadequate?\nNeed breakthrough?"];
    patterns [label="Same issue in different places?\nFeels familiar across domains?\nReinventing wheels?"];
    assumptions [label="Solution feels forced?\n'This must be done this way'?\nStuck on assumptions?"];
    scale [label="Will this work at production?\nEdge cases unclear?\nUnsure of limits?"];
    bugs [label="Code behaving wrong?\nTest failing?\nUnexpected output?"];

    stuck -> complexity;
    stuck -> innovation;
    stuck -> patterns;
    stuck -> assumptions;
    stuck -> scale;
    stuck -> bugs;

    complexity -> simp [label="yes"];
    innovation -> collision [label="yes"];
    patterns -> meta [label="yes"];
    assumptions -> invert [label="yes"];
    scale -> scale_skill [label="yes"];
    bugs -> debug [label="yes"];

    simp [label="skills/problem-solving/\nsimplification-cascades", shape=box, style="rounded,filled", fillcolor=lightgreen];
    collision [label="skills/problem-solving/\ncollision-zone-thinking", shape=box, style="rounded,filled", fillcolor=lightgreen];
    meta [label="skills/problem-solving/\nmeta-pattern-recognition", shape=box, style="rounded,filled", fillcolor=lightgreen];
    invert [label="skills/problem-solving/\ninversion-exercise", shape=box, style="rounded,filled", fillcolor=lightgreen];
    scale_skill [label="skills/problem-solving/\nscale-game", shape=box, style="rounded,filled", fillcolor=lightgreen];
    debug [label="skills/debugging/\nsystematic-debugging", shape=box, style="rounded,filled", fillcolor=lightyellow];
}

Stuck-Type → Technique

| How You're Stuck | Use This Skill |

|------------------|----------------|

| Complexity spiraling - Same thing 5+ ways, growing special cases | skills/problem-solving/simplification-cascades |

| Need innovation - Conventional solutions inadequate, can't find fitting approach | skills/problem-solving/collision-zone-thinking |

| Recurring patterns - Same issue different places, reinventing wheels | skills/problem-solving/meta-pattern-recognition |

| Forced by assumptions - "Must be done this way", can't question premise | skills/problem-solving/inversion-exercise |

| Scale uncertainty - Will it work in production? Edge cases unclear? | skills/problem-solving/scale-game |

| Code broken - Wrong behavior, test failing, unexpected output | skills/debugging/systematic-debugging |

| Multiple independent problems - Can parallelize investigation | skills/collaboration/dispatching-parallel-agents |

| Root cause unknown - Symptom clear, cause hidden | skills/debugging/root-cause-tracing |

Process

  • Identify stuck-type - What symptom matches above?
  • Load that skill - Read the specific technique
  • Apply technique - Follow its process
  • If still stuck - Try different technique or combine

Combining Techniques

Some problems need multiple techniques:

  • Simplification + Meta-pattern: Find pattern, then simplify all instances
  • Collision + Inversion: Force metaphor, then invert its assumptions
  • Scale + Simplification: Extremes reveal what to eliminate

Remember

  • Match symptom to technique
  • One technique at a time
  • Combine if first doesn't work
  • Document what you tried

Repackaged in 1 other repositories

same content, different owner
aAAaqwq/AGI-Super-Team open on GitHub →

How to use it

Copy the folder

Take mrgoonie/when stuck - problem-solving dispatch from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.