prd-update-progress

You can automatically update PRD progress from git commits by analyzing commit messages and code diffs to map development work directly to PRD checklist items. This Skill scans recent repository activity to propose evidence-based status updates, reducing manual tracking efforts for product teams.

Commit-to-PRD mapping is the process of linking code changes and commit messages to specific PRD checklist items. By analyzing git diffs and conversation context, this approach automatically reflects feature completion status and flags divergences between planned requirements and actual development.

Yes, you can use conversation context to refine PRD progress estimates alongside git analysis. The Skill reads contextual discussions to interpret commit activity, flag potential divergences from the PRD, and generate more accurate, evidence-based progress reports for product reviews.

To detect divergence between code changes and PRD requirements, the Skill maps git commit diffs against existing PRD items and flags discrepancies. It applies contextual reasoning to identify when development work drifts from planned product requirements, proposing structured progress updates accordingly.

Yes, PRD progress automation works with existing git repositories and PRD files. The solution requires integration with your git repository to read commit messages and diffs, alongside access to PRD documents, enabling automated evidence-based progress tracking without disrupting current workflows.

Automated PRD progress tracking from git history relies heavily on commit message quality and clear PRD checklists. If commits are poorly documented or PRD items lack specificity, the Skill may struggle to accurately map changes, requiring manual review of proposed progress updates and divergence flags.