skills.rest
quanganh208
quanganh208COMMUNITY
Explore all skills by this author →
GitHub

ck:problem-solving

Diagnose complex technical problems and dispatch matching problem-solving techniques.

1|Updated Mar 6, 2026
Search Tags:#problem-solving#meta-patterns#inversion#simplification-cascades#scale-testing#collision-zone
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-problem-solving-quanganh208
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:problem-solving
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/problem-solving
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-problem-solving-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Many teams and individuals get stuck on complex, recurring, or assumed constraints that block progress; this Skill gives a structured way to diagnose why you're stuck and which technique will most likely break the impasse. It helps you move from confusion and ad-hoc fixes to a reproducible approach that surfaces the key insight or redesign that removes complexity.

Core Features & Use Cases

  • Symptom-to-technique dispatch: Match your observed stuck-symptom to the most effective technique (simplification, collision, inversion, meta-pattern, scale).
  • Concrete techniques with processes: Step-by-step guidance for Simplification Cascades, Collision-Zone Thinking, Meta-Pattern Recognition, Inversion Exercise, and the Scale Game.
  • Composable application: Combine techniques for complex situations (e.g., Simplification + Meta-pattern, Collision + Inversion).
  • Use Case: When a system has five divergent implementations, use Simplification Cascades to find the unifying abstraction and eliminate duplication.

Quick Start

Describe the specific problem, symptoms, and context in one sentence, for example: "I'm stuck with recurring edge-case complexity across our checkout service and five divergent implementations, recommend which techniques to apply and the first three practical steps."

Frequently Asked Questions about ck:problem-solving

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

FAQPage Schema
How do I resolve recurring edge-case complexity and divergent implementations in software architecture?▼

Resolve recurring edge-case complexity by applying Simplification Cascades to find a unifying abstraction. This systematic technique diagnoses why you are stuck and eliminates duplication across divergent implementations to remove architectural complexity.

What is the best way to diagnose why a team is stuck on complex technical problems?▼

Diagnose why a team is stuck by using a symptom-to-technique dispatch. Match observed stuck-symptoms like assumption constraints or scale uncertainty to effective techniques such as inversion exercises or collision-zone thinking to break the impasse.

How do I apply systematic problem-solving techniques to scale uncertainty in product features?▼

Apply systematic problem-solving to scale uncertainty by running the Scale Game. This step-by-step process tests extreme-scale scenarios within product features and team workflows to surface key redesigns that remove complexity spirals.

When do I need meta-pattern recognition for software engineering blocks?▼

You need meta-pattern recognition when facing recurring technical problems and innovation blocks. This process identifies repeating structural assumptions within software architecture, helping you move from ad-hoc fixes to a reproducible approach.

Can I combine multiple problem-solving techniques for complex system design situations?▼

Yes, you can combine techniques for complex situations. Composable application allows you to merge methods like Simplification and Meta-pattern or Collision and Inversion to diagnose and resolve intricate software architecture design problems.

What are the limitations of using systematic problem-solving techniques for ad-hoc fixes?▼

Systematic problem-solving techniques require clearly described symptoms and context to work effectively. Without a structured problem statement, these methods may not surface the key insights needed to move beyond ad-hoc fixes and resolve design problems.

Related Skills

Explore More Software Engineering Skills→
spacholski1225spacholski1225
2

When Stuck - Problem-Solving Dispatch

Map stuck symptoms to problem-solving techniques and dispatch matching methods.

Community
Basic
kevinnguyen271090kevinnguyen271090
15

problem-solving

Apply structured problem-solving techniques to stuck technical and design sessions.

Community
Basic
dthuy62dthuy62

ck:problem-solving

Select a systematic problem-solving technique for the current blocker.

Community
Intermediate
thavirak-svaythavirak-svay
1

systematic-debugging

Debug software issues through four phases of root cause investigation and testing.

Community
Advanced