Problem-Solving Techniques

Identify stuck symptoms and apply structured problem-solving techniques to actionable steps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BoneTheDeveloper/Electronic-Contact-Contact-Book --skill problem-solving-techniques-bonethedeveloper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Problem-Solving Techniques
Source: https://github.com/BoneTheDeveloper/Electronic-Contact-Contact-Book/tree/main/.claude/skills/problem-solving
Command: npx skills add https://github.com/BoneTheDeveloper/Electronic-Contact-Contact-Book --skill problem-solving-techniques-bonethedeveloper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic approaches that help individuals and teams break through blocking situations by applying proven problem-solving patterns.

Core Features & Use Cases

  • Symptom-to-Technique Dispatch: Maps stuck symptoms to proven strategies like Simplification Cascades, Collision-Zone Thinking, Meta-Pattern Recognition, Inversion Exercise, and Scale Game.
  • Structured Application Process: Step-by-step guidance from symptom identification to applying the chosen technique and documenting results.
  • Comprehensive Reference Library: Includes accessible references for each technique to deepen understanding.

Quick Start

Identify your stuck symptom, choose the recommended technique from the quick-dispatch guide, and apply it to produce a concrete next step.

Frequently Asked Questions about Problem-Solving Techniques

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

FAQPage Schema
How do I apply systematic problem-solving when I am stuck on a software engineering task?

Systematic problem-solving maps your stuck symptoms to structured techniques like Simplification Cascades or Meta-Pattern Recognition, moving you from a blocking state to actionable engineering steps.

What is the best way to troubleshoot recurring engineering patterns and complexity spirals?

Troubleshoot recurring patterns by identifying specific stuck symptoms and applying targeted techniques like Meta-Pattern Recognition or Inversion Exercise to break complexity spirals into manageable steps.

How do I break down innovation blocks and assumption constraints during product development?

Break down innovation blocks by applying structured techniques like Collision-Zone Thinking to challenge assumption constraints and generate concrete next steps for product development.

Can I use these problem-solving techniques for operations and design workflows, or are they limited to software engineering?

These problem-solving techniques are applicable across software engineering, product, design, and operations workflows to resolve scale uncertainty and other blocking situations.

How do I move from identifying a stuck symptom to producing a concrete next step?

Move from symptom to step by using a symptom-to-technique dispatch guide, selecting a proven strategy, applying it through a structured process, and documenting the resulting actionable step.

Why does my engineering decision-making fail when facing scale uncertainty?

Decision-making under scale uncertainty often fails without structured systems-thinking techniques like the Scale Game, which prescribe actionable steps to navigate blocking complexity.