---
name: mode
description: Declare or switch working mode. Available modes — explore, build, think-with, ship, cool-off.
argument-hint: <mode>
---

# Switch Working Mode

Declare the current working mode for this session.

Modes shape posture — what kind of output to produce, how much to load, when to pause.

## Arguments

The user requested mode: **$ARGUMENTS**

If no mode was provided, list the available modes and ask which one:

| Mode | Posture |
|------|---------|
| **explore** | Divergent, curious. Follow threads. No commitment to output. |
| **build** | Focused, generative. Produce artifacts. Show the thing. |
| **think-with** | Reflective. Hold complexity. Don't rush to solutions. |
| **ship** | Convergent, decisive. Finish what's in front of you. |
| **cool-off** | Minimal output. Wind down. Integration time. |

## Workflow

### If Vibe Harness MCP is available

Call `vibe_set_mode` with the requested mode. The Vibe Harness tracks mode duration, transition history, and metabolic state. Display the response.

### If Vibe Harness is not available

Acknowledge the mode switch in conversation. Note:
- What mode you're switching **from** (if one was active)
- What mode you're switching **to**
- Any posture shift this implies (e.g., moving from explore to ship means narrowing focus)

If switching from a deep mode (explore, think-with) to an output mode (build, ship), briefly summarise what was explored before shifting gears. Transitions have a cost — name it.

## Custom Modes

The five starter modes cover most knowledge work. If the user has defined custom modes in their CLAUDE.md or `config/modes.md`, honour those instead. The function matters, not the label.