Agent skill · shipshitdev
how
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.
What it needs
About 2k tokens when loaded.
What this skill does
How Explore the codebase to answer "how does X work?" Produce an architectural explanation at the level of a senior engineer onboarding onto a subsystem. Two modes: 1. Explain (default). Explore and produce a clear explanation. 2. Critique. Explain first, then spawn independent critics. Companion to why. This skill answers what the code does. why answers what forces led to its shape. Contract Inputs: A how-question: subsystem, feature flow, architectural overview, or runtime trace Outputs: The structured explanation below In Critique mode, a lead verdict over critic findings Creates/Modifies: None External Side Effects: None. Read-only exploration. Confirmation Required: None Delegates To: None. May spawn read-only explorer, explainer, and critic subagents. Explain mode Step 1. Understand the question Parse the ask. If ambiguous, state the best-guess interpretation and proceed. Do not ask. Let the user redirect. Simple (one module, a narrow function): skip explorer agents. The explainer explores and explains in one pass. Complex (multiple files or services, a cross-cutting feature): spawn 2-4 parallel explorers, then one explainer. When in doubt, lean simple. Step 2a. Explore (complex only) Decompose into 2-4 distinct slices so explorers do not duplicate work. Spawn all explorers in one message on the fast cheap tier, read-only. Each explorer gets references/explorer-prompt.md plus its slice. Each traces input to output without hand-waving. Step 2b. Direct explain (simple) Spawn one read-only explainer on the strongest judgment tier. It explores and writes the explanation. Use references/explainer-prompt.md. Step 3. Synthesize (complex only) Once explorers return, spawn one explainer on the strongest judgment tier with all findings. It reconciles overlap and contradictions. Step 4. Present Present the explainer's output. Light edits for clarity are fine. Do not substantially rewrite. Output format Overview. 1-2 paragraphs. What it is, what it does, why it exists. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills shipshitdev/how