when-stuck

Problem-solving techniques are dispatched by matching your current symptoms to a decision graph covering complexity, innovation gaps, pattern repetition, assumption traps, scaling doubts, and debugging issues. This directs you to a specialized sub-skill for rapid technique selection.

Choosing a problem-solving method for a complex codebase involves identifying your specific blockage type through a symptom-to-technique mapping decision graph. This process directs you to targeted techniques like simplification-cascades to handle the complexity effectively.

You can combine multiple problem-solving techniques by following the Skill's guidance on blending methods when a single approach falls short. It provides a decision graph that links your current symptoms to specific sub-skills, allowing you to integrate multiple techniques systematically.

Yes, this problem-solving dispatch model explicitly handles assumption traps and scaling doubts. It applies a decision graph to six common stuck scenarios, including complexity, innovation gaps, pattern repetition, scaling doubts, and debugging issues, to recommend the appropriate technique.

Your debugging approach may fail because pattern repetition issues require specialized problem-solving techniques rather than standard debugging. This Skill identifies pattern repetition as a distinct stuck scenario and dispatches you to targeted sub-skills designed to break those specific cycles.