AGENTS.md template
Start from an AGENTS.md template, then upgrade it into memory you can review: RAAV syncs agent rules and adds a review queue, swimlanes, and audit trail.
An AGENTS.md template is a good start, but a flat rules file cannot separate confirmed facts from assumptions, show who is editing what, or record verification.
RAAV keeps AGENTS.md as the short instruction sheet it should be, then backs it with current project state. Agents get rules plus scoped work; founders get proposals, ownership, and run history.
An AGENTS.md or CLAUDE.md gives the agent baseline instructions. RAAV keeps that file and adds the changing project state a founder needs to review.
A useful AGENTS.md covers project setup, coding conventions, test commands, and the rules for claiming files and submitting verification.
RAAV generates and syncs these rules across AGENTS.md, CLAUDE.md, Cursor rules, and Copilot instructions so every agent follows the same protocol.
A flat AGENTS.md changes silently and hides assumptions. RAAV separates confirmed facts from inferred ones and routes changes through a review queue.
Stable instructions can stay in AGENTS.md while product changes wait in a founder review queue.
Swimlanes and claims show which agent is applying the rules now. Submitted work records what changed and which checks passed.
The template is where you start; reviewable memory is where you end up.
RAAV does not replace your coding agent. It gives the agent a durable operating system for product truth, task ownership, and proof.
RAAV writes an AGENTS.md and matching rules for your agents.
The same operating rules land in CLAUDE.md, Cursor, and Copilot files.
Agents read memory, claim files, and submit verification.
The founder supervises via the review queue and audit trail.
Ask your agent to install RAAV and generate the AGENTS.md for you. You get synced rules plus a review queue, swimlanes, and audit.
Install RAAV in this repo and generate an AGENTS.md template. Sync the operating rules across CLAUDE.md and Cursor, and make agents claim files and submit verification as part of those rules.AGENTS.md remains the instruction file. RAAV records the changing work and decisions around it.
Most tools either write code or track human tickets. RAAV sits between the founder and the coding agents as shared product memory, coordination, and audit.
Founders ask whether they still need an AGENTS.md if they use RAAV.
Yes, and RAAV generates and syncs it. The file is real memory your agents read. RAAV adds the review queue, swimlanes, and audit that a flat file cannot provide.
RAAV syncs operating rules across agent files while keeping your project-specific content. The point is one consistent protocol across agents.
No. RAAV prepares and maintains the context files that Codex, Claude Code, Cursor, and Copilot read.
The Trial is €10/week. The plan includes the local instruction workflow and a hosted founder console; invitations are still released in small cohorts.