documentation-currency

What problem does it solve?

Documentation often becomes stale, with outdated status markers, old "TODOs," and "coming soon" claims that are no longer relevant. This erodes trust and wastes developer time. This skill identifies and flags these issues, ensuring your project's knowledge base is always current.

Core Features & Use Cases

• Stale Status Detection: Flags "CRITICAL ISSUE" markers for problems that have been solved or "TODOs" for features that have already been implemented.
• Version Lag Analysis: Identifies documentation referencing significantly older software versions compared to the current codebase.
• "Coming Soon" Verification: Checks if promised features are implemented, cancelled, or genuinely still in active progress by analyzing code and commit history.
• Use Case: Schedule this skill to run monthly to get a report on all stale documentation, ensuring your project's README.md and guides always reflect the current state of the software.
• Use Case: Automatically update "Last Updated" dates in documentation to match the actual Git commit history, maintaining accuracy without manual effort.

Quick Start

This skill is typically auto-invoked as part of a larger workflow.

To manually trigger a documentation currency report:

/align-project

(Select Phase 3: Documentation currency from the options presented)