agentleFS
mtarcuremtarcure/claude-vibe-squad/.agents/skills/layered-analysis-loop/SKILL.md

layered-analysis-loop

Skill220 starsChanged 17 days agoMITView on GitHub

Use when analyzing a target deeply enough to require distinct structural, behavioral, edge-case, and contradiction passes rather than one undirected read—fix a question for each layer, record its evidence-backed delta, and stop only at a no-delta layer or an explicit budget cutoff.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the question each layer will answer before starting it.

    line 12
  2. Distinctive:

    Run layer 1 for structure only: what exists, how it is organized, where the entry points are.

    line 13
  3. Distinctive:

    Run layer 2 for behavior: follow the primary paths end to end and record what actually happens, in order.

    line 14
  4. Distinctive:

    Run layer 3 for edges: error paths, empty and boundary inputs, concurrency, and the states the primary path assumes but does not enforce.

    line 15
  5. Distinctive:

    Run layer 4 for contradiction: actively try to falsify the model built by layers 1-3.

    line 16
  6. Distinctive:

    Stop when a full layer produces no delta, and say so.

    line 18
  7. Distinctive:

    Every layer closes with an explicit delta, including "no change".

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Layered Analysis Loop

Analyze in deliberate passes that each answer one question, so depth accumulates on a stable base instead of one undirected read producing a shallow summary.

Steps

  1. Write the question each layer will answer before starting it. A layer without a question becomes a re-read.
  2. Run layer 1 for structure only: what exists, how it is organized, where the entry points are. Resist diagnosing anything yet.
  3. Run layer 2 for behavior: follow the primary paths end to end and record what actually happens, in order.
  4. Run layer 3 for edges: error paths, empty and boundary inputs, concurrency, and the states the primary path assumes but does not enforce.
  5. Run layer 4 for contradiction: actively try to falsify the model built by layers 1-3. Look for the case that breaks it rather than the case that confirms it.
  6. Close each layer with a written delta — what changed in the model — and carry forward only findings with evidence. An unrecorded layer did not happen.
  7. Stop when a full layer produces no delta, and say so. Continuing past convergence spends budget; stopping before it ships an untested model.
  8. Report the layers run, the delta from each, and the layer at which convergence occurred.

Acceptance

  • Each layer has a written question fixed before the layer ran.
  • Structure, behavior, edge, and contradiction layers are separately recorded.
  • Every layer closes with an explicit delta, including "no change".
  • The contradiction layer names at least one specific attempt to falsify the model.
  • The stopping condition is stated as convergence or as an explicit budget cutoff.

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.