Skip to content

AI readiness

The map for making a repository safe and usable for coding agents.

Updated View as MarkdownView on Github

This section covers repositories used with coding agents. It does not cover AI-powered product features or model selection.

Agent instructions is the enforceable baseline for repository instruction files. Repository context adds the context code cannot provide. Development environment requires a reproducible path from a clean clone to a verified local environment. AI change workflow adds the stacking rule for agent-opened pull requests. The remaining pages in this section map standards that are not yet written and create no requirement yet.

Readiness areas

  • Agent instructions defines where repository rules live and how tools discover them.
  • Consult the standards sets up AGENTS.md so agents read these standards before they act on anything they cover.
  • Repository context requires a repository to surface its invariants and make its published contracts and consumers discoverable.
  • Development environment requires checked-in tool resolution, clean setup, declared dependencies, and a safe reset.
  • Task automation covers the commands agents use to build, check, test, and inspect a repository.
  • Tools and integrations covers approved assistants, command-line tools, connectors, and tool configuration.
  • Testing and feedback covers fast checks, deterministic results, and useful failure output.
  • Security and data covers secrets, permissions, sensitive data, and untrusted input.
  • AI change workflow covers task intake, review, handoff, and human accountability.
  • AI maintenance covers ownership, freshness, and measuring where agents still get stuck.

Boundary with existing standards

AI-assisted changes follow the same quality gates, four-eyes review, security, and code ownership standards as any other change. The AI section documents the repository work needed to apply those standards when a coding agent participates.

When a page in this section becomes a standard, it asserts only the gaps the existing standards leave open and points to them for the rest. It does not restate a requirement that already has a home. Much of what a coding agent needs is already covered by Agent instructions, so a new page is often thin by design.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close