getting-unstuck

Diagnose technical blockers through a 3-strike escalation protocol and generate RCA documents.

1|Updated Jan 31, 2026

Search Tags:#developer tools #debugging #troubleshooting #escalation #RCA #blocker resolution

Ready to run

npx skills add https://github.com/jugrajsingh/skillgarden --skill getting-unstuck

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: getting-unstuck
Source: https://github.com/jugrajsingh/skillgarden/tree/main/plugins/unstuck/skills/getting-unstuck
Command: npx skills add https://github.com/jugrajsingh/skillgarden --skill getting-unstuck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a structured, multi-step protocol to help users overcome technical blockers by systematically diagnosing, pivoting, and escalating issues.

Core Features & Use Cases

3-Strike Protocol: Guides users through Diagnose, Pivot, and Escalate phases.
RCA Generation: Creates a persistent Root Cause Analysis document for each issue.
Contextual Knowledge: Leverages language and framework detection to load relevant knowledge packs.
Use Case: When a developer is stuck on a complex bug for hours, they can invoke this skill to systematically try different approaches and document the process, ensuring progress or a clear escalation path.

Quick Start

Use the getting-unstuck skill to help resolve an issue with a runtime error in your Python application.

Frequently Asked Questions about getting-unstuck

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

FAQPage Schema

How do I resolve technical blockers when I am stuck debugging a complex software issue?▼

A structured 3-strike escalation protocol helps resolve technical blockers by guiding you through diagnosing the issue, pivoting strategies after failed attempts, and escalating when necessary. It ensures systematic troubleshooting and generates an RCA document.

What is the 3-strike escalation protocol for troubleshooting development issues?▼

The 3-strike escalation protocol is a structured troubleshooting process consisting of Diagnose, Pivot, and Escalate phases. It helps developers systematically attempt different approaches to resolve a blocker and document the process for escalation.

How do I create a Root Cause Analysis document for a runtime error?▼

You can generate a persistent Root Cause Analysis (RCA) document automatically by running a structured troubleshooting protocol on your runtime error. The RCA captures the diagnostic steps, pivot attempts, and final resolution path for future reference.

Does this troubleshooting protocol work with my programming language and framework?▼

Yes, the troubleshooting protocol detects your programming language and framework context to load relevant knowledge packs. This contextual awareness provides more effective problem-solving tailored to your specific development environment.

When should I escalate a technical blocker instead of trying another debugging approach?▼

You should escalate a technical blocker after completing the Diagnose and Pivot phases of the 3-strike protocol without resolving the issue. Escalation provides a clear path forward when systematic troubleshooting attempts fail to overcome the blocker.

What is the best way to pivot strategies when initial debugging attempts fail?▼

The best way to pivot strategies is to follow a structured troubleshooting protocol that forces a change in approach after initial attempts fail. This prevents repetitive debugging cycles and drives progress toward either a resolution or a documented escalation.