Global Documentation

This skill acts as a specialized quality assurance mechanism for technical documentation, providing the agent with strict adherence protocols based on defined repository standards. It is intended for software engineers, technical writers, and AI agents managing large codebases who need to ensure that project-level documentation, architectural specs, and development guides remain synchronized with global standards. By utilizing this skill, the agent cross-references local edits against the central documentation directives, preventing formatting drift and ensuring that README files, architectural manifests, and technical specs follow the organization's established structural guidelines.

• Validates technical documentation against mandatory global coding and style standards.

• Monitors consistency between individual module READMEs and central documentation folders.

• Facilitates automated reviews of architectural specifications (e.g., architecture-refactoring/spec.md) to ensure compliance with project-wide requirements.

• Provides context-aware guidance for documentation updates, ensuring that new files are tagged and cross-linked correctly.

• Supports integration with agent-os/standards/global/documentation.md for live rule evaluation during the editing process.

• Use this skill whenever you are modifying, creating, or auditing documentation files within the repository to ensure they meet mandatory structural rules.

• Input expected: Markdown documentation files or specification manifests. Output: Compliance checks, structural suggestions, and standardized formatting adjustments.

• Constraints: The skill relies on the presence of the agent-os/standards/global/documentation.md file; ensure this path is accessible in your environment.

• Best practice: Always invoke this skill before finalizing pull requests or major updates to technical specs to verify that global cross-references are valid and that formatting follows the organizational template.

• Applicable to technical ecosystems including Go backends, CLI-first issue trackers like Beads, and complex architecture refactoring documentation.