agents-md-maintainer

Use this skill after nontrivial implementation work and before finalizing when you need to decide whether AGENTS.md should change.

Rules

• Treat AGENTS.md as durable repo guidance, not a task log.
• Run a brief AGENTS.md maintenance pass at the end of implementation.
• Do not modify AGENTS.md unless the implemented code, tests, and docs state already proves the new rule.
• Update AGENTS.md only for durable repo-wide guidance such as:
  • required build, test, lint, typecheck, or verification commands
  • architecture invariants or hard constraints
  • canonical data shapes, contracts, directory ownership, or file locations
  • repo-wide coding, review, or release expectations
  • recurring failure modes that future sessions must avoid
• Do not update AGENTS.md for one-off feature details, branch context, temporary migrations, issue notes, task plans, historical summaries, or implementation narration.
• Keep edits minimal and high-signal. Prefer replacing, tightening, deduplicating, or deleting existing bullets over appending prose.
• Keep AGENTS.md clean, concise, and production-facing.
• Do not include working-session phrasing such as Phase, plan, follow-up, or similar developer-tracking language.
• Write rules as short, concrete, imperative bullets that a coding agent can apply immediately in a new session with no prior chat context.
• Keep root AGENTS.md limited to broadly applicable guidance. Put scoped rules in the nearest folder-level AGENTS.md. Put reusable workflows in skills or referenced docs.