When Stuck - Problem-Solving Dispatch

Map stuck symptoms to problem-solving techniques and dispatch testable approaches.

3|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/zircote/agents --skill when-stuck-problem-solving-dispatch-zircote
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: When Stuck - Problem-Solving Dispatch
Source: https://github.com/zircote/agents/tree/main/skills/problem-solving/when-stuck
Command: npx skills add https://github.com/zircote/agents --skill when-stuck-problem-solving-dispatch-zircote

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify and apply the most effective problem-solving technique when you are unsure which approach to take, reducing guesswork and accelerating resolution.

Core Features & Use Cases

  • Maps stuck symptoms to validated problem-solving techniques, enabling fast, deterministic decision-making.
  • Provides a structured process: identify, load, apply, and iterate techniques to resolve problems across domains.
  • Supports combining techniques for complex scenarios and offers actionable next steps with practical examples.

Quick Start

Describe your stuck symptom and ask for the recommended problem-solving technique.

Frequently Asked Questions about When Stuck - Problem-Solving Dispatch

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

FAQPage Schema
How do I choose the right problem-solving technique when I'm stuck?

To choose the right problem-solving technique, match your specific stuck symptoms to a predefined taxonomy of techniques. This deterministic mapping identifies the most effective approach to reduce guesswork and accelerate resolution.

What is the best way to apply root-cause analysis to a complex software engineering issue?

The best way to apply root-cause analysis is to describe your stuck symptom, load the dispatched technique, and apply it to diagnose the issue. You can combine multiple techniques for complex scenarios and iterate until resolved.

How do I map technical symptoms to a concrete problem resolution workflow?

You map technical symptoms to a problem resolution workflow by identifying the specific stuck-type, then using a deterministic mapping to load and apply a validated technique. This yields a concrete, testable approach for resolving the issue.

Can I combine multiple decision-making techniques for a single complex problem?

Yes, you can combine multiple decision-making techniques for complex scenarios. The process supports iterating through several methods, allowing you to apply and combine techniques to produce actionable next steps.

Does this problem-solving dispatch method work without predefined technique categories?

No, this problem-solving dispatch method requires a predefined taxonomy of techniques. It relies on a deterministic mapping from symptoms to methods to accurately identify and load the appropriate technique for your specific issue.

Why does my current problem-solving approach feel like guesswork?

Your current problem-solving approach feels like guesswork because it lacks a deterministic mapping from symptoms to methods. By dispatching a predefined taxonomy of techniques based on specific symptoms, you apply a structured process to resolve problems across domains.