agentleFS
LucasDuysLucasDuys/forge/docs/agents.md

forge

AGENTS.md56 starsChanged 8 months agoMITView on GitHub

The separation between agents is deliberate. The reviewer has fresh context and no implementation bias. The verifier never sees execution details, only checks outcomes against the spec. Three skills are inlined into agent definitions and run automatically. No manual invocation required. All three degrade gracefully. If no graph or DESIGN.md exists, agents behave exactly as before v0.2.0.

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    All three degrade gracefully.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 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

Seven Specialized Agents

AgentRoleMin ModelKey Constraint
forge-speccerWrites R-numbered specs with testable criteriasonnetOne question at a time, capability-aware criteria
forge-plannerDecomposes specs into streaming DAGssonnetCoverage verification, no gold-plating
forge-executorImplements tasks with TDD + convention inferencehaikuWorktree + checkpoints, follow existing patterns
forge-researcherMulti-source research before implementationhaikuProduces reports only, never writes code
forge-reviewerTwo-pass review: spec compliance + blast radiussonnetCaveman for minor, verbose for security
forge-verifierFour-level goal-backward verificationsonnetCaveman for pass, verbose for gaps
forge-complexityScores task difficulty across 5 dimensionshaikuLightweight, runs on every command startup

The separation between agents is deliberate. The reviewer has fresh context and no implementation bias. The verifier never sees execution details, only checks outcomes against the spec.

Cross-Cutting Skills (v0.2.0)

Three skills are inlined into agent definitions and run automatically. No manual invocation required.

SkillUsed ByBehavior
karpathy-guardrailsexecutor, reviewer, plannerFour behavioral principles: Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution. Executor self-checks; reviewer flags violations as IMPORTANT.
graphify-integrationplanner, researcher, reviewer, executorAuto-detected via graphify-out/graph.json. Planner aligns tasks with community clusters. Researcher queries graph before external docs. Executor gets focused context.
design-systembrainstorming, planner, executor, reviewerAuto-detected via DESIGN.md. Planner tags UI tasks. Executor loads design tokens. Reviewer runs design compliance pass.

All three degrade gracefully. If no graph or DESIGN.md exists, agents behave exactly as before v0.2.0.

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.