how
Use for "how does X work", code walkthroughs, and placement, ownership, or layering questions. Explains subsystem architecture, runtime flow, and onboarding mental models.
- License 许可
- MIT
- 所属仓库
- syanga/astack
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- how
- description
- Use for "how does X work", code walkthroughs, and placement, ownership, or layering questions. Explains subsystem architecture, runtime flow, and onboarding mental models.
- disable-model-invocation
- true
02 资源文件 3
- 许可证LICENSE1.0 KB
- 参考文档references/explainer-prompt.md2.9 KB
- 参考文档references/explorer-prompt.md2.5 KB
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.
Use the available subagent tool for the steps below. All exploration and explanation is read-only. If subagents are unavailable, perform those steps directly.
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. Spawn the explorers in parallel.
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)
Spawn one subagent that explores and explains in one pass.
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, spawn one subagent to synthesize their findings into one explanation.
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
replace-with-skill-name
Replace with when this skill should be reached.
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
worktree-cleanup
Worktree cleanup. Use for cleanup, resource audits, close this lane, or close out.
wizard
Generate an interactive Bash wizard that walks a human through steps only they can perform. Use when provisioning, credential setup, or a one-off migration needs such steps.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Returns a cited read on decisions and tradeoffs.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.