What problem does it solve? Engineers often need to understand an unfamiliar change, subsystem, or codebase quickly, but raw code reading and documentation dumps rarely produce real understanding. This Skill turns a body of work into a plain, paced explanation that builds genuine comprehension. ## Core Features & Use Cases - Orchestrated explanation: Runs the how and why skills in parallel and weaves their findings into one coherent account of what something is, how it works, and why it is built that way. - Audience-calibrated depth: Chooses what to teach based on why the person is asking (reviewing, debugging, onboarding) and what they already know, keeping answers short first and going deeper on request. - Progressive diagrams: Builds understanding with a series of diagrams that each add one part, using mermaid for flows and generated whiteboard-style images for spatial ideas. - Use Case: A developer joins a team and asks "help me really understand the chat virtualization subsystem." The Skill runs how and why, then delivers a plain explanation starting with a one-sentence definition and building up mechanism by mechanism. ## Quick Start Ask the agent to teach you how a specific subsystem or recent change works and why it was built that way.
