problem-solving

Map software engineering symptoms to problem-solving techniques.

Updated Dec 12, 2025
One-click install
npx skills add https://github.com/hungtrandigital/ResidentOne --skill problem-solving-hungtrandigital
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-solving
Source: https://github.com/hungtrandigital/ResidentOne/tree/main/0-agents/agents/skills/problem-solving
Command: npx skills add https://github.com/hungtrandigital/ResidentOne --skill problem-solving-hungtrandigital

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

A catalog of problem-solving techniques and dispatch logic to apply the right method for the situation.

Core Features & Use Cases

  • Lightweight dispatch system to map symptoms to techniques
  • References to detailed guides for each technique
  • Quick-start prompts to apply techniques to real problems

Quick Start

Dispatch to the right technique using the problem-solving skill for a given symptom.

Frequently Asked Questions about problem-solving

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

FAQPage Schema
How do I systematically approach a complex software engineering problem I'm stuck on?

Problem-solving techniques provide a structured dispatch system that maps your specific symptom—whether it's complexity spiraling, innovation blocks, or scale uncertainty—to the right technique. The Skill applies methods like Simplification Cascades, Collision-Zone Thinking, and Meta-Pattern Recognition to move from symptom to actionable solution rapidly.

What techniques are available for breaking through recurring architectural or design patterns?

The Skill references five core techniques: Simplification Cascades reduce overwhelming complexity, Collision-Zone Thinking exposes hidden constraints, Meta-Pattern Recognition identifies recurring structures, Inversion Exercise flips assumptions, and Scale Game tests viability across contexts. Each maps to specific problem categories across development, architecture, and operations.

When should I use problem-solving dispatch instead of debugging or refactoring alone?

Use dispatch when you face assumption constraints, general stuck-ness, or patterns that repeat across projects. Debugging targets specific bugs; this Skill targets the deeper structural or methodological block preventing progress—ideal when conventional troubleshooting hasn't resolved the root issue.

How do I know which problem-solving technique applies to my situation?

The Skill provides a symptom-based dispatch system: describe your blocker—complexity spiraling, innovation blocks, scale uncertainty, or constraint violation—and the system routes you to the matching technique with quick-start prompts and detailed reference guides for immediate application.

Can I use these problem-solving techniques across different domains—development, architecture, and operations?

Yes. The techniques are domain-agnostic and apply across development, architecture, and operations contexts. Each technique reference includes domain-neutral heuristics and patterns that transfer across technology stacks and problem spaces.