What problem does it solve? When you encounter an unfamiliar section of a codebase, it is hard to understand how it fits into the bigger picture. This Skill lifts the analysis up a layer of abstraction and produces a structured, map-first explanation of the relevant modules, their relationships, and the risks involved. ## Core Features & Use Cases - Map-First Architecture Answers: Produces a structured overview covering modules/layers, relationships, critical paths, and risks/gaps using the project's own glossary vocabulary. - Impact Analysis: Separates structural impact (imports, callers, containment, type usage) from observed impact (prior worker history, retries, co-changed files) when the focused area is a likely change target. - Optional Memory Graph Integration: Opportunistically folds in Memory recall, graph neighbors, and path queries when available, degrading cleanly to ordinary code reading when they are not. - Use Case: You are about to modify a service you have never touched. Ask for a zoom-out on that module to get its responsibilities, callers, impact surface, and change hazards before writing any code. ## Quick Start Ask the agent to zoom out and explain how the authentication module fits into the overall codebase architecture.
