zoom-outlisted

Use this skill when two conditions are met: (1) the user is already mid-session on a technical topic, and (2) they signal a desire to step back and reconnect with human impact, business outcomes, or plain-language tradeoffs. Trigger phrases: "zoom out", "step back", "big picture", "plain terms", "remind me why we're doing this", "what does this mean for users", "what's at stake", "plain english", "without the jargon", "losing the forest for the trees", "what are we actually deciding", "eli5 what we're trading off", "lost the thread". Do NOT trigger for: standalone learning questions with no prior session context, fresh architecture comparisons, document summarization, code review, or general "explain X to me" requests.
RobertGumeny/skills · ★ 0 · AI & Automation · score 75

Install: claude install-skill RobertGumeny/skills

# Zoom Out Skill ## Purpose Help the user escape deep technical weeds mid-session and reorient around what actually matters — who is affected, what outcomes are at stake, and what the real tradeoffs are — before returning cleanly to the decisions at hand. **Three-phase flow:** 1. **Breadcrumb** — snapshot where we are 2. **Zoom Out** — explain through three lenses 3. **Zoom Back In** — ask which thread to pick up first --- ## Step 0: Load the Right Reference File Before executing the three-phase flow, identify the domain of the current discussion and load the corresponding reference file. Reference files contain domain-specific personas, common tradeoffs, and an example zoom-out to guide your output. ### Domain Detection Infer from context first. If ambiguous, ask before proceeding. | Domain | Reference File | Signals | |---|---|---| | Software architecture & system design | `references/architecture.md` | Services, APIs, databases, scaling, infra, queues, caching | | Product & feature planning | `references/product-planning.md` | User flows, roadmap, specs, requirements, stakeholders, prioritization | | Data modeling & API design | `references/data-api.md` | Schemas, endpoints, contracts, data relationships, versioning | | DevOps / infra / cloud | `references/devops-infra.md` | Deployments, pipelines, environments, reliability, cost, containers | **If the session spans multiple domains**, load the file that best matches the *current decision being discussed*, not th