mcaf-documentation
Apply MCAF documentation guidance for docs structure, navigation, source-of-truth placement, and writing quality. USE FOR: docs are missing, stale, duplicated, or hard to navigate; a repo needs a cleaner source-of-truth structure; durable engineering guidance needs to be added without. DO NOT USE FOR: writing a specific feature spec or ADR when that skill already fits; dumping large template content into public pages. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.