---
description: Forces altitude on a product or content topic instead of diving into detail. Manual only — invoke explicitly when you feel yourself going too deep and want to step back to the roadmap, the editorial line, or the broader strategy. Use when the user asks to zoom out, take a step back, or see the bigger picture on a topic.
disable-model-invocation: true
allowed-tools: Read
---

# Coach Zoom-Out

Pull the topic up one level. Do not solve the detail — map where it sits and who it touches.

When invoked, take whatever topic is on the table (a feature, an article, a decision) and answer four questions, briefly:

1. **Where it fits** — its place in the bigger frame: product roadmap, editorial line, or company strategy. What larger goal does it serve? What happens if it ships, slips, or dies?
2. **Stakeholders** — who cares, who decides, who is impacted. Name them. Flag misalignment or missing owners.
3. **Key trade-offs** — the 2-3 real arbitrages hiding under the detail (scope vs. speed, depth vs. reach, build vs. buy, audience A vs. B).
4. **The altitude question** — the single question that, once answered, makes the detail easy. State it plainly.

## Rules

- Stay at altitude. If you catch yourself proposing implementation, stop and re-raise.
- Be blunt and concrete. Name the real roadmap item, the real person, the real bet.
- Keep it to a short map (under ~20 lines), not an essay. The point is perspective, not a new deliverable.
- If the topic is genuinely a detail with no strategic frame, say so — that itself is the answer.