problem-solving

Decompose complex problems through a five-phase evidence-based workflow.

4|Updated Sep 6, 2013
One-click install
npx skills add https://github.com/mway/dotfiles --skill problem-solving-mway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-solving
Source: https://github.com/mway/dotfiles/tree/main/home/dot_codex/skills/problem-solving
Command: npx skills add https://github.com/mway/dotfiles --skill problem-solving-mway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured problem-solving methodology that applies systematically to planning, design, debugging, or complex multi-step tasks.

Core Features & Use Cases

  • Phase-based problem solving and documentation
  • Decomposition of problems into actionable tasks
  • Evidence-based reasoning with traceable decisions
  • Adaptable to engineering, design, and research workflows

Quick Start

Guide me through the five-phase problem-solving process to decompose requirements, plan actions, execute steps, verify results, and reflect on outcomes.

Frequently Asked Questions about problem-solving

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

FAQPage Schema
How do I decompose complex requirements into actionable engineering tasks?

To decompose complex requirements, apply a structured five-phase problem-solving workflow that breaks problems down into actionable tasks, ensuring evidence-based reasoning and traceable decisions throughout the process.

What is the best way to structure a debugging workflow for multi-step engineering tasks?

The best way to structure debugging is a five-phase, evidence-based workflow that scopes planning, design, and execution while verifying results and reflecting on outcomes to ensure traceable decisions.

Can I use a structured problem-solving process for design and research workflows?

Yes, this structured problem-solving process is adaptable to engineering, design, and research workflows, applying phase-based decomposition and documentation to systematically tackle complex multi-step tasks.

How does phase-based problem solving ensure traceable decisions during planning?

Phase-based problem solving ensures traceable decisions by decomposing problems into documented, actionable steps across five phases, applying evidence-based reasoning to planning, execution, and verification.

Do I need specific scripts or references to follow a five-phase problem-solving methodology?

No specific scripts are required to start, but the five-phase methodology supports optional resources such as scripts, references, and assets to aid decomposition, execution, and reflection in complex engineering tasks.

When should I use structured problem solving instead of ad-hoc planning for software engineering?

Use structured problem solving for complex multi-step project tasks like planning, design, and debugging, applying a five-phase, evidence-based workflow to decompose requirements and verify outcomes systematically.