zoom-out · v1.1.3 · 2026-10-30 · sha256 315974624356c276
zoom-out v1.1.3A
Immutable. This exact content never changes and is served at /api/v1/blob/315974624356c276.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_teu4scf32hfwwqj7/315974624356c2762094be06ca8cb4963db6304366c15bebbae164d57814c5ee.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.3 description: >- Step back from the code to show which modules a change touches, how they connect, and what it affects that isn't obvious, using CONTEXT.md when present. Use before a structural decision or when a change feels bigger than expected. Trigger on "zoom out", "step back", "give me the big picture", "what else does this touch?". 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.