AGENT SKILL

how

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.

License 许可
MIT
最近更新
2026-11-04
Stars
★ 0
Forks
0

01 前言 Front Matter

name
how
description
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.

02 资源文件 2

03 SKILL.md 正文

How

Explore the codebase to answer "how does X work?" questions. Produce architectural explanations at the level of a senior engineer onboarding onto a subsystem, enough to build a working mental model, not so much that it reads like annotated source code.

Dispatch contract. Resolve every configured role through provider-dispatch.md. Values are Routes written as [provider:]model@effort. On Codex, resolve remaining Claude tool names via codex-tools.md.

Each spawn below names a role line in the active model sheet (see t3-tools.md) and a default. Use that line's value, or the default if the sheet or the line is missing. Leave the Route unset when the value is auto or inherit-parent.

Step 1. Assess Complexity

If the scope is ambiguous, state your interpretation and explore. The user can redirect.

  • Simple (a single module, a small utility, a narrow question such as "how does function X work"): no explorers. One explainer explores and explains in a single pass. Go to Step 2b.
  • Complex (a subsystem spanning multiple files or services, a cross-cutting feature, a full architectural overview): spawn parallel explorers first, then hand off to the explainer. Go to Step 2a.

When in doubt, take the simple path.

Step 2a. Explore (complex questions only)

Decompose the question into 2 to 4 exploration angles, each a distinct slice of the subsystem. Start all explorers in one fan-out phase through provider dispatch. Use the how explorer line (default inherit-parent) in read-only mode.

Each explorer gets the prompt in references/explorer-prompt.md with its angle filled in. Then go to Step 3.

Step 2b. Direct Explain (simple questions)

Dispatch one read-only lane that explores and explains in one pass using the how explainer line (default inherit-parent).

Build its prompt from references/explainer-prompt.md without the explorer-findings section. Go to Step 4.

Step 3. Synthesize (complex questions only)

Once all explorers have returned, dispatch one read-only lane to synthesize their findings into one explanation using the how explainer line (default inherit-parent).

Build its prompt from references/explainer-prompt.md with every explorer's findings filled in.

Step 4. Present

Present the explainer's output to the user. Light edits for clarity or context from the conversation are fine. Do not substantially rewrite it.

Output Format

The explanation uses the sections defined in references/explainer-prompt.md, dropping any that do not apply: Overview, Key Concepts, How It Works, Where Things Live, Gotchas.

04 同仓库更多 Skills