zoom-out · v1.1.1 · 2026-10-08 · sha256 342ae5c0d2bee085

zoom-out v1.1.1A

Immutable. This exact content never changes and is served at /api/v1/blob/342ae5c0d2bee085.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_teu4scf32hfwwqj7/342ae5c0d2bee0851eb1f1b3fd812c072c631a949ecbbbfde976eab4a1464b91.json

Then /plugin install zoom-out@markdownregistry-teu4scf32hfwwqj7 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: zoom-out
version: 1.1.1
description: |
  Guide a decision from a higher level: step back from the code to show which modules a change touches, how they connect, and what it affects that is not obvious. Reads the project's CONTEXT.md or domain glossary when available. Use when asked to "step back", "zoom out", "give me the big picture", "which modules does this change touch?", "what does this change affect?", "what am I missing here", before a structural decision when you want a map first, or when a change feels bigger than expected.
disable-model-invocation: true
requires_agent_teams: false
requires_claude_code: false
min_plan: starter
owns:
  directories: []
  patterns: []
  shared_read: ["*"]
allowed-tools: ["Read", "Grep", "Glob"]
composes_with: ["maintain-context"]
spawned_by: []
---

# zoom-out

Go up a layer. Map the modules involved in this change. Read the domain glossary (`CONTEXT.md`, configured via `setup-project-skills`) if one exists.

Output a numbered list of modules, one line per module describing its role, with arrows (`→`) showing connections between them. Example shape:

```text
1. AuthService — validates JWTs → 2. UserRepo
2. UserRepo — loads/persists users → 3. SessionStore
3. SessionStore — refresh-token cache → AuthService
```

Do not propose changes. The user asked for orientation, not a fix — if they wanted a fix they'd have invoked a different skill.