sw-intervene

name	sw:intervene
description	Design interventions for all three dimensions (Rider, Elephant, Path) in sticking-point priority order. Reads the diagnosis and orchestrates a complete intervention plan. Use after /sw:diagnose as the primary intervention workflow.
argument-hint	[optional context about the change initiative]

<intervene_context> #$ARGUMENTS </intervene_context>

Intervene

Design a complete set of interventions covering all three dimensions of the Switch framework. Reads the diagnosis sticking-point ranking and sequences interventions in priority order.

When to Use

• After /sw:diagnose -- this is the recommended next step
• "Help me design interventions for this change"
• "What should I do about this change challenge?"
• When you want all three dimensions addressed in one session

Before Starting

Check for diagnosis

Read docs/switch/current-diagnosis.md. Hard redirect if missing (see references/shared-enforcement-prompts.md).

Read sticking point ranking

Extract the sticking-point field from frontmatter and the ranking from Section 6. Determine the sequence:

• Start with the primary sticking point dimension
• Then the secondary
• Then the tertiary

Check for prior interventions

Search docs/switch/interventions/ for existing intervention files. Surface relevant ones:

"You have existing interventions: [list with dates and status]. I'll build on these or create new ones as needed."

Present the plan

"Your diagnosis ranks the sticking point as:

1. [Primary] -- [reasoning from diagnosis]
2. [Secondary] -- [reasoning]
3. [Tertiary] -- [reasoning]

I'll work through interventions in this order. Each dimension gets its own intervention plan."

The Sequence

Run the three intervention types in sticking-point priority order. For each, follow the same step sequence as the standalone skill (/sw:direct, /sw:motivate, /sw:shape). The key difference is that this skill ensures all three are addressed in one session.

For the Primary Dimension

Run the full 3-step intervention process for this dimension (see the corresponding standalone skill for the complete step sequence). Give it the most time and depth.

Use AskUserQuestion between dimensions:

"[Primary dimension] interventions complete. Moving to [secondary dimension]. Ready?"

For the Secondary Dimension

Run the full 3-step process. The user may have less to say here -- that's fine, but all three steps must be at least considered.

For the Tertiary Dimension

Run the full 3-step process. If the diagnosis says this is "not a major factor," acknowledge that:

"Your diagnosis says [dimension] is not a major factor. We'll do a lighter pass, but it's worth checking -- the diagnosis could be wrong, and small [dimension] interventions can reinforce the other two."

Assembling the Intervention Plans

After all three dimensions are complete:

1. Save each dimension's intervention plan to its own file using the corresponding template:
   • docs/switch/interventions/rider-{slug}-{date}.md
   • docs/switch/interventions/elephant-{slug}-{date}.md
   • docs/switch/interventions/path-{slug}-{date}.md
2. Present a summary of all three plans together
3. Highlight connections between dimensions (e.g., "The environment tweak in Path supports the critical move in Rider")

After Saving

Use AskUserQuestion:

Question: "Intervention plans saved for all three dimensions. What next?"

Options:

1. Run /sw:compound -- Save what you learned during this session
2. Revise a dimension -- Deepen or change one dimension's interventions (/sw:direct, /sw:motivate, or /sw:shape)
3. Revise the diagnosis -- Run /sw:diagnose if the interventions revealed gaps
4. Done for now -- Implement and come back with results

Important Rules

• All three dimensions must be addressed. This is the whole point of this skill vs. the individual intervention skills.
• Primary gets the most depth. But secondary and tertiary still need real interventions, not placeholders.
• Surface connections. The best change efforts have interventions that reinforce each other across dimensions.
• Use the diagnosis. Every intervention should connect back to specific evidence from the diagnosis.

Pipeline Mode

When invoked with disable-model-invocation context:

• Skip all AskUserQuestion prompts
• Use diagnosis sticking-point ranking to determine sequence
• Work through all three dimensions using available information
• Make reasonable assumptions, flag them in output
• Write all three output files without waiting for confirmation