Summary

drivers-evergreen-tools has no agent-facing documentation, so coding agents (and new contributors) can't discover repo structure, prerequisites, or the make install/make lint workflow (added in DRIVERS-3590) before making a change.

Motivation

Who is the affected end user?

Coding agents and contributors working in drivers-evergreen-tools.

How does this affect the end user?

Without a documented entry point, they don't know which command validates a change, or where to find repo conventions, testing approach, and PR requirements — leading to wasted time or skipped validation.

How likely is it that this problem or use case will occur?

Main path — every change to the repo needs this.

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance: wrong commands, wasted iteration, or PRs opened without local validation.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

No — documentation and tooling discoverability.

Acceptance Criteria

• A new AGENTS.md documents repo structure, prerequisites, execution, testing, the make install/make lint pre-commit workflow, conventions, and PR requirements.
• A new CLAUDE.md points agents to AGENTS.md as the source of truth.

Implementation plan: https://gist.github.com/blink1073/ac2a810e43b7e14090b3357abad91faa