What problem does it solve? Keeping technical documentation, AGENTS.md, and CONTRIBUTING.md accurate and consistent across a repository is difficult, especially when docs span multiple frameworks, locales, and agent instruction aliases that drift out of sync. ## Core Features & Use Cases - Build and review playbooks: Classify work as build or review, brownfield or evergreen, then follow structured playbooks covering structure, writing quality, and validation. - Governance and alias management: Inventory AGENTS.md, CONTRIBUTING.md, and alias files like CLAUDE.md or .cursorrules, resolve precedence conflicts, and keep one canonical policy core. - Framework-aware path validation: Verify Fern, Mintlify, and Sphinx configs so referenced files exist and URL routes match source paths. - Use Case: Run a full-repo documentation audit that maps every docs surface, detects broken commands and missing referenced files, applies high-confidence fixes, and returns a prioritized issue report with validation notes. ## Quick Start Ask the agent to review this repository's documentation and AGENTS.md for broken references, conflicting instructions, and structural issues, then apply the safe fixes.
