pm-update-roadmap-tracking

To sync roadmap documentation with codebase implementation, this skill inspects git logs, test results, and product artifacts to reconcile tracking files against the actual state. It identifies documentation drift and automatically updates progress trackers based on verified code changes.

Documentation drift occurs when roadmap tracking documents become disconnected from the actual codebase and approved product specifications. This skill solves drift by detecting discrepancies between implementation plans and repository-level status through evidence-based reconciliation.

To update progress tracking files after feature completion, this skill reconciles the implementation against the PRD and roadmap. It validates status changes using evidence from git logs and test results, ensuring the tracker reflects the new status without manual document auditing.

Yes, you can detect discrepancies between approved product specifications and current implementation reality. This skill operates across project-specific tracking files and implementation plans to identify drift, validating any status changes against evidence from the codebase.

No, you do not need to manually audit repository-level status documents to ensure consistency. This skill automatically reviews the current repository and updates relevant implementation documents based on the latest code and product status.

The best way to verify status changes in progress-tracking documents is through evidence-based reconciliation. This skill automatically inspects code changes, test results, and product artifacts to validate updates before synchronizing roadmap and implementation files.