A Claude Code plugin that encodes the Heath Brothers' Switch framework into structured workflows for leading change. The framework's insight: change fails not because people are lazy but because what looks like resistance is often a lack of clarity (Rider), emotional exhaustion (Elephant), or a hostile environment (Path).
Outputs are plain markdown, git-tracked, and compound over time. Each change initiative's diagnosis and outcomes feed the next.
Analyzes a change challenge through the Rider/Elephant/Path lens:
- Define the change -- what specifically needs to change, for whom
- Find bright spots -- where is the desired change already happening?
- Map the Rider -- is there clarity? Do people know what to do?
- Map the Elephant -- is there motivation? Do people feel the need?
- Map the Path -- is there support? Does the environment make it easy?
- Diagnose the sticking point -- where is this change primarily stuck?
Produces a diagnosis at docs/switch/current-diagnosis.md.
The primary intervention workflow. Reads the diagnosis sticking-point ranking and sequences all three intervention types in priority order:
- Rider interventions -- bright spot replication, critical moves, destination postcard
- Elephant interventions -- find the feeling, shrink the change, grow your people
- Path interventions -- environment tweaks, habit building, herd rallying
Produces intervention plans in docs/switch/interventions/.
Standalone skills for focused work on a single dimension:
/sw:direct-- Rider interventions only/sw:motivate-- Elephant interventions only/sw:shape-- Path interventions only
Use these for revising or deepening one dimension after an initial /sw:intervene pass.
Captures what the other skills don't -- the meta-insights about change:
- Which resistance was actually Rider confusion vs. Elephant fear
- Which interventions worked and which didn't, and why
- Real-world outcomes from implemented changes
- Cross-initiative patterns
Add the marketplace:
/plugin marketplace add Untangling-Systems/switch
Install the plugin:
/plugin install switch@Untangling-Systems-switch
Reload to activate:
/reload-plugins
Then use the skills from any project:
/sw:diagnose migrate engineering team to trunk-based development
/sw:intervene
/sw:compound
Diagnose --> Intervene (Rider + Elephant + Path) --> Implement --> Record outcomes --> Diagnose again
|
Compound <-- real-world results ----------------------------------------+
Each session reads from the knowledge stores before starting. Prior diagnoses surface so you don't repeat failed approaches. Prior intervention outcomes show which tactics worked for similar challenges.
| Store | Contents | Created by |
|---|---|---|
docs/switch/current-diagnosis.md + diagnoses/ |
Change diagnosis + archived versions | /sw:diagnose |
docs/switch/interventions/ |
Rider/Elephant/Path intervention plans with outcomes | /sw:intervene, /sw:direct, /sw:motivate, /sw:shape, /sw:compound |
docs/switch/patterns/ |
Cross-initiative learnings and patterns | /sw:compound |
The skills enforce the framework -- that's the point:
- Redirect with reasoning -- explains why the step matters
- Warn and flag -- notes the skip, proceeds with a warning
- Let the output speak -- downstream skills surface gaps
Examples: "That's a goal, not a behavior change." "That's a training program, not an environment tweak." "You've designed Rider interventions but haven't addressed the Elephant."
- Friction is the product. The forced Rider/Elephant/Path decomposition produces insight.
- Compound over time. Initiative 5 should be sharper than initiative 1.
- Framework fidelity. All three dimensions must be addressed. Skipping one is the most common change failure mode.
- Built for change leaders. Framework reasoning is surfaced inline.
- Plain markdown, git-tracked. Everything is greppable.
- Flywheel -- AI-powered positioning, copy, and growth workflows
- Compound Engineering -- AI-powered development tools from Every.to
- Compound Knowledge -- Knowledge work workflows from Every.to
MIT