---
description: Deep collaborative thinking about a problem - read code, consult experts, explore options, think together
argument-hint: <problem to think through>
allowed-tools: Task, Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion
---

Think through this problem deeply: $ARGUMENTS

## Instructions

Load the `ideate` skill, then:

### 1. Understand What's Being Asked

- **User's words:** [exact quote]
- **Your interpretation:** [what you think they mean]
- **Scope:** [what's in/out]

If interpretation differs, **ask**.

### 2. Gather Context

```bash
grep -rn "[keywords]" --include="*.go" --include="*.ts"
```

Read the specs, docs, adjacent systems.

### 3. Explore the Solution Space

Write out 3-4 options (always include "do nothing"):

```markdown
### Option A: [Name]
- Approach: [how]
- Pros: [why good]
- Cons: [why risky]
- Assumption: [what must be true]
```

### 4. Step Back

- **Assumptions:** What am I assuming that's unverified?
- **Fresh eyes:** Would someone new agree?
- **Skeptic:** What would a disagreer say?
- **Missing:** Whose perspective am I ignoring?

### 5. Think Out Loud

Share: what you learned, what surprised you, the core tension, where you're leaning, questions for them.

### 6. Collaborate

Listen, adjust, drill deeper, iterate.

## Critical Rules

- READ code before forming opinions
- INCLUDE "do nothing" as an option
- SURFACE assumptions explicitly
- INVITE dialogue, don't just deliver answers
