how

Files (3)

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

SKILL.md (first lines)

# How

On Pi, read the [platform mapping](../poteto-mode/references/pi-tools.md), including its per-skill notes, before following this skill.

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.

Each spawn below names a role line in `pstack-models.md` and a default in [Models](#models). Set `model` to that line's value, or to the default if the sheet or the line is missing. Leave `model` unset when the value is `auto` or `inherit-parent`. If the `Agent` tool rejects a slug, use the default and say so. If it rejects the default, use the closest valid slug of the same family from its error message.

## 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 all explorers in a single message:

- `subagent_type`: `pstack-reader` (read-only: no edit or write tools, MCP kept)
- `model`: the `how explorer` line, default in [Models](#models)

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 `Agent` subagent that explores and explains in one pass:

- `subagent_type`: `pstack-reader` (read-only: no edit or write tools, MCP kept)
- `model`: the `how explainer` line, default in [Models](#models)

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 `Agent` subagent to synthesize their findings into one explanation:

- `subagent_type`: `pstack-reader` (read-only: no edit or write tools, MCP kept)
- `model`: the `how explainer` line, default in [Models](#models)

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.

## Models

Role defaults, stamped by pstack-pi's `scripts/sync-pstack.mjs` from upstream `models.json` and the Pi model map in `port.json`. A matching role line in `~/.pi/agent/pstack-models.md` overrides each at runtime; `/pstack:setup-pstack` writes it.

- how explorer: `openai-codex/gpt-6-sol`
- how explainer: `openai-codex/gpt-6-sol`

## Reasoning effort

A role value in the override sheet may name a reasoning effort after its model, as in `openai-codex/gpt-6-sol @xhigh`. Levels on Pi: `low`, `medium`, `high`, `xhigh`, `max`. Which ones apply depends on the model. A value without `@` takes the sheet's `default effort` line, a level or `session`, and `session` when the sheet has no such line. `session` sets no effort, so the dispatch is the usual one. Strip the suffix before reading the model: `inherit-parent` or `auto` still omits `model` at every level, and a model name is passed as `model`. On Pi, pass the level as the `Agent` tool's `thinking` field and keep the usual `subagent_type` and `model`. Pi clamps a level the model does not support.

From proguha/pstack-pi, MIT.

More from proguha/pstack-pi