agentleFS
Sign inStart free
docxologydocxology/codomyrmex/.agents/skills/systems-thinking/AGENTS.md

codomyrmex / systems-thinking

AGENTS.md10 starsChanged 38 days agoMITView on GitHub

Portable repository-scoped skill: Analyze a change as part of a wider system: boundaries, dependencies, feedback loops, delays, incentives, leverage points. Defined entirely by SKILL.md. - SKILL.md — canonical definition: frontmatter (name: systems-thinking, description), a six-step workflow (boundary and owners → stocks, flows, and state transitions → dependencies and feedback loops → second-order effects → high-leverage interventions → indicators, guardrails, and rollback), and the required output (causal map or table, intervention, downstream effects, risks, measurements). - README.md — human signpost. -…

The file

We split this AGENTS.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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. Distinctive:

    Use when a local change may alter behavior elsewhere in the system.

    line 31
  2. Very specific:

    Keep name equal to the folder name.

    line 34
  3. Distinctive:

    Keep the output contract concrete (a causal map or table plus measurements) so reviewers can check it rather than accept narrative.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

AGENTS.md — codomyrmex/.agents/skills/systems-thinking

Purpose

Portable repository-scoped skill: Analyze a change as part of a wider system: boundaries, dependencies, feedback loops, delays, incentives, leverage points. Defined entirely by SKILL.md.

Key Files

  • SKILL.md — canonical definition: frontmatter (name: systems-thinking, description), a six-step workflow (boundary and owners → stocks, flows, and state transitions → dependencies and feedback loops → second-order effects → high-leverage interventions → indicators, guardrails, and rollback), and the required output (causal map or table, intervention, downstream effects, risks, measurements).
  • README.md — human signpost.

Dependencies

  • Claude Code wrapper: .claude/skills/systems-thinking/SKILL.md only points back to this file.
  • Second step of the composition order in docs/agents/agent-interoperability.md: it consumes the first-principles decision record and hands its causal map to red-team.
  • Parent: ../AGENTS.md

Development Guidelines

  • Use when a local change may alter behavior elsewhere in the system.
  • This is the canonical copy; runtime wrappers such as .claude/skills/systems-thinking/ stay pointers — change the workflow here.
  • Keep name equal to the folder name; a rename must also update the wrapper, .agent/SKILL_INDEX.md, and the interoperability doc.
  • Keep the output contract concrete (a causal map or table plus measurements) so reviewers can check it rather than accept narrative.

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