problem-solver

Structure complex problems into evidence-based analyses with ranked recommendations.

1|Updated May 18, 2026
One-click install
npx skills add https://github.com/linenoize/topia --skill problem-solver-linenoize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-solver
Source: https://github.com/linenoize/topia/tree/main/skills/problem-solver
Command: npx skills add https://github.com/linenoize/topia --skill problem-solver-linenoize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you analyze ambiguous, high-stakes, or complex problems by forcing structured reasoning before conclusions, reducing guesswork and cognitive bias.

Core Features & Use Cases

  • Domain classification: Distinguishes clear, complicated, complex, chaotic, or confused situations so the analysis depth matches the problem.
  • Bias detection: Flags confirmation bias, anchoring, sunk cost, overconfidence, and other decision traps before they distort judgment.
  • Framework selection: Chooses the right method for the task, such as 5 Whys, Fishbone, SWOT, PESTLE, weighted decision matrices, or pre-mortems.
  • Use case: A developer diagnosing repeated production failures can use it to isolate root causes, test assumptions, and produce ranked remediation options.
  • Use case: A team choosing between competing technical directions can use it to compare trade-offs, run a steel-manned evaluation, and select a recommendation with evidence.

Quick Start

Ask the problem-solver skill to analyze your problem, classify its complexity, identify likely biases, and return a ranked set of solutions.

Frequently Asked Questions about problem-solver

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

FAQPage Schema
How do I structure root cause analysis for complex software problems?

Root cause analysis for complex software problems is structured by classifying the domain, detecting cognitive biases, selecting reasoning frameworks like 5 Whys or Fishbone, and producing ranked remediation options. This approach separates symptoms from actual root causes.

What is the best way to evaluate technical architecture trade-offs?

Evaluating technical architecture trade-offs is best done by applying weighted decision matrices and pre-mortems to compare options. This process steel-mans competing directions, tests underlying assumptions, and selects an evidence-backed recommendation.

How do I identify cognitive bias when making high-stakes technical decisions?

Identifying cognitive bias in high-stakes technical decisions involves actively checking for confirmation bias, anchoring, sunk cost, and overconfidence before conclusions are drawn. Structured reasoning frameworks flag these decision traps to prevent distorted judgment.

When do I need structured problem-solving frameworks for ambiguous work?

You need structured problem-solving frameworks when facing ambiguous, high-stakes, or complex situations where guesswork risks outcomes. Frameworks like SWOT or PESTLE match analysis depth to the problem, decomposing unclear work into ranked decisions.

Can I use this approach for diagnosing repeated production failures?

Yes, you can use this approach for diagnosing repeated production failures by isolating root causes and testing assumptions. It systematically distinguishes symptoms from actual failures and generates ranked remediation options for technical settings.

What are the limitations of using decision frameworks for problem decomposition?

The limitation of using decision frameworks for problem decomposition is that they require accurate domain classification to be effective. If a complex situation is misclassified as merely complicated, the selected framework and resulting recommendations may mismatch the actual problem.