Stats
Actions
Tags
From mycelium
Classifies new software problems into Cynefin domains (Clear, Complicated, Complex, Chaotic, Confused) and recommends methods like best practices, expert analysis, or experiments. Updates Claude canvas files.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mycelium:cynefin-classifyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Classify problem domain and route to appropriate methods.
Classify problem domain and route to appropriate methods.
Describe the problem in neutral terms.
Ask diagnostic questions:
Classify into one of five domains using cynefin-routing.md.
Select methods appropriate to the domain:
Cross-reference with Wardley evolution if strategic context is available.
Output:
## Cynefin Classification
Problem: [description]
Domain: [Clear/Complicated/Complex/Chaotic/Confused]
Confidence: [High/Medium/Low]
Liminal: [Yes/No — is this between domains?]
Rationale: [why this classification]
Recommended methods:
- [method 1]
- [method 2]
Warning signs of misclassification:
- [what would indicate we got it wrong]
Update .claude/diamonds/active.yml with the cynefin_domain field for the relevant diamond.
If Wardley mapping was referenced, update .claude/canvas/landscape.yml component evolution stages.
Most real decisions happen in liminal zones — transitional states between domains where characteristics of two adjacent domains blend. If the classification feels uncertain, you may be in a liminal zone rather than a pure domain.
| Transition | What it feels like | Action |
|---|---|---|
| Clear → Complicated | "We have a process but it's not covering edge cases" | Add expert analysis to the existing practice |
| Complicated → Complex | "Experts disagree and new factors keep emerging" | Shift from analysis to experimentation |
| Complex → Chaotic | "Our experiments aren't converging, things are getting worse" | Stabilize first, experiment later |
| Chaotic → Complex | "We've stopped the bleeding, now what?" | Design safe-to-fail probes |
| Clear → Chaotic (catastrophic fold) | "Everything was fine and then it all collapsed" | See warning below |
The most important Cynefin warning: when a system in Clear becomes complacent — rigid rules, no sensing, "we've always done it this way" — it can catastrophically collapse into Chaotic with no warning. The transition is NOT gradual. There is no intermediate Complicated or Complex stage.
Detection signs: Over-reliance on best practices without questioning them. No feedback loops. "We don't need to monitor that." Dismissing edge cases as irrelevant.
Mycelium connection: Theory gates and /mycelium:feedback-review prevent complacent drift by requiring evidence refresh and active sensing at every transition.
Source: Snowden (Cynefin evolution, cynefin.io, 2022+)
APPEND a ### Cynefin Classification entry to .claude/harness/decision-log.md with: domain classified, key indicators, method routed to, confidence in classification.
npx claudepluginhub haabe/mycelium --plugin myceliumClassifies problems by cause-effect to choose the right approach: plan, analyze, experiment, or stabilize. Avoids mismatched methods for clear, complicated, complex, chaotic domains.
Classifies problems into Cynefin Framework domains (Clear, Complicated, Complex, Chaotic, Confusion) and recommends response strategies like sense-analyze-respond. Use when unsure of approach, facing analysis paralysis, or choosing analysis vs experimentation.
Classifies problems into Cynefin Framework domains (Clear, Complicated, Complex, Chaotic, Confusion) and recommends response strategies like probe-sense-respond. Use for approach uncertainty or analysis paralysis.