Roadmap Auditor

To verify roadmap progress claims, audit progress statements in files like README.md and CHANGELOG.md against the actual state of the codebase and checkpoint files. This identifies mismatches and confirms evidence for completed items, catching inaccurate status updates.

Auditing project documentation for unverified claims involves comparing stated progress in files like .github/PROJECT_*.md against tangible code and test evidence. This mismatch identification process prevents misleading status updates before closing a project milestone.

Yes, you can check if completed features have corresponding tests by comparing roadmap claims in documentation against actual code and test evidence. This verification process identifies discrepancies where features are marked completed but lack implementation or test proof.

Evidence-based verification for project milestones works by comparing roadmap progress statements against tangible evidence in the codebase. It verifies evidence for completed items and identifies unverified or contradictory claims by checking the actual state of the codebase and checkpoint files.

You should audit your roadmap to prevent misleading status updates before closing a project milestone. This confirms that all features marked as completed are indeed implemented, tested, and documented, catching potential oversights or inaccuracies in progress statements.

Your roadmap status may contradict the actual codebase state due to unverified or contradictory claims. Auditing compares progress statements in README.md and CHANGELOG.md against code, tests, and checkpoint files to identify these mismatches and prevent inaccurate documentation.