When Stuck Problem Solving Dispatch

Name: When Stuck Problem Solving Dispatch
Author: aaaaqwq

aaaaqwq/agi-super-skills

7 installs
82 repo stars
Updated August 2, 2026
aaaaqwq/agi-super-skills

when-stuck is a Claude Code dispatch skill that matches your type of stuck-ness to the right problem-solving or debugging technique.

About

when-stuck is a dispatch meta-skill that matches how you are stuck to the right problem-solving technique. It maps symptoms like spiraling complexity, need for innovation, recurring patterns or broken code to specific skills such as simplification-cascades, meta-pattern-recognition or systematic-debugging. A developer uses it to pick the right technique instead of guessing when blocked.

Matches your type of stuck-ness to the right problem-solving technique
Maps eight stuck-symptoms to specific skills like simplification-cascades or systematic-debugging
Meta-skill that dispatches to other problem-solving and debugging skills

When Stuck Problem Solving Dispatch by the numbers

7 all-time installs (skills.sh)
Ranked #2,273 of 3,280 Productivity & Planning skills by installs in the Skillselion catalog
Data as of Aug 3, 2026 (Skillselion catalog sync)

At a glance

when stuck - problem-solving dispatch capabilities & compatibility

Capabilities: problem solving · technique dispatch · debugging routing
Use cases: debugging · planning

From the docs

What when stuck - problem-solving dispatch says it does

Different stuck-types need different techniques.

SKILL.md

**Core principle:** Match stuck-symptom to technique.

SKILL.md

npx skills add https://github.com/aaaaqwq/agi-super-skills --skill when-stuck---problem-solving-dispatch

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/aaaaqwq/agi-super-skills/when-stuck---problem-solving-dispatch.svg)](https://skillselion.com/skills/aaaaqwq/agi-super-skills/when-stuck---problem-solving-dispatch)

Installs	7
repo stars	★ 82
Last updated	August 2, 2026
Repository	aaaaqwq/agi-super-skills ↗

What it does

Identify the right problem-solving technique by matching your stuck-symptom to a specific skill.

Who is it for?

Choosing which problem-solving technique to apply when blocked

Skip if: Executing the technique itself; it only routes to other skills

When should I use this skill?

When stuck and unsure which problem-solving technique fits your situation

By the numbers

8 stuck-type to technique mappings
version 1.1.0

Files

SKILL.mdMarkdownGitHub ↗

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

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