agentleFS
Sign inStart free
christofferbergjchristofferbergj/agent-skills/skills/planning/how/SKILL.md

how

Skill1 starsChanged 23 days agoMITView on GitHub

Use for Pstack code walkthroughs, subsystem behavior, or module placement and ownership questions.

90 other projects use a version of this, 49 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-pstack and poteto-help.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 25 projects that use this

  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 14 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 89 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use /swarm for every explorer and explainer.

    line 12
  2. Distinctive:

    When in doubt, take the simple path.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 89 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Invoke /domain-modeling to resolve and read the invoking project's configured artifacts. Read-only investigations and reviews report documentation drift without edits; creation or implementation reconciles accepted model changes through that owner.

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 /swarm for every explorer and explainer; each is read-only. Explorers take the how explorer role and explainers the how explainer role. With no delegation, perform the same passes sequentially and disclose it.

  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 the explainer prompt 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. Complete when the target and the path are explicit.

  2. Explore (complex only). Decompose the question into 2 to 4 angles, each a distinct slice of the subsystem. Spawn all explorers in a single message, each with the explorer prompt and its angle filled in. Complete when each angle returns source pointers, runtime flow, and gaps.
  3. Synthesize (complex only). Once all explorers have returned, spawn one explainer with the explainer prompt and every explorer's findings filled in. Complete when the explanation is supported by inspected code.
  4. Present the explainer's output. Light edits for clarity or context from the conversation are fine. Do not substantially rewrite it. The explanation uses the sections defined in the explainer prompt, dropping any that do not apply: Overview, Key Concepts, How It Works, Where Things Live, Gotchas. Complete when the reader can trace the subsystem and distinguish current behavior from rationale, which belongs to /why.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free