Writing /

Seven practices, each derived from something that runs.

Seven practices for running a fleet of AI coding agents, each derived from a working artifact rather than written as advice. Every page names the file it comes from and, where it counts something, the command that recounts it.

7 practices · Last verified 2026-09-11

  1. The operating manualHow a layered set of CLAUDE.md and AGENTS.md files gives every agent the rules for the directory it is standing in.~/.claude/CLAUDE.md and per-project CLAUDE.md / AGENTS.md
  2. WorktreesWhy every branch gets its own working tree, where they are allowed to live, and the two-line helper that enforces it.~/.claude/rules/project-inventory.md
  3. The fleetHow a 132-line shell script keeps parallel agent sessions findable instead of scattered across terminal tabs.~/.local/bin/work
  4. The session catalogA local Swift daemon that indexes agent transcripts into a read-only catalog and serves six search tools back to the agents that wrote them.~/dev/lodestar/tools/session-catalog
  5. VerificationAn adversarial review layer that attacks findings on four fixed lenses and fails closed when it cannot reach a verdict.~/.claude/agents/verify-depth.md and ~/.claude/workflows/fan-out-verify.js
  6. Eval-gated skillsA loop that edits an agent skill, measures the change against a held-out eval set, and refuses to promote it without a statistical margin and an independent verdict.~/dev/_tools/skillopt
  7. The attention ledgerOne file defines every metric, three reporters read it, and the hardest work was removing the automation from its own numbers.~/dev/METRICS.md