prd-update-progress

Update PRD checkboxes and progress status based on git commits and conversation context.

Updated Nov 7, 2024
One-click install
npx skills add https://github.com/jeremysball/dotfiles --skill prd-update-progress-jeremysball
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-update-progress
Source: https://github.com/jeremysball/dotfiles/tree/main/.pi/skills-archive/prd-update-progress
Command: npx skills add https://github.com/jeremysball/dotfiles --skill prd-update-progress-jeremysball

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a Product Requirements Document in sync with actual implementation work is tedious and error-prone; this Skill analyzes completed work and proposes evidence-based checkbox and status updates to the PRD. ## Core Features & Use Cases - Context-First Progress Analysis: Uses conversation context and todo lists first, falling back to git log and diff analysis only when context is unclear. - Evidence-Based Completion: Categorizes unchecked requirements (implementation, documentation, validation, launch, metrics) and only marks items complete with direct evidence such as passing tests, mypy, and ruff checks. - Divergence Detection and Commits: Flags where implementation differs from the plan, updates outdated code examples, and commits progress with a PRD-referenced message. - Use Case: After finishing a feature described in PRD #12, run this Skill to detect which requirements are now satisfied, update the checkboxes, commit the progress checkpoint, and get routed to /prd-next or /prd-done. ## Quick Start Ask the assistant to update the current PRD's progress based on the work just completed in this session.

Frequently Asked Questions about prd-update-progress

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

FAQPage Schema
How do I update a PRD based on completed implementation work?▼

Run this Skill after finishing implementation work; it detects the target PRD from conversation context, git branch names, or recently modified files, then proposes checkbox completions backed by concrete evidence before applying them.

How does the PRD progress analysis decide which checkboxes to mark complete?▼

It categorizes unchecked items into implementation, documentation, validation, launch, and metrics groups, then marks items complete only with direct evidence such as code files, passing tests, and clean mypy and ruff runs.

Does it use git history or conversation context to detect progress?▼

Conversation context is used first because it is faster and more accurate; git log and git diff analysis serve as a fallback only when the conversation does not clearly show what was completed.

Can it detect when implementation diverges from the original PRD plan?▼

Yes, it flags architecture changes, scope changes, and requirement evolution, then recommends decision log updates, requirement modifications, and updates to outdated code examples in the PRD.

What happens after the PRD progress update is committed?▼

Changes are committed locally with a PRD-referenced message; if tasks remain you are directed to /prd-next, and if the PRD is 100% complete you are directed to /prd-done to close it out.