repo-docs

Repo docs

Make the maintained documentation agree with what the project actually does, make its development instructions usable by each intended host, and give a project one documentation policy to follow.

Argument: $ARGUMENTS. If the host leaves it literal, read the request instead. audit, a review request, an explicit no-edit instruction, or the command alone with no argument and no request beside it means report only: nothing is written in the project, and a report is saved only as the reconciliation's step 4 allows. fix, or an explicit reconciliation or cleanup request in the owner's words, authorizes ordinary in-scope documentation fixes. Resolve an ambiguous request as an audit, and end an audit by naming fix as the way to apply its ordinary fixes. maintain runs the maintenance step first and edits nothing until the owner approves a group of its proposals. adopt edits nothing until the owner approves the files it shows. readme, or a request about one README, works on that README alone. A request to write one page for people authorizes writing that page and works on it alone; a request to review one reports on that page alone. A path narrows the pass to that area plus its incoming references; state that boundary.

On Claude Code invoke /anneal:repo-docs; on Codex use $repo-docs; on Antigravity use /repo-docs. Find the plugin files through ${CLAUDE_PLUGIN_ROOT} on Claude Code, or resolve ../../ from this file on other hosts. Resolve target paths against the project root, never the installed plugin directory.

On Antigravity, give every command the project root the person named as its working directory, the Cwd of run_command. Without it, commands can run in Antigravity's own scratch directory instead of the project. When the person named no project root, ask for it before running anything.

Modes

Every mode reads the Invariants section of the documentation contract first, and treats the project's own applicable instructions as its documentation policy.