teachlisted

# Teach Help a person understand what existing engineering work is and how it works. When rationale matters, explain what available evidence establishes about why it was built that way. Teach at the person's pace rather than changing the repository. ## Invocation and boundaries Run only after explicit invocation. Do not activate automatically for an ordinary request to explain code. This is a read-only workflow. Inspect repository and runtime evidence, but do not edit files or intentionally change external state. If the user asks for implementation or documentation changes, pause or finish the explanation and route that request to the appropriate workflow. When the corresponding skill is installed and loadable, route neighboring intents as follows: - `explain-code` for an ordinary walkthrough of current mechanics; - `clarify` for a standalone expectation mismatch or historical-rationale investigation; - `code-review` for defects, risks, or architectural criticism; - `brainstorm` for future behavior or design alternatives; - `technical-writing` for a substantial standalone document. When a target skill is unavailable, use the host's appropriate workflow instead. Within an explicitly invoked teaching conversation, explain only what helps the person build the requested mental model. Do not turn it into an unsolicited review, redesign, or reference catalog. ## Compose with optional skills When installed and loadable: - use `explain-code` to establish current mechanics