playbooks

home / skills / openclaw / skills / overcome-problem

overcome-problem skill

/skills/jhillin8/overcome-problem

This skill helps you break complex problems into actionable steps with structured thinking, progress tracking, and obstacle handling to reach clear outcomes.

npx playbooks add skill openclaw/skills --skill overcome-problem

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
2.2 KB
---
name: overcome-problem
description: Break down any problem with structured thinking, action plans, and progress tracking
author: clawd-team
version: 1.0.0
triggers:
  - "help me overcome"
  - "stuck on problem"
  - "how do I solve"
  - "break down problem"
  - "overcome challenge"
---

# Overcome Any Problem

Transform obstacles into solvable steps. Structured thinking beats brute force.

## What it does

- **Problem decomposition** - Break complex challenges into discrete, manageable pieces
- **Action planning** - Generate step-by-step execution paths with clear dependencies
- **Obstacle identification** - Anticipate blockers before they derail progress
- **Progress tracking** - Monitor advancement and adjust course mid-execution

## Usage

### Define Problem
State the challenge clearly. What's blocking you? What does success look like?

### Break it Down
Decompose into 8 angles: functional, technical, temporal, resource, risk, stakeholder, precedent, creative.

### Create Action Plan
Sequence tasks with dependencies. Identify parallelizable work. Flag critical path items.

### Track Progress
Update status as you execute. Log blockers. Trigger re-analysis if assumptions break.

### Review Obstacles
When stuck, inspect the directive. What changed? What was missed? Update and retry.

## Problem-Solving Framework

**Define** - Clarify the problem statement. State constraints and success criteria.

**Analyze** - Apply multiple lenses (technical, financial, temporal, creative, etc).

**Generate options** - Brainstorm 3+ solution paths. Don't filter yet.

**Choose** - Select the highest-leverage path. Justify the choice.

**Execute** - Run the action plan. Track assumptions in real-time.

**Review** - Evaluate outcome. What worked? What's the directive update?

## Tips

- Start with the constraint. Problems are bottleneck puzzles. Remove the tightest constraint first.
- Think in primitives. What's the smallest building block? Build up from there.
- Multiply, don't add. Each system should amplify everything below it.
- Parallel over sequential. Find independent work streams. Execute simultaneously.
- All data stays local on your machine. No cloud dependencies, full privacy control.

Overview

This skill breaks down any problem into clear components, builds a practical action plan, and tracks progress toward resolution. It combines structured thinking, multi-angle analysis, and iterative review to turn vague obstacles into executable tasks. Use it to clarify goals, anticipate blockers, and maintain momentum while adjusting plans as reality changes.

How this skill works

You start by defining the problem and success criteria, then the skill decomposes the challenge across eight angles (functional, technical, temporal, resource, risk, stakeholder, precedent, creative). It generates sequenced tasks with dependencies, highlights parallel work and critical path items, and provides checkpoints for progress updates. When blockers appear, it triggers obstacle analysis and suggests course corrections.

When to use it

  • Facing a complex project with unclear scope or many moving parts
  • Needing a step-by-step execution plan with dependencies and parallel tasks
  • When progress stalls and you must identify root causes and next steps
  • Prioritizing work to remove the tightest constraint first
  • Reviewing outcomes and updating the directive after new information

Best practices

  • Start by writing a concise problem statement with measurable success criteria
  • Decompose across multiple lenses rather than relying on a single perspective
  • Generate at least three distinct solution paths before choosing one
  • Flag assumptions explicitly and track them during execution
  • Prefer parallelizable tasks where safe; isolate the critical path
  • Log blockers immediately and trigger re-analysis when assumptions fail

Example use cases

  • Planning a product launch with cross-functional dependencies and tight deadlines
  • Solving a technical outage by isolating root causes, creating remediation steps, and tracking fixes
  • Breaking an ambitious personal goal into weekly, testable experiments
  • Coordinating a research project that requires resource allocation and stakeholder alignment
  • Reworking a stalled initiative by identifying overlooked constraints and replanning

FAQ

How granular should task decomposition be?

Break tasks until each one is independently actionable in a single work period or owned by a specific person. Avoid over-fragmenting into trivial steps.

What if the chosen path fails?

Log what changed, revisit assumptions, and re-run the analysis. Use one of the pre-generated alternative paths or create a new hybrid approach.