legibility--auditor

To audit repository documentation for agent readiness, evaluate AGENTS.md placement, progressive disclosure quality, and UX intent documentation to produce a comprehensive Legibility Audit Report detailing findings and remediation steps.

Repo legibility is the measure of how easily autonomous agents can navigate a codebase through proper documentation coverage. It matters because clear AGENTS.md guidance and documented UX intent enable robust onboarding and autonomous operation.

Check AGENTS.md configuration by auditing root and path-specific guidance across subdirectories. The audit surfaces gaps in progressive disclosure and identifies where local AGENTS.md files are needed to support agent onboarding.

Yes, the agent readiness audit evaluates path-specific guidance across subdirectories to surface hidden assumptions impacting agent navigation. It aligns documentation with agent-first practices across the entire onboarding scope.

The best way to surface hidden assumptions impacting agent navigation is to apply a legibility audit to the onboarding scope. This evaluates documentation coverage and checks compliance against the Agent Readiness checklist.

A legibility audit report should include findings on missing files, documentation gaps, risks, and recommended remediation steps. It must detail AGENTS.md placement issues and areas lacking progressive disclosure or UX intent clarity.