when-stuck

Diagnose stuckness types and dispatch users to specialized problem-solving techniques.

2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/ucirello/sgai --skill when-stuck-ucirello
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: when-stuck
Source: https://github.com/ucirello/sgai/tree/main/cmd/sgai/skel/.sgai/skills/problem-solving/when-stuck
Command: npx skills add https://github.com/ucirello/sgai --skill when-stuck-ucirello

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you identify and select the most effective problem-solving technique when you find yourself stuck, ensuring you don't waste time on approaches that won't work.

Core Features & Use Cases

  • Stuck-Type Identification: Diagnoses the nature of your problem (e.g., complexity, innovation block, assumption-bound).
  • Technique Dispatch: Recommends specific problem-solving skills tailored to your identified stuck-type.
  • Use Case: You're trying to refactor a complex piece of code but keep hitting dead ends. This skill helps you determine if you need a simplification cascade, inversion exercise, or another approach.

Quick Start

Use the when-stuck skill to find the best problem-solving technique for a complex coding issue.

Frequently Asked Questions about when-stuck

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

FAQPage Schema
How do I choose the right debugging strategy when I am stuck on a complex coding problem?

To choose the right debugging strategy when stuck, identify your specific roadblock type, such as complexity, recurring patterns, or assumptions, to dispatch to the matching problem-solving technique.

What is the best way to troubleshoot recurring issues and innovation blocks during software development?

Troubleshooting recurring issues and innovation blocks involves diagnosing your specific stuckness type to select targeted techniques like meta-pattern-recognition or inversion-exercise for effective resolution.

How do I find a problem-solving technique for refactoring code that hits dead ends?

Finding a problem-solving technique for refactoring code hitting dead ends requires identifying if the issue stems from scale or complexity to recommend approaches like simplification-cascades.

When should I use systematic debugging instead of other troubleshooting strategies?

You should use systematic debugging instead of other troubleshooting strategies when your specific type of stuckness is diagnosed as a debugging challenge, ensuring targeted and effective problem resolution.