How do I know which problem-solving technique to use?

The skill provides a symptom-to-technique map. For example, if you find yourself implementing the same thing in five different ways, it will direct you to 'simplification-cascades'.

Can I use multiple techniques at once?

Yes, the skill specifically outlines how to combine techniques, such as pairing 'Collision Zone Thinking' with 'Inversion' to break through innovation blocks.

Is this skill only for fixing broken code?

No, it addresses a wide range of 'stuck' states including scaling uncertainty, innovation needs, and managing architectural complexity.

What happens if the first technique doesn't work?

The process recommends trying a different technique from the dispatch list or combining multiple strategies to view the problem from a new perspective.

How does this improve developer workflow?

It reduces 'wheel-spinning' time by providing a structured diagnostic path to a solution rather than relying on trial and error.

Problem-Solving Dispatcher

Name: Problem-Solving Dispatcher
Author: lifangda

bylifangda

•

Productivity & Workflow

Directs developers to the most effective problem-solving techniques by diagnosing specific types of technical roadblocks and bottlenecks.

About

The Problem-Solving Dispatcher is a meta-skill designed to help developers navigate out of 'stuck' states by matching their specific symptoms to proven mental models and frameworks. Whether you are facing spiraling code complexity, architectural assumptions, or scaling uncertainties, this skill provides a structured decision matrix to identify the right strategy—such as inversion exercises, simplification cascades, or systematic debugging. It acts as a diagnostic hub that bridges the gap between encountering a difficult problem and applying the most efficient solution pattern.

Key Features

Visual decision matrix mapping bottlenecks to specialized techniques
Actionable process steps for systematic issue resolution
16 GitHub stars
Symptom-based diagnostic framework for rapid problem identification
Guidance for handling complexity, innovation gaps, and recurring patterns
Strategic frameworks for combining multiple problem-solving methods

Use Cases

Determining the best approach when a project feels over-complicated with excessive special cases
Identifying if a technical hurdle requires a breakthrough in innovation or a systematic debugging process
Breaking free from architectural assumptions that are forcing suboptimal implementation paths

About

Key Features

Visual decision matrix mapping bottlenecks to specialized techniques
Actionable process steps for systematic issue resolution
16 GitHub stars
Symptom-based diagnostic framework for rapid problem identification
Guidance for handling complexity, innovation gaps, and recurring patterns
Strategic frameworks for combining multiple problem-solving methods

Use Cases

Determining the best approach when a project feels over-complicated with excessive special cases
Identifying if a technical hurdle requires a breakthrough in innovation or a systematic debugging process
Breaking free from architectural assumptions that are forcing suboptimal implementation paths