What problem does it solve? Planning documents like roadmaps, TODO files, and milestone trackers drift out of sync with the actual codebase as work progresses, leaving teams unsure what is truly finished, blocked, or obsolete. ## Core Features & Use Cases - Evidence-Based Status Verification: Assigns each planned item a status (complete, partial, blocked, stale, obsolete, unverified, undocumented) based on tests, source code, and integration evidence rather than checkboxes. - Plan Drift Detection: Identifies incorrect completion claims, stale items, conflicting planning documents, and undocumented implementation work. - Corrected Execution Sequence: Produces a prioritized list of three to seven next tasks with dependencies, acceptance criteria, and validation methods. - Use Case: After several weeks of incremental development, ask the agent to check your ROADMAP.md against the repository to learn which milestones are genuinely complete and what should be implemented next. ## Quick Start Ask the agent to reconcile the project roadmap with the current repository state and report what is actually finished and what to work on next.