When Stuck - Problem-Solving Dispatch

To find the right problem-solving technique when stuck, this dispatch skill identifies the specific nature of your blocker, such as complexity, flawed assumptions, or debugging needs, and recommends targeted techniques to resolve it.

The best way to simplify code with too many special cases is to use problem-solving dispatch to identify the complexity and recommend specific techniques like the simplification-cascades method to streamline logic.

To choose a debugging method for recurring patterns, this skill analyzes your specific stuck-type and dispatches you to targeted debugging techniques that address the root cause of the repetition.

Yes, you can use this dispatch technique for innovation needs and scalability concerns, as it categorizes these specific types of being stuck and matches them with appropriate problem-solving skills.

You should use a problem-solving dispatch instead of standard debugging when you are unsure of the root cause, such as dealing with flawed assumptions or innovation needs, and need help identifying the correct approach.