Back to Skills

When Stuck - Problem-Solving Dispatch

mrgoonie
Updated Today
17 views
738
118
738
View on GitHub
Othergeneral

About

This skill helps developers identify the right problem-solving technique when they're stuck by matching their specific "stuck-symptom" to appropriate methods. It provides quick dispatch guidance for common scenarios like complexity management, innovation blocks, or pattern recognition. Use it when unsure which problem-solving approach to apply for your particular type of stuck-ness.

Documentation

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 StuckUse This Skill
Complexity spiraling - Same thing 5+ ways, growing special casesskills/problem-solving/simplification-cascades
Need innovation - Conventional solutions inadequate, can't find fitting approachskills/problem-solving/collision-zone-thinking
Recurring patterns - Same issue different places, reinventing wheelsskills/problem-solving/meta-pattern-recognition
Forced by assumptions - "Must be done this way", can't question premiseskills/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 outputskills/debugging/systematic-debugging
Multiple independent problems - Can parallelize investigationskills/collaboration/dispatching-parallel-agents
Root cause unknown - Symptom clear, cause hiddenskills/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

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

Quick Install

/plugin add https://github.com/mrgoonie/claudekit-skills/tree/main/when-stuck

Copy and paste this command in Claude Code to install this skill

GitHub 仓库

mrgoonie/claudekit-skills
Path: .claude/skills/problem-solving/when-stuck

Related Skills

subagent-driven-development

Development

This skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.

View skill

algorithmic-art

Meta

This Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.

View skill

executing-plans

Design

Use the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.

View skill

cost-optimization

Other

This Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.

View skill