how

Generates architectural explanations of codebases using parallel explorer and explainer subagents.

1|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/edivad1999/stuc-stack --skill how-edivad1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: how
Source: https://github.com/edivad1999/stuc-stack/tree/main/skills/how
Command: npx skills add https://github.com/edivad1999/stuc-stack --skill how-edivad1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Understanding how an unfamiliar subsystem works requires hours of manual code reading, and ad-hoc explanations often miss cross-cutting flows or key abstractions. This Skill answers "how does X work" questions by systematically exploring the codebase and producing a senior-engineer-level architectural explanation. ## Core Features & Use Cases - Complexity Assessment: Routes simple questions to a single-pass explainer and complex subsystem questions to parallel explorers plus a synthesizer. - Parallel Exploration: Spawns 2-4 read-only explorer subagents, each tracing a distinct angle of the subsystem with a structured findings template. - Structured Explanations: Produces explanations with Overview, Key Concepts, How It Works, Where Things Live, and Gotchas sections, including mermaid or ASCII diagrams where useful. - Use Case: Before modifying a payment flow spanning multiple modules, ask how it works and receive a unified walkthrough of entry points, data flow, file locations, and non-obvious behavior. ## Quick Start Ask the agent to explain how the authentication flow works in this repository before making changes to it.

Frequently Asked Questions about how

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an explanation of how a codebase subsystem works?▼

Ask a how-does-X-work question and the Skill assesses complexity, then either explains directly or spawns parallel read-only explorer agents. Their findings are synthesized into a structured explanation covering flow, key concepts, and file locations.

How does the Skill handle simple versus complex architecture questions?▼

Simple questions about a single module or function go to one explainer subagent in a single pass. Complex questions spanning multiple files or services trigger 2-4 parallel explorers whose findings a synthesizer merges into one explanation.

Can the explorers modify my code while investigating?▼

No. All explorer and explainer subagents run with readonly set to true, using only Read, Grep, and Glob. They gather facts and trace code paths without making any changes to the codebase.

What sections does the generated architectural explanation include?▼

Explanations use Overview, Key Concepts, How It Works, Where Things Live, and Gotchas sections, dropping any that do not apply. Diagrams in mermaid or ASCII are included when the flow involves multiple interacting components.

When should I use this instead of asking why something was built?▼

Use this Skill for mechanism questions: how something works, where code should live, and which layer owns logic. For motivation and rationale behind a design decision, the documentation directs you to the separate why skill.