Individual skill

how

Explain how a part of the codebase works, from trigger to result, at the depth an experienced engineer needs to start changing it. Use for "how does X work", "walk me through Y", "where should this code go", "which layer owns Z".

plugins/requie/endostack/skills/how/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# how

Explain how some part of the codebase works so that an experienced engineer new to the area can build a working mental model and start making changes. Aim for the flow, the actors and the decision points. Line-by-line narration is out of scope.

Run this skill when the user asks for it (`/how` or an explicit request). The [teach](../teach/SKILL.md) skill calls it for the mechanics half of an explanation.

## Questions this skill answers

- How something works, or a walkthrough before an edit.
- Placement and ownership: where new code belongs, which package is responsible for something, whether code sits in the right layer.
- The architecture of a subsystem and its runtime execution flow.
- Building a newcomer's picture of an unfamiliar area.

Questions about motivation or history go to the [why](../why/SKILL.md) skill. Questions about what a change might break go to the [blast-radius](../blast-radius/SKILL.md) skill.