unified-docs

To audit project documentation for outdated files, run a full corpus health check that validates frontmatter schemas, identifies broken dependency links, and flags non-compliant doc types. This provides automated documentation health validation across the entire repository.

Enforcing consistent frontmatter metadata schemas for specs and ADRs requires applying built-in doc type contracts during creation and maintenance. The system validates required metadata fields against strict schemas to ensure every document follows team standards.

Tracking cascade dependencies between how-to guides and explanations involves mapping depends-on and updates relationships within the doc graph. The system automatically flags broken links to archived content and provides repair guidance to keep relationships accurate.

Yes, you can generate a structured implementation plan with gate conditions for a new feature using the plan creation workflow. This enforces correct lifecycle rules and frontmatter schemas from the start, ensuring the plan complies with project documentation standards.

Documentation lifecycle management works for TIL notes and plan documents by applying enforced doc type rules. It ensures these specific document types follow correct lifecycles, maintain accurate frontmatter, and integrate properly into the cascade dependency graph.

Documentation dependencies break when archiving or superseding old specs because downstream documents still reference the outdated content. The audit mode detects these broken links in the cascade dependency graph and provides repair guidance to update or remove the invalid references.