docs-maintenance

Documentation maintenance ensures cross-references and shared conventions match actual files. You update README enumerations, workflow routing, and skill documentation to fix broken Markdown links and anchor mismatches, keeping repository discovery accurate.

Auditing Markdown links and workflow listings requires running a docs inventory script to scan the repository. This generates a report of mismatched cross-references and outdated workflow routing, which you repair while preserving workflow semantics.

To update workflow routing and README entries without breaking semantics, follow a documented maintenance checklist to apply only documentation-scoped changes. This updates installable skill documentation and library load references while leaving underlying workflow logic untouched.

Yes, this approach fixes heading anchors and duplicate phrasing across Markdown files. It enforces cross-file consistency by repairing shared references and standardizing terminology, ensuring that routing and discovery assets remain structurally aligned.

Outdated workflow listings and stale library references mislead users because they create a gap between documented assets and actual repository structure. Systematic documentation maintenance closes this gap by aligning cross-references and shared conventions with real files.

You should run a repository documentation audit whenever you add, rename, or remove workflow files to prevent expired references. Running the docs inventory script validates that Markdown links and skill documentation match the current file structure.