ck:problem-solving

Structured problem-solving techniques resolve stuck software design issues by identifying the specific symptom, such as complexity spiraling or assumption constraints, and dispatching a matching pattern from a quick reference to guide resolution. This reproducible approach applies to complex, multi-domain issues without external dependencies.

Symptom-based dispatch is a problem-solving mechanism where you identify the specific characteristics of a stuck problem, like recurring patterns or complexity spiraling, to select and apply the most relevant structured technique from a quick reference for targeted resolution.

Yes, these problem-solving patterns apply effectively to organizational decision-making and product strategy. The dispatch-based approach is designed for cross-domain applicability, guiding users through complex, multi-domain issues beyond just software engineering.

To apply inversion techniques when complexity spirals, describe your stuck problem and consult the quick reference to load deep-dive guidance. This dispatch workflow matches your specific symptoms to the appropriate technique for targeted problem resolution.

No, you do not need external dependencies to apply these scaling and complexity techniques. The problem-solving skill operates safely with zero dependencies, using a frontmatter-driven entry and internal references to guide the resolution process.