ck:problem-solving

Diagnose stuck problems and dispatch systematic problem-solving techniques.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/DatTran26/KienTruThiHanh --skill ck-problem-solving-dattran26
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:problem-solving
Source: https://github.com/DatTran26/KienTruThiHanh/tree/main/.agents/skills/problem-solving
Command: npx skills add https://github.com/DatTran26/KienTruThiHanh --skill ck-problem-solving-dattran26

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Solving stuck problems by applying a structured, dispatch-based problem-solving skill that guides users through proven techniques.

Core Features & Use Cases

  • Systematic diagnosis of stuck-type symptoms using a mapped technique dispatch.
  • Access to a library of reference guides (e.g., Simplification Cascades, Collision-Zone Thinking, Meta-Pattern Recognition, Inversion Exercise, Scale Game, When Stuck).
  • Guided, reproducible problem-solving workflow with documentation of insights and outcomes.

Quick Start

Describe a stuck problem and generate a structured, dispatch-guided problem-solving plan.

Frequently Asked Questions about ck:problem-solving

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

FAQPage Schema
How do I solve recurring stuck problems in software engineering?

Recurring stuck problems can be solved by applying systematic problem-solving techniques that map symptoms to proven methods like Simplification Cascades and Meta-Pattern Recognition, generating a structured workflow to unblock work.

What is dispatch-driven problem solving and when should I use it?

Dispatch-driven problem solving is a workflow that maps your specific stuck-type symptoms to targeted techniques, consulting reference guides and recording insights. Use it for complexity spirals, innovation blocks, and scale uncertainty across product and engineering contexts.

How do I apply systematic problem-solving techniques to overcome complexity spirals?

To overcome complexity spirals, describe the stuck problem to generate a structured plan. The system diagnoses symptoms using a mapped technique dispatch, applying methods like Simplification Cascades to systematically reduce and resolve the spiral.

Can I use these problem-solving techniques for process and product issues, not just engineering code?

Yes, these systematic problem-solving techniques apply to complex, recurring problems across product, process, and engineering contexts. They address innovation blocks, assumption constraints, and scale uncertainty, ensuring reproducible diagnosis regardless of domain.

What is the best way to document insights when unblocking stuck work?

The best way to document insights is through a guided, reproducible problem-solving workflow. The system records systematic insights and outcomes as you apply techniques from the reference library, ensuring your unblocking process is fully documented.