"Activate when: someone says 'I keep pushing harder but nothing's working'; a manager feels they need to control every detail; a founder is forcing growth that isn't happening; a team is over-engineering something; someone says 'let it happen', 'stop forcing', or 'effortless action'.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add deciqAI/knowledge-skills --skill wu-wei --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Wu Wei?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/deciqai-wu-wei)More formats (shields.io, HTML) on the badges page.
---
name: wu-wei
description: "Activate when: someone says 'I keep pushing harder but nothing's working'; a manager feels they need to control every detail; a founder is forcing growth that isn't happening; a team is over-engineering something; someone says 'let it happen', 'stop forcing', or 'effortless action'.
Do NOT activate when: the situation is a genuine emergency requiring immediate intervention; the user is a novice in a domain where they haven't yet trained the underlying skill. More: deciqai.com/s/wu-wei"
---
# Wu Wei (无为, Effortless Action)
## Overview
**Wu wei (无为)** — Daoist principle (*Daodejing*, ~4th century BCE): act *without forcing*, not without acting. A skilled manager or craftsman in wu wei is fully active; they simply do not oppose the situation's natural dynamic. Diagnostic: forcing produces resistance proportional to force; wu wei produces disproportionate effect with less effort. Modern parallel: Csikszentmihalyi's *flow* (1990). Wu wei is the expert mode — the fruit of deliberate practice, not its bypass.
Composes with [`middle-way`](../middle-way/SKILL.md), [`occams-razor`](../occams-razor/SKILL.md), [`feedback-loops`](../feedback-loops/SKILL.md), [`metacognition`](../metacognition/SKILL.md).
## When to Use
- A manager is over-managing employees who would perform better with less direction
- A product team is over-engineering a feature that should be cut entirely
- A negotiator is too aggressive in a deal that needed gentler tempo
- A founder is forcing growth that should be allowed to compound
- Personal practice: forcing meditation, creativity, or a relationship
- Someone says "wu wei," "effortless action," "flow," "stop forcing," "act with the grain"
**Not when:** the situation requires active intervention (e.g., a fire); you haven't trained the underlying skill; the "natural dynamic" is actually destructive (wu wei is not fatalism).
## Coaching Novices (Adaptive Front Door)
- **Engine mode:** user has a concrete case → run The Process directly.
- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.
In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.
1. One-line: wu wei isn't doing nothing — it's acting *with* the situation's own dynamic instead of forcing against it, often by subtracting your own friction rather than adding more effort.
2. Check fit: true emergency / novice in domain / destructive natural dynamic → not this lens.
3. Elicit the specific situation where forcing isn't working.
> **[WAIT — do not advance until user responds]**
4. One question at a time: where are you forcing? what direction is the situation already moving? what would happen if you stopped?
> **[WAIT — do not advance until user responds]**
5. Close: name the specific forcing to stop + the natural dynamic to align with.
> **[WAIT — do not advance until user responds]**
## The Process
**Step 1 — Identify the forcing:** What are you trying to make happen? What resistance are you encountering? (Forcing = diminishing returns as effort increases.)
**Step 2 — Diagnose the natural dynamic:** What direction is the situation already moving? What would happen if you stopped intervening?
**Step 3 — Subtract before adding:** What action is making it worse (habit/anxiety)? What is genuinely necessary? Remove the former; keep the latter.
**Step 4 — Act with the grain:** What does the situation want? What is the minimum-effort, maximum-leverage action?
**Step 5 — Empirical test:** After removing the forcing — did resistance drop and outcomes improve?
**Step 6 — Train the skill:** Wu wei is the expert mode. What deliberate practice would let you act with the grain habitually?
## Output: Wu Wei Analysis
```markdown
# Wu Wei Analysis: <situation>
## Forcing — what's being forced / effort applied / resistance encountered:
## Natural dynamic — direction situation is moving / what happens without intervention:
## Subtraction — action to stop (habit/anxiety) / action to keep (necessary):
## Aligned action — action with the grain / leverage point:
## Test — did removing the forcing improve outcomes?
## Skill training — what deliberate practice precedes wu wei here?
```
*→ Method in Action: [Zhuangzi's Cook Ding, ~3rd century BCE](examples/zhuangzi-cook-ding-3rd-century-bce.md)*
## Pack: Wu Wei Patterns
| Situation | Forcing failure mode | Wu wei move |
|---|---|---|
| Managing a high-performer | Micromanagement, over-feedback | Set context, remove obstacles, let them work |
| Product development | Forcing every feature into spec | Cut ruthlessly; let scope match resources |
| Negotiation | Aggressive demands, hard deadlines | Match counterparty's tempo; find their actual constraints |
| Founder fundraising | Pitching everyone, forcing meetings | Get inbound; aligned investors say yes early anyway |
| Engineering management | More process, more meetings | Subtract: remove low-value meetings, give focus time |
## Applying It Well
- **Remove before adding** — the highest-leverage move is often subtractive.
- **Observe the natural dynamic honestly**, including when it's unflattering.
- **Wu wei requires trained skill** — Cook Ding trained for three years first.
- **Org wu wei:** remove obstacles, let competence operate; most management failures are forcing.
*→ Primary sources: [references/sources.md](references/sources.md)*
## Common Rationalizations
**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**
| Fake move | Reality |
|---|---|
| [D] "Wu wei means do nothing" | Wu wei means act *without forcing* — strong action can still be wu wei. |
| [D] "I'm being wu wei by not trying" | If you haven't trained the skill, you're a novice, not wu wei. |
| [D] Skipping practice to "be natural" | Wu wei is the fruit of practice, not its bypass. |
| [D] Applying wu wei in genuine emergencies | A fire needs action. Wu wei doesn't override "intervention required." |
| [D] Treating frustration as proof to try harder | Frustration often signals forcing — step back and observe. |
| [D] Romanticizing wu wei to avoid hard decisions | "Going with the flow" can be evasion; honest wu wei faces destructive dynamics too. |
| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |
## Red Flags
- Effort increasing while outcomes deteriorate | resistance proportional to your push
- Can't articulate the situation's natural dynamic
- Claiming wu wei in a domain you haven't trained | using wu wei to avoid a needed action
## Verification
- [ ] Specific forcing identified; natural dynamic honestly diagnosed (including if destructive)
- [ ] What to subtract distinguished from what to keep; aligned action designed
- [ ] After subtraction, resistance actually dropped (empirical test)
- [ ] Underlying skill deliberately trained; not misapplied to genuine emergencies
---
*Part of **deciqAI Knowledge Skills** — 237 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/s/wu-wei** · Built by deciqAI · github.com/deciqAI · Contributions welcome.*
*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/wu-wei.json*
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!