Spell Zoom Out

## Summary

**Strategic problem validation.** Takes a plan, decision, or direction and challenges it from five lenses: problem reframing, inversion, opportunity cost, second-order effects, and upstream analysis. Produces a strategic recommendation — stay course, adjust, pivot, or stop — with evidence-backed findings and specific next actions.

**Arguments:** `$ARGUMENTS` (required) - The plan, decision, or direction to challenge

**Output:** Structured strategic analysis with findings, convergence map, recommendation, and next actions output directly to the conversation (Write is available if the user requests the output be saved to a file)

---

## Skill References

Before proceeding, load the relevant skill documents for reference:

Read the following files from the repository root:
- `docs/skills/problem-framing.md`
- `docs/skills/strategic-thinking.md`

---

## Process

### Phase 1: Ground

#### Step 1: Parse Arguments

**If `$ARGUMENTS` is empty:**
Ask the user: "What plan, decision, or direction should I challenge?"

**Otherwise:**
- Extract the plan, decision, or direction from `$ARGUMENTS`
- Continue to Step 2

#### Step 2: Map Current Framing

Establish what the current framing IS before challenging it. Understand the direction as its proponents see it.

**Codebase analysis (if relevant):**
- Check if the topic relates to the current codebase — look for relevant code, config, docs, ADRs, or prior decisions

**Web research (if available):**
Search the web for current best practices, case studies, and documented failures related to the topic.

**Graceful degradation:** If web search is unavailable, rely on built-in knowledge and codebase analysis. Note this honestly in the Coverage field.

**Output the current framing:**