Govern agent instructions, Skills, Plugins, MCP servers, ownership, and rollout.
Key takeaways
When AGENTS.md, Skills, Plugins, and MCP servers shape agent behavior, documentation culture becomes governance.
Assign an owner and reviewer to every surface and set risk levels, with high-risk surfaces like Plugins and MCP servers requiring security review.
Encode a change policy where each surface has a required reviewer and destructive Tools or OpenAPI breaking changes get separate approval or migration notes.
Roll out in phases (baseline rules, then API/runbook/KB contracts, then Skills/MCP checks, then Plugins/governance) instead of a big-bang migration.
Measure ROI against a local baseline (agent rework, onboarding time, MTTR, breaking changes caught, freshness, blocked destructive actions) and avoid inflated claims.
In agentic documentation, culture becomes governance. If AGENTS.md, Skills, Plugins, and MCP
servers influence agent behavior, teams need ownership, review rules, and retirement policies.