how

Files (3)

• SKILL.md
• explainer-prompt.md · references/
• explorer-prompt.md · references/

SKILL.md (first lines)

# How

Follow the [portable runtime contract](../pstack-omp/references/runtime.md) for explorer and synthesizer roles, model choices, and host fallbacks.

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.

Every child is read-only. Explorers use the `how explorer` line in the portable pstack configuration (`$PSTACK_CONFIG`, else `.pstack/config.md`), default role `explorer`. Every explainer uses the `how explainer` line, default role `synthesizer`. Use that line's value, or the default role if the configuration or the line is missing. An `auto` or `inherit-parent` value runs the child on the parent chat model, with no explicit model choice. If the host task runner rejects a configured choice, use the default role and say so. If it rejects the default, use the closest live role the host exposes.

## 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. Spawn one explainer that explores and explains in one pass, built from `references/explainer-prompt.md` without the explorer-findings section. Go to step 4.
- **Complex** (a subsystem spanning multiple files or services, a cross-cutting feature, a full architectural overview): go to step 2.

When in doubt, take the simple path.

## 2. Explore (complex only)

Decompose the question into 2 to 4 angles, each a distinct slice of the subsystem. Launch all explorers concurrently through the host's task facility, each with a standalone brief built from `references/explorer-prompt.md` and its angle filled in.

## 3. Synthesize (complex only)

Once all explorers have returned, spawn one explainer with `references/explainer-prompt.md` and every explorer's findings filled in.

## 4. Present

Present the explainer's output. 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.

From weiihann/pstack-omp, MIT.

More from weiihann/pstack-omp