problem-solving

To solve complex problems, describe your stuck problem, use the dispatch workflow to map symptoms to a specific technique, load the corresponding reference guide, and apply it step by step to document actionable insights.

The inversion exercise is a structured problem-solving technique that helps resolve stubborn challenges by reversing the problem to identify constraints and avoid failure paths across domains.

You need systematic problem-solving techniques when you are stuck in ambiguity and require a repeatable process to move from complex constraints to actionable insights in product design or organizational strategy.

Yes, you can use these cross-domain problem-solving methods for software engineering and organizational strategy, as the toolkit supports applying structured techniques to real-world scenarios across multiple domains.

The best way to diagnose a stuck problem using pattern recognition is to map your specific stuck symptoms to the dispatch guidance, which routes you to the appropriate technique reference for structured resolution.

The limitation of structured problem-solving frameworks is that they rely on YAML frontmatter and a references directory, requiring you to manually map symptoms to techniques rather than automatically resolving constraints.