Search

PythonReactSEOPDF
OpenClaw

structure-thinking

Structured problem analysis and communication using system mapping and hierarchical logic. Use when a request involves messy, multi-factor problems, root-cause analysis, intervention design, feedback loops or delays, or when a clear top-line recommendation with logically grouped support is required.

caoyumin970 source installs☆ 0 Repository stars

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

SkillHub CLI

skillhub install caoyumin97/structure-thinking

Inspect the source and compatibility requirements, then follow its installation steps.

Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.

View source ↗Guides

Skill instructions

Structure Thinking

Overview

Use this skill to turn a messy situation into a clear decision path. You will model the system to find real levers, then build a compact argument that enables action. The focus is practical: define the decision, diagnose the system behavior, choose interventions, and communicate a decisive recommendation.

Preferred Inputs

  • Decision owner and deadline.
  • Success definition (metric, threshold, or observable change).
  • Constraints (budget, time, policy, technical limits).
  • Behavior over time (trend, seasonality, oscillation).

If any are missing and the user wants an answer now, proceed with explicit assumptions and mark them as Assumed.

Workflow

1) Define the Decision and Question

Goal: one clear governing question and a provisional answer.

Do:

  • Write a one-sentence decision statement: “Decide whether to X by date Y to achieve Z.”
  • Capture Situation, Complication, Question, Answer.
  • List assumptions and unknowns explicitly.

Output:

  • Governing question.
  • Provisional answer in one sentence.
2) Describe Behavior Over Time

Goal: pin the problem to a trend, not a feeling.

Do:

  • Summarize how the key metric changes over time.
  • Note seasonality, spikes, or oscillations.
  • State the time horizon that matters.

Output:

  • Behavior-over-time summary (2-4 bullets).
3) Model the System

Goal: explain why the behavior persists.

Do:

  • Define system boundary and stakeholders.
  • Identify 1-3 critical stocks and their flows.
  • Draw reinforcing and balancing loops.
  • Mark delays and missing information.

Output:

  • System map notes: stocks, flows, loops, delays.
4) Generate Hypotheses (MECE)

Goal: create testable explanations or options.

Do:

  • Build an issue tree with 3-5 MECE branches.
  • Label each branch as an assertion (not a topic).
  • Rank branches by impact and evidence availability.

Output:

  • Issue tree with ranked branches.
5) Select Leverage Points and Interventions

Goal: choose a small set...

Source information

Source
github
Repository
openclaw/skills
Path
skills/caoyumin97/structure-thinking
Version
—
Commit
55e37afceafdafd6104a08ae3eeceb591fcc3be5
Classification source
rules
Status
active
Visibility
public

These signals come from indexed source analysis and may lag behind changes. Check the current source files.

Extracted content

SKILL.md
# Structure Thinking

## Overview
Use this skill to turn a messy situation into a clear decision path. You will model the system to find real levers, then build a compact argument that enables action. The focus is practical: define the decision, diagnose the system behavior, choose interventions, and communicate a decisive recommendation.

## Preferred Inputs
- Decision owner and deadline.
- Success definition (metric, threshold, or observable change).
- Constraints (budget, time, policy, technical limits).
- Behavior over time (trend, seasonality, oscillation).

If any are missing and the user wants an answer now, proceed with explicit assumptions and mark them as `Assumed`.

## Workflow

### 1) Define the Decision and Question
Goal: one clear governing question and a provisional answer.

Do:
- Write a one-sentence decision statement: “Decide whether to X by date Y to achieve Z.”
- Capture `Situation`, `Complication`, `Question`, `Answer`.
- List assumptions and unknowns explicitly.

Output:
- Governing question.
- Provisional answer in one sentence.

### 2) Describe Behavior Over Time
Goal: pin the problem to a trend, not a feeling.

Do:
- Summarize how the key metric changes over time.
- Note seasonality, spikes, or oscillations.
- State the time horizon that matters.

Output:
- Behavior-over-time summary (2-4 bullets).

### 3) Model the System
Goal: explain why the behavior persists.

Do:
- Define system boundary and stakeholders.
- Identify 1-3 critical stocks and their flows.
- Draw reinforcing and balancing loops.
- Mark delays and missing information.

Output:
- System map notes: stocks, flows, loops, delays.

### 4) Generate Hypotheses (MECE)
Goal: create testable explanations or options.

Do:
- Build an issue tree with 3-5 MECE branches.
- Label each branch as an assertion (not a topic).
- Rank branches by impact and evidence availability.

Output:
- Issue tree with ranked branches.

### 5) Select Leverage Points and Interventions
Goal: choose a small set...

Related skills

OpenClaw

a-stock-trader

bombfuock

A股模拟交易系统 - 数据爬取、存储、策略回测、模拟交易 / A-Share Paper Trading System - Data Fetch, Storage, Backtest, Simulation

OpenClaw

adaptive-skill-factory

505768069-rgb

Discover, install, update, or create the right skill when a workflow gap appears. Use when a task is repetitive, a role lacks a reliable procedure, an existing skill might save time, ClawHub search/install coul...