freshness-check

To find stale documentation and broken references, scan product-development and team files to classify content by age tier and surface missing cross-reference targets. This identifies outdated files and should-have-updated signals by comparing modification history against feature-index expectations.

Documentation freshness scanning classifies files into age tiers like Aging, Stale, and Archive candidate to maintain knowledge base hygiene. You need it during scheduled maintenance, onboarding cleanup, and pre-planning to ensure team documentation is current before people rely on it for decisions.

Yes, you can exclude stable files and directories from stale file detection using configured stable-reference exceptions and a .freshness-ignore file. This targeted exception handling ensures the freshness scan only flags relevant product-development and team files that require updates.

Detect should-have-updated documents by comparing file modification history against feature-index.yaml expectations. This flags metrics or docs that lag behind shipped features, producing signals that help teams keep their knowledge base accurate and aligned with recent product development.

No, the freshness check does not automatically delete or archive stale files. It operates with guardrails that ensure the tool only flags issues and routes ownership attribution using the team roster, leaving all deletion and archiving decisions to the team.