Problem-Solving Techniques

Map stuck-problem symptoms to systematic problem-solving techniques.

2|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/hotriluan/alkana-dashboard --skill problem-solving-techniques-hotriluan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Problem-Solving Techniques
Source: https://github.com/hotriluan/alkana-dashboard/tree/main/.opencode/skill/problem-solving
Command: npx skills add https://github.com/hotriluan/alkana-dashboard --skill problem-solving-techniques-hotriluan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This collection helps individuals and teams move past stuck moments by applying a suite of systematic problem-solving techniques tailored to different patterns.

Core Features & Use Cases

  • Symptom-to-technique mapping: Use the When Stuck guidance to identify the most effective technique for a given problem.
  • Core techniques: Simplification Cascades, Collision-Zone Thinking, Meta-Pattern Recognition, Inversion Exercise, Scale Game.
  • Practical application: Combine techniques to handle complex problems across software, design, and operations.

Quick Start

Describe a stuck problem to enable the system to dispatch the correct problem-solving technique from the reference.

Frequently Asked Questions about Problem-Solving Techniques

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve stuck software problems when complexity spirals out of control?▼

To resolve stuck problems, this skill uses a symptom-to-technique mapping that identifies the correct systematic approach. It guides you through a safe iterative workflow to break complexity spirals and document the resolution process.

What is the best way to handle scale uncertainty in system design?▼

To handle scale uncertainty, this skill applies the Scale Game technique to systematically analyze architectural and operational constraints. It provides reference-guided application to resolve scaling issues across software and organizational contexts.

How do I break recurring patterns and innovation blocks during development?▼

You can break recurring patterns and innovation blocks by applying Meta-Pattern Recognition and the Inversion Exercise. These systematic techniques identify root causes and challenge assumption constraints to unblock development progress.

Can I use systematic problem-solving techniques for organizational and operations issues?▼

Yes, these systematic problem-solving techniques apply directly to organizational and operations contexts. The framework resolves recurring patterns and assumption constraints across software, design, and operational workflows.

When should I apply Collision-Zone Thinking to resolve a design problem?▼

Apply Collision-Zone Thinking to resolve design problems when facing innovation blocks or conflicting constraints. This technique systematically maps symptoms to targeted approaches, navigating design collisions through an iterative workflow.