Problem-Solving Techniques

Map stuck-problem symptoms to structured techniques for guided remediation.

Updated Dec 16, 2025
One-click install
npx skills add https://github.com/nguyenvanlinh1902/trackingSolar --skill problem-solving-techniques-nguyenvanlinh1902
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Problem-Solving Techniques
Source: https://github.com/nguyenvanlinh1902/trackingSolar/tree/main/.opencode/skill/problem-solving
Command: npx skills add https://github.com/nguyenvanlinh1902/trackingSolar --skill problem-solving-techniques-nguyenvanlinh1902

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Problem-solving can stall teams; this guide provides a structured set of techniques to diagnose and overcome stuck moments.

Core Features & Use Cases

  • Symptom-to-technique mapping: quickly match a stuck symptom to an applicable technique.
  • Guided application: follow a repeatable process to apply techniques and document insights.
  • Reference-loaded depth: access targeted reference guides to deepen understanding as needed.

Quick Start

Identify your stuck symptom, then select the matching technique and follow its process to generate actionable steps.

Frequently Asked Questions about Problem-Solving Techniques

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

FAQPage Schema
What is a systematic approach for diagnosing a problem when my team is stuck?

The problem-solving workflow guides you through symptom identification, technique selection, reference loading, and guided application with progressive disclosure to systematically resolve a stuck problem and generate actionable steps.

How do I apply problem-solving techniques to match symptoms to a remediation workflow?

You identify the stuck symptom, select the matching technique, load targeted reference guides for depth, and follow a repeatable process to apply the technique and document insights for progressive remediation.

Can I use these problem-solving techniques for operations and product management, not just software engineering?

Yes, you can use these structured problem-solving techniques to diagnose and overcome inefficiencies across software, product, and operations domains by matching symptoms to applicable techniques.

What's the best way to structure problem-solving when facing unclear operational inefficiencies?

The best way to structure problem-solving is using a defined workflow that starts with symptom identification, selects matching techniques, and applies them through guided application with progressive disclosure.

When should I not use a symptom-dispatch workflow for problem-solving?

You should avoid the symptom-dispatch workflow for problem-solving if your situation lacks clearly identifiable symptoms or if the issue requires immediate ad-hoc fixes rather than a structured, repeatable diagnostic process.