How

Answer "how does X work?" with the mental model a senior would give on day one. Not annotated source.

/why answers why it is this way. /analyze writes the broader memo (a bug, an idea, impact, an execution seed). This skill does not write tickets or code, and it does not start a build. The selected execution skill owns any later build.

The section shape is adapted from poteto's pstack /how (MIT). The steps below are this pack's.

Read when

• About to search the repo or read large files? Open main-context.md. Skip it and the walkthrough drowns in file dumps.
• About to describe layers, ownership, or a public API? Open code-quality.md and code-structure.md. Skip them and the model copies a messy layout.
• About to reply? Open Plain language and Unslop. Skip them and the walkthrough reads like a tour script.
• About to ask the user anything? Open Asking the user. Skip it and you ask what the repo already answers.

Contract