pm-update-roadmap-tracking

Name: pm-update-roadmap-tracking
Availability: InStock
Author: pingmepi

Synchronize roadmap documents with codebase and test evidence.

Updated Jun 8, 2026

Search Tags:#documentation #roadmap #sync #progress #tracking #product-management

Ready to run

npx skills add https://github.com/pingmepi/pm-os --skill pm-update-roadmap-tracking

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-update-roadmap-tracking
Source: https://github.com/pingmepi/pm-os/tree/main/skills/pm-update-roadmap-tracking
Command: npx skills add https://github.com/pingmepi/pm-os --skill pm-update-roadmap-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of documentation drift, where roadmap and progress-tracking documents become disconnected from the actual state of the codebase and product requirements.

Core Features & Use Cases

Evidence-Based Reconciliation: Automatically inspects code changes, test results, and product artifacts to verify status updates.
Drift Detection: Identifies discrepancies between approved product specifications and current implementation reality.
Use Case: When a developer finishes a feature, use this skill to reconcile the implementation against the PRD and roadmap, ensuring the tracker reflects the new status without manual document auditing.

Quick Start

Use the pm-update-roadmap-tracking skill to review the current repository and update all relevant roadmap and implementation documents based on the latest code and product status.

Frequently Asked Questions about pm-update-roadmap-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I sync roadmap documentation with actual codebase implementation status?▼

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.

What causes roadmap tracking documents to drift from the actual product specifications?▼

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.

How do I automatically update progress tracking files when a developer finishes a feature?▼

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.

Can I detect discrepancies between approved product specifications and current implementation reality?▼

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.

Do I need to manually audit repository-level status documents to ensure consistency?▼

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.

What's the best way to verify status changes in progress-tracking documents against evidence?▼

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.