agent-docs-maintainer

To clean up bloated CLAUDE.md and AGENTS.md files, audit them to detect bloat, spot stale project names, and identify duplicated managed blocks, then rewrite the agent docs to keep only essential routing rules and project facts while moving deep details into skills or references.

Agent docs often grow into stale command manuals because command references and archived notes accumulate over time. Replacing copied command manuals with concise skill-or-help pointers keeps the documentation compact, current, and routing-oriented for agents.

The best way to maintain compact instruction templates for GitNexus workflows is to generate agent guides that preserve only essential workflow routing, project maps, gotchas, and validation hooks, ensuring support for xtrm, beads, and specialists without turning the file into a manual.

Yes, you can rewrite agent documentation while preserving managed blocks. The rewriting process requires managed-block preservation, ensuring only the essential rules and workflow routing remain intact while stale terms and bloat are cleaned up.

Yes, this approach works directly with repositories using beads, specialists, or GitNexus workflows. It audits and rewrites xtrm instruction templates, CLAUDE.md, and AGENTS.md to keep them short, accurate, and routing-oriented for these specific environments.

You should not keep deep command details inside AGENTS.md when they bloat the file and make it hard to trust at session start. Moving deep details into skills, references, or docs and replacing them with concise pointers keeps the agent guide current and compact.