When Stuck - Problem-Solving Dispatch

Problem-solving technique selection starts by mapping your specific symptom—like code bugs or complexity spiraling—to a matching diagnostic method. This dispatch skill identifies the stuck-type and loads the appropriate guided workflow to resolve the issue.

Symptom-based technique selection is a diagnostic method that matches recurring patterns, faulty assumptions, or scale uncertainty to specific problem-solving workflows. It guides users through a step-by-step process to apply and combine techniques effectively.

To diagnose recurring patterns and faulty assumptions, you dispatch a targeted problem-solving workflow that guides you through structured diagnosis. This approach identifies underlying issues and directs you to techniques that break the cycle.

You need to combine problem-solving techniques during workflow diagnosis when a single method cannot address overlapping symptoms like complexity spiraling and scale uncertainty. The dispatch process includes combination rules to apply multiple techniques effectively.

Yes, you can use this problem-solving dispatch for general tasks outside of software engineering. It covers common stuck-types such as need for innovation and scale uncertainty across general problem-solving scenarios, not just code bugs.

The best way to handle complexity spiraling is using a problem-solving dispatch to select the correct technique based on your exact symptoms. This prevents choosing the wrong approach by mapping the issue to a structured, guided workflow.