dot-ai-prd-update-progress
Skill336 starsChanged 10 months agoMITView on GitHub
Update PRD progress based on git commits and code changes, enhanced by conversation context
In this repository33 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- dot-ai-changelog-fragmentSkill
- dot-ai-generate-cicdSkill
- dot-ai-generate-dockerfileSkill
- dot-ai-impact_analysisSkill
- dot-ai-manageKnowledgeSkill
- dot-ai-manageOrgDataSkill
- dot-ai-operateSkill
- dot-ai-prd-closeSkill
- dot-ai-prd-createSkill
- dot-ai-prd-doneSkill
- dot-ai-prd-fullSkill
- dot-ai-prd-nextSkill
- dot-ai-prds-getSkill
- dot-ai-prd-startSkill
- dot-ai-prd-update-decisionsSkill
- dot-ai-process-feature-requestSkill
- dot-ai-projectSetupSkill
- dot-ai-query-dot-aiSkill
- dot-ai-querySkill
- dot-ai-recommendSkill
- dot-ai-remediateSkill
- dot-ai-request-dot-ai-featureSkill
- dot-aiSkill
- dot-ai-tag-releaseSkill
- dot-ai-usersSkill
- dot-ai-versionSkill
- dot-ai-worktree-prdSkill
- dot-ai-write-docsSkill
- infographic-generatorSkill
- publish-mock-serverSkill
- write-docsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
31 rules. About 0 are common, 28 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈28
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Context-First Progress Analysis: - Use conversation context first, Git analysis as fallback
- Distinctive: line 19
User Confirmation: - Verify proposals and handle edge cases
- Distinctive: line 29
Current Work Context: Look for recent conversation about specific PRD work, features, or issues
- Distinctive: line 30
Git Branch Analysis: Check current git branch for PRD indicators (feature/prd-*, issue numbers)
- Distinctive: line 32
Todo List Context: Check if TodoWrite tool shows PRD-specific tasks in progress
- Distinctive: line 35
If conversation explicitly mentions "PRD #X" or specific PRD file → Use that PRD
- Distinctive: line 36
If git branch contains PRD reference (e.g., "feature/prd-12-*") → Use PRD #12
- Distinctive: line 37
If TodoWrite shows PRD-specific tasks → Use that PRD context
- Distinctive: line 38
If only one PRD file recently modified → Use that PRD
- Distinctive: line 39
If multiple PRDs possible → Ask user to clarify
- Distinctive: line 48
Todo list context: Check TodoWrite tool for completed/in-progress items
- Distinctive: line 100
Be conservative: - only mark items complete with direct evidence
- Distinctive: line 116
Examples verified: All documented examples work
- Distinctive: line 196
Requirement modifications: Update requirements to match actual functionality
- Distinctive: line 213
Acknowledge validation gaps: when you can't verify functionality works
- Distinctive: line 216
Wait for user confirmation before making changes, and handle:
- Distinctive: line 225
Update only confirmed items: - Don't make assumptions
- Distinctive: line 232
When updating PRDs based on implementation progress:
- Distinctive: line 234
CRITICAL: Always check if code examples in PRD match current implementation
- Distinctive: line 248
Validate Examples: Test updated examples to ensure they work
- Distinctive: line 258
Immediately: When interface changes break existing examples
- Distinctive: line 259
Before completion: When marking implementation milestones complete
- Distinctive: line 260
During reviews: When validating PRD accuracy
- Distinctive: line 261
User feedback: When someone reports examples don't work
- Distinctive: line 265
After successfully updating the PRD, commit all changes to preserve the progress checkpoint:
- Very specific: line 286
Reference PRD number: Always include prd-X in commit message
- Distinctive: line 289
Evidence-based: Only commit when there's actual implementation progress
- Distinctive: line 291
Note: Do NOT push commits unless explicitly requested by the user.
- Distinctive: line 295
After completing the PRD update and committing changes, guide the user based on completion status:
- Very specific: line 305
Run /prd-next to get the next task
- Very specific: line 317
Run /prd-done to move the PRD to the done folder and close the GitHub issue
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PRD Update Progress Slash Command
Instructions
You are helping update an existing Product Requirements Document (PRD) based on implementation work completed. This command analyzes git commits and code changes, enhanced by conversation context, to track PRD completion progress and propose evidence-based updates.
Process Overview
- Identify Target PRD - Determine which PRD to update
- Context-First Progress Analysis - Use conversation context first, Git analysis as fallback
- Map Changes to PRD Items - Intelligently connect work to requirements
- Propose Updates - Suggest checkbox completions and requirement changes
- User Confirmation - Verify proposals and handle edge cases
- Update PRD - Apply changes to checkboxes and status
- Flag Divergences - Alert when actual work differs from planned work
- Commit Progress Updates - Preserve progress checkpoint
- Continue to Next Task - Prompt user to run /prd-next
Step 1: Smart PRD Identification
Automatically detect target PRD using conversation context:
- Current Work Context: Look for recent conversation about specific PRD work, features, or issues
- Git Branch Analysis: Check current git branch for PRD indicators (feature/prd-*, issue numbers)
- Recent File Activity: Identify recently modified PRD files in
prds/directory - Todo List Context: Check if TodoWrite tool shows PRD-specific tasks in progress
Detection Priority Order:
- If conversation explicitly mentions "PRD #X" or specific PRD file → Use that PRD
- If git branch contains PRD reference (e.g., "feature/prd-12-*") → Use PRD #12
- If TodoWrite shows PRD-specific tasks → Use that PRD context
- If only one PRD file recently modified → Use that PRD
- If multiple PRDs possible → Ask user to clarify
Step 2: Context-First Progress Analysis
PRIORITY: Use conversation context first before Git analysis
Conversation Context Analysis (FAST - Use First)
If recent conversation shows clear work completion:
- Recently discussed implementations: "Just completed X", "Implemented Y", "Built Z"
- Todo list context: Check TodoWrite tool for completed/in-progress items
- File creation mentions: "Created file X", "Added Y functionality"
- Test completion references: "Tests passing", "All X tests complete"
- User confirmations: "That works", "Implementation complete", "Ready for next step"
Use conversation context when available - it's faster and more accurate than Git parsing
Git Change Analysis (FALLBACK - Use Only If Context Unclear)
Only use git tools when conversation context is insufficient:
Commit Analysis
# Get recent commits (last 10-20 commits)
git log --oneline -n 20
# Get detailed changes since last PRD update
git log --since="1 week ago" --pretty=format:"%h %an %ad %s" --date=shortFile Change Analysis
# See what files were modified recently
git diff --name-status HEAD~10..HEAD
# Get specific changes in key directories
git diff --stat HEAD~10..HEADChange Categorization
Identify different types of changes:
- New files: Indicates new functionality or components
- Modified files: Shows updates to existing functionality
- Test files: Evidence of testing implementation
- Documentation files: Shows documentation updates
- Configuration files: Indicates setup or deployment changes
Step 3: Comprehensive PRD Structure Analysis
CRITICAL: Systematic Checkbox Scanning
MUST perform this step to avoid missing requirements:
- Scan ALL unchecked items in the PRD using grep or search
- Categorize each unchecked requirement by type:
- Implementation (code, features, technical tasks)
- Documentation (guides, examples, cross-references)
- Validation (testing examples work, user journeys)
- User Acceptance (real-world usage, cross-client testing)
- Launch Activities (training, deployment, rollout)
- Success Metrics (adoption, analytics, support impact)
- Map git changes to appropriate categories only
- Be conservative - only mark items complete with direct evidence
Evidence-Based Completion Criteria
Implementation Requirements - Mark complete when:
- Code files: Show functionality is implemented
- Test files: Demonstrate comprehensive testing
- Integration: Components properly connected
Documentation Requirements - Mark complete when:
- Files created: Documentation files exist
- Examples validated: Commands/examples have been tested
- Cross-references work: Internal links verified
Validation Requirements - Mark complete when:
- Manual testing done: Workflows tested end-to-end
- Examples verified: All documented examples work
- User journeys confirmed: Complete workflows validated
Launch Activities - Mark complete when:
- Training delivered: Team has been trained
- Deployment done: Feature is live and accessible
- Rollout complete: Users are actively using the feature
Conservative Completion Policy
DO NOT mark complete unless there is direct evidence:
- ❌ Don't assume documentation is "good enough" without validation
- ❌ Don't mark testing complete without evidence of actual testing
- ❌ Don't mark launch items complete without proof of rollout
- ❌ Don't mark success criteria complete without metrics
Gap Analysis
Systematically identify:
- Requirements without evidence (what still needs work)
- Evidence without requirements (work done outside scope)
- Missing validation (implemented but not tested)
- Missing rollout (ready but not deployed/adopted)
Step 4: Comprehensive Progress Report
REQUIRED: Complete Status Analysis
Present a comprehensive breakdown:
## PRD Progress Analysis: [PRD Name]
### ✅ COMPLETED (with evidence):
**Implementation** (X/Y items):
- [x] Item name - Evidence: specific files/changes
- [x] Item name - Evidence: specific files/changes
**Documentation** (X/Y items):
- [x] Item name - Evidence: docs created, examples tested
- [x] Item name - Evidence: cross-references verified
### ⏳ REMAINING WORK:
**Validation** (X items unchecked):
- [ ] Item name - Reason: needs manual testing/validation
- [ ] Item name - Reason: examples not tested
**User Acceptance** (X items unchecked):
- [ ] Item name - Reason: no cross-client testing done
- [ ] Item name - Reason: no user feedback collected
**Launch Activities** (X items unchecked):
- [ ] Item name - Reason: team not trained
- [ ] Item name - Reason: not deployed to production
**Success Metrics** (X items unchecked):
- [ ] Item name - Reason: no usage data available
- [ ] Item name - Reason: adoption not measured
### 🎯 COMPLETION STATUS:
- **Overall Progress**: X% complete (Y of Z total items)
- **Implementation Phase**: 100% complete ✅
- **Validation Phase**: X% complete (what's missing)
- **Launch Phase**: X% complete (what's missing)Conservative Recommendation Policy
ONLY suggest marking items complete when you have direct evidence. CLEARLY list what still needs to be done. DO NOT claim "everything is done" unless ALL items are truly complete.
Step 5: Implementation vs Plan Analysis
Divergence Detection
Flag when actual implementation differs from planned approach:
- Architecture changes: Different technical approach than originally planned
- Scope changes: Features added or removed during implementation
- Requirement evolution: User needs that became clearer during development
- Technical discoveries: Constraints or opportunities discovered during coding
Update Recommendations
Suggest PRD updates when divergences are found:
- Decision log updates: Record why implementation approach changed
- Requirement modifications: Update requirements to match actual functionality
- Architecture updates: Revise technical approach documentation
- Scope adjustments: Move items between phases or update feature definitions
Step 6: User Confirmation Process
Present proposed changes clearly with complete transparency:
- Evidence summary: Show what work was detected
- Proposed completions: List specific checkbox items to mark done with evidence
- Remaining work analysis: Clearly show what's still unchecked and why
- Divergence alerts: Highlight any plan vs reality differences
- Honest progress assessment: Give realistic completion percentage
Critical Requirements:
- Never claim "everything is done" unless literally ALL checkboxes are complete
- Be explicit about limitations of git-based analysis
- Acknowledge validation gaps when you can't verify functionality works
- Separate implementation from validation/rollout
Wait for user confirmation before making changes, and handle:
- Partial acceptance: User agrees with some but not all suggestions
- Additional context: User provides information not visible in git history
- Scope clarification: User explains work that appears to be out of scope
- Future planning: User wants to adjust upcoming work based on current progress
Step 7: Systematic Update Application
When applying updates:
- Update only confirmed items - Don't make assumptions
- Update status sections to reflect current phase
- Preserve unchecked items that still need work
- Update completion percentages realistically
Step 7.5: Code Example Validation
When updating PRDs based on implementation progress:
CRITICAL: Always check if code examples in PRD match current implementation
Example Impact Detection
- Interface Changes: Function signatures, parameter types, return formats
- API Evolution: Method names, class structures, data models
- Workflow Updates: User interaction patterns, step sequences
- Integration Changes: How components connect and communicate
Code Example Update Process
- Scan PRD: Identify all code snippets and examples
- Cross-reference Implementation: Compare examples with actual code
- Mark Outdated: Flag examples that no longer match
- Priority Assessment: Determine which examples need immediate updates
- Update Examples: Revise code snippets to match current implementation
- Validate Examples: Test updated examples to ensure they work
Example Categories to Check
- Function calls: Parameter order, types, names
- Interface definitions: TypeScript interfaces, class structures
- API responses: Data formats, field names, response structures
- Workflow steps: User interaction sequences, tool usage patterns
- Configuration: Setup examples, environment variables, config files
When to Update Examples
- Immediately: When interface changes break existing examples
- Before completion: When marking implementation milestones complete
- During reviews: When validating PRD accuracy
- User feedback: When someone reports examples don't work
Step 8: Commit Progress Updates
After successfully updating the PRD, commit all changes to preserve the progress checkpoint:
Commit Implementation Work
# MANDATORY: Stage ALL files - implementation work AND PRD updates together
# DO NOT selectively add only PRD files - commit everything as one atomic unit
git add .
# Verify what will be committed
git status
# Create comprehensive commit with PRD reference
git commit -m "feat(prd-X): implement [brief description of completed work]
- [Brief list of key implementation achievements]
- Updated PRD checkboxes for completed items
Progress: X% complete - [next major milestone]"Commit Message Guidelines
- Reference PRD number: Always include
prd-Xin commit message - Descriptive summary: Brief but clear description of what was implemented
- Progress indication: Include completion status and next steps
- Evidence-based: Only commit when there's actual implementation progress
Note: Do NOT push commits unless explicitly requested by the user. Commits preserve local progress checkpoints without affecting remote branches.
Step 9: Next Steps Based on PRD Status
After completing the PRD update and committing changes, guide the user based on completion status:
If PRD has remaining tasks
PRD progress updated and committed.
To continue working on this PRD:
- Clear/reset the conversation context
- Run
/prd-nextto get the next task
If PRD is 100% complete
PRD #X is complete!
To finalize:
- Clear/reset the conversation context
- Run
/prd-doneto move the PRD to the done folder and close the GitHub issue
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

