Menu
Dispatch to the right problem-solving technique based on how you're stuck
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when starting any conversation in Trae - establishes mandatory skill activation, Trae tool mapping, and workflow priority before any response or action
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when executing implementation plans with independent tasks in the current session
Use when you have a spec or requirements for a multi-step task, before touching code
Use when tests have arbitrary sleeps/timeouts, race conditions, flaky async behavior, or timing-dependent failures
Use after finding a root cause when adding validation at multiple layers would make the bug impossible or obvious
| 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 | Skill(name="simplification-cascades") |
| Need innovation - Conventional solutions inadequate, can't find fitting approach | Skill(name="collision-zone-thinking") |
| Recurring patterns - Same issue different places, reinventing wheels | Skill(name="meta-pattern-recognition") |
| Forced by assumptions - "Must be done this way", can't question premise | Skill(name="inversion-exercise") |
| Scale uncertainty - Will it work in production? Edge cases unclear? | Skill(name="scale-game") |
| Code broken - Wrong behavior, test failing, unexpected output | Skill(name="systematic-debugging") |
| Multiple independent problems - Can parallelize investigation | Skill(name="dispatching-parallel-agents") |
| Root cause unknown - Symptom clear, cause hidden | Skill(name="root-cause-tracing") |
Skill(name="<skill>") for the specific techniqueSome problems need multiple techniques: