sw:diagnose

Analyze change challenges with the Rider/Elephant/Path framework and write a markdown diagnosis file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps leaders and teams discover why a proposed change is not happening by mapping clarity (Rider), motivation (Elephant), and environment (Path) into a single, evidence-based diagnosis that can drive prioritized interventions.

Core Features & Use Cases

  • Structured six-step diagnosis: Define the specific behavior change, find bright spots, map Rider, Elephant, and Path, and rank the primary sticking point.
  • Revision and pipeline support: Revise targeted sections of an existing diagnosis or run headless with provided context and reasonable assumptions.
  • Persistent, git-friendly output: Produces and archives a markdown diagnosis at docs/switch/current-diagnosis.md and docs/switch/diagnoses/[slug]-[date].md for downstream planning and tracking.

Quick Start

Ask the skill to analyze a change by saying: /sw:diagnose migrate the engineering team to trunk-based development

Frequently Asked Questions about sw:diagnose

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

FAQPage Schema
How do I diagnose why a process change is stuck in my team?

Diagnose a stalled process change by mapping clarity, motivation, and environment evidence using the Rider, Elephant, and Path framework to identify and rank the primary sticking point for targeted intervention planning.

What is the Rider Elephant Path framework for change management?

The Rider Elephant Path framework is a change diagnosis method mapping Rider clarity, Elephant motivation, and Path environment friction to identify evidence-based reasons why organizational transformations stall.

How do I find bright spots during an organizational change diagnosis?

Find bright spots during change diagnosis by identifying specific instances where the target behavior already happens successfully, then map those Rider, Elephant, and Path factors to isolate enabling conditions.

Can I run an automated change diagnosis headless with provided context?

Run change diagnosis headless by providing operational context and reasonable assumptions to map Rider, Elephant, and Path evidence automatically, generating a markdown diagnosis file without interactive input.

Does change diagnosis output integrate with existing planning workflows?

Change diagnosis integrates with planning workflows by generating persistent, git-friendly markdown files archived at docs/switch/current-diagnosis.md and dated slug paths for downstream intervention tracking.

When should I use a structured change diagnosis workflow instead of direct intervention?

Use structured change diagnosis instead of direct intervention when stalled adoptions or feature rollouts require evidence-based identification of whether clarity, motivation, or environmental friction is the primary blocker.