sw:intervene

Generate prioritized Rider, Elephant, and Path intervention plans from a diagnosis file.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Untangling-Systems/switch --skill sw-intervene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sw:intervene
Source: https://github.com/Untangling-Systems/switch/tree/main/skills/sw-intervene
Command: npx skills add https://github.com/Untangling-Systems/switch --skill sw-intervene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams and leaders often know something needs to change but lack a coherent, prioritized plan that addresses clarity (Rider), motivation (Elephant), and environment (Path) together. This Skill turns a diagnosis into a sequenced, actionable set of interventions so change efforts are balanced, evidence-driven, and mutually reinforcing.

Core Features & Use Cases

  • Diagnosis-driven sequencing: Reads the sticking-point ranking from docs/switch/current-diagnosis.md and orders interventions by priority.
  • Triple-dimension orchestration: Runs the full three-step intervention process for Rider, Elephant, and Path, giving the primary dimension deeper focus while ensuring secondary and tertiary dimensions receive meaningful plans.
  • Persistence and discovery: Searches existing intervention files in docs/switch/interventions/, saves new dimension-specific markdown plans using templates, and surfaces connections across dimensions.
  • Pipeline and interactive modes: Supports an automated pipeline mode that skips prompts and a normal mode that asks the user confirmation between dimensions.
  • Use Case: After running /sw:diagnose on a product migration, invoke this Skill to produce prioritized, file-backed intervention plans for rollout, motivation, and environmental changes.

Quick Start

Ask the skill to design interventions by saying: Design interventions for migrating the engineering team to trunk-based development.

Frequently Asked Questions about sw:intervene

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan prioritized interventions for organizational change initiatives?

To plan prioritized organizational change interventions, use a diagnosis-driven approach that sequences actions across Rider, Elephant, and Path dimensions. This method reads existing diagnosis files to produce balanced, evidence-driven, and mutually reinforcing intervention plans for your change scenario.

What is the Rider Elephant Path framework for change management?

The Rider Elephant Path framework splits organizational change into clarity (Rider), motivation (Elephant), and environment (Path). It orchestrates intervention planning by giving the primary dimension deeper focus while ensuring secondary and tertiary dimensions receive meaningful, actionable change plans.

How do I turn a change management diagnosis into an actionable intervention plan?

To turn a diagnosis into an actionable intervention plan, read the sticking-point ranking from your diagnosis file and sequence interventions by priority. This process writes dimension-specific markdown plans using prescribed templates, balancing evidence-driven actions across clarity, motivation, and environment.

Do I need a diagnosis file before designing Rider Elephant Path interventions?

Yes, you need a diagnosis file before designing interventions. This Skill requires an existing diagnosis document to sequence and produce Rider, Elephant, and Path intervention plans. It reads the diagnosis to prioritize sticking points and checks existing intervention files before generating new plans.

Can I automate intervention planning for multiple change scenarios in pipeline mode?

Yes, you can automate intervention planning using pipeline mode. Pipeline mode skips user confirmation prompts between dimensions, allowing the sequential generation of Rider, Elephant, and Path intervention markdown files without manual interaction for multiple organizational change scenarios.

What's the best way to balance motivation and environment changes during a product migration?

The best way to balance motivation and environment changes is triple-dimension orchestration. It runs the full three-step intervention process for Rider, Elephant, and Path together, giving the primary dimension deeper focus while ensuring secondary dimensions receive meaningful, mutually reinforcing plans.