Verified:GitHub

strategic-problem-solving

Guide structured four-phase problem-solving to identify root causes and verifiable fixes.

4|Updated Mar 16, 2018

Search Tags:#problem-solving #root-cause-analysis #systems-thinking #architectural-decisions #structured-reasoning #debugging-frameworks

Ready to run

npx skills add https://github.com/InNoobWeTrust/dotfiles --skill strategic-problem-solving

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: strategic-problem-solving
Source: https://github.com/InNoobWeTrust/dotfiles/tree/main/.agents/skills/strategic-problem-solving
Command: npx skills add https://github.com/InNoobWeTrust/dotfiles --skill strategic-problem-solving

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides teams through structured problem-solving to replace ad-hoc debugging with repeatable methods, enabling faster root-cause analysis and better architectural decisions.

Core Features & Use Cases

Three-Phase Framework: Define the problem, analyze root causes, solve with action plans, and challenge results to ensure quality.
Elicitation & Adversarial Validation: Built-in prompts to surface assumptions and test them against evidence and alternative viewpoints.
Operational Runbook: Step-by-step phases that normalize debugging workflows and reduce recursion loops.

Quick Start

Provide a structured, four-phase problem-solving workflow to identify root causes and propose verifiable fixes.

Frequently Asked Questions about strategic-problem-solving

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

FAQPage Schema

How do I find the root cause of a tricky software bug instead of trial-and-error debugging?▼

Structured problem-solving for tricky bugs uses a four-phase framework: Define the problem, Analyze root causes, Solve with action plans, and Challenge results. This operational runbook normalizes debugging workflows and reduces recursion loops through systematic hypothesis testing.

What is structured problem-solving for complex software systems?▼

Structured problem-solving for complex software systems is a framework-based method applying systems thinking to multi-concern failures. It uses disciplined elicitation to surface assumptions, test hypotheses against evidence, and implement verifiable architectural decisions rather than relying on ad-hoc debugging.

How do I make better architectural decisions when facing multi-concern failures?▼

To make better architectural decisions during multi-concern failures, apply structured reasoning that surfaces root causes through adversarial validation. This challenges assumptions against alternative viewpoints and evidence, ensuring your architectural decisions are verifiable and robust.

Can I use a systematic debugging framework for both code defects and architectural decisions?▼

Yes, this systematic debugging framework applies to both tricky code defects and architectural decisions. It normalizes workflows across software systems by guiding you through defining issues, analyzing root causes, and validating solutions to handle multi-concern failures effectively.

What's the best way to challenge and validate root cause analysis results?▼

The best way to validate root cause analysis results is through adversarial validation. This built-in elicitation process forces you to challenge assumptions, test hypotheses against alternative viewpoints and evidence, ensuring the final fixes are verifiable and accurate.