Menu
Dispatch to the right problem-solving technique based on how you're stuck
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
| name | When Stuck - Problem-Solving Dispatch |
| description | Dispatch to the right problem-solving technique based on how you're stuck |
| when_to_use | when stuck and unsure which problem-solving technique to apply for your specific type of stuck-ness |
| version | 1.1.0 |
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.
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];
}
| 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 |
Some problems need multiple techniques: