skills.rest
MinhHoangDono
MinhHoangDonoCOMMUNITY
Explore all skills by this author →
GitHub

problem-solving

Diagnose stuck patterns and apply systematic problem-solving techniques.

Updated Mar 7, 2026
Search Tags:#debugging#scalability#strategy#innovation#problem-solving#assumption testing#root-cause thinking
One-click install
npx skills add https://github.com/MinhHoangDono/antigravity-kit --skill problem-solving-minhhoangdono
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: problem-solving
Source: https://github.com/MinhHoangDono/antigravity-kit/tree/main/.agent/skills/problem-solving
Command: npx skills add https://github.com/MinhHoangDono/antigravity-kit --skill problem-solving-minhhoangdono

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you break out of being stuck by diagnosing the specific pattern behind the blockage and applying a targeted, structured technique instead of looping on ad-hoc attempts.

Core Features & Use Cases

  • Dispatch by stuck symptom: Choose the right approach for complexity spirals, innovation blocks, recurring patterns, assumption constraints, or scale uncertainty.
  • Five core techniques: Use Simplification Cascades, Collision-Zone Thinking, Meta-Pattern Recognition, Inversion Exercise, and Scale Game to generate actionable direction.
  • Systematic application process: Identify the stuck-type, apply the matching technique, and document insights for reuse across similar problems.

Quick Start

Tell your AI assistant: "I’m stuck implementing this problem; diagnose the stuck-type and apply the most appropriate technique to produce the next concrete steps and insights."

Frequently Asked Questions about problem-solving

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

FAQPage Schema
How do I resolve recurring implementation mistakes in my software architecture?▼

To resolve recurring implementation mistakes, apply Meta-Pattern Recognition to diagnose the underlying pattern and document insights, preventing the same architectural errors from repeating.

Can I use assumption testing to break through an innovation block in feature development?▼

The best way to handle uncertainty about production scalability is to apply the Scale Game technique, which systematically diagnoses scale constraints and produces actionable architectural direction.

When should I apply root-cause thinking instead of trying random debugging strategies?▼

Yes, you can use the Inversion Exercise technique to test forced assumptions, systematically breaking through innovation blocks by challenging constraints and generating new implementation pathways.

How do I systematically diagnose a software engineering blockage to find clear next steps?▼

Apply root-cause thinking when complexity spirals or recurring patterns cause stuck moments, dispatching a systematic problem-solving technique to diagnose the underlying issue rather than attempting random fixes.

Can I use assumption testing to break through an innovation block in feature development?▼

Systematically diagnose a software engineering blockage by identifying the specific stuck symptom, dispatching the matching problem-solving technique, and documenting the resulting insights for consistent reuse.

Related Skills

Explore More Software Engineering Skills→
spacholski1225spacholski1225
2

When Stuck - Problem-Solving Dispatch

Map stuck symptoms to problem-solving techniques and dispatch matching methods.

Community
Basic
thesimonhothesimonho
26

learn

Extract reusable error-resolution and debugging patterns into Markdown skill files.

Community
Intermediate
noahsilve123noahsilve123
1

systematic-debugging

Debug technical issues through root cause analysis and hypothesis testing.

Community
Advanced
hungtrandigitalhungtrandigital

problem-solving

Map software engineering symptoms to problem-solving techniques.

Community
Intermediate