Stats
Actions
Tags
From bad-daves-robot-army
Processes stakeholder feedback on a specified PRD file, categorizes it, and creates an updated version incorporating changes with tracked decisions.
How this command is triggered — by the user, by Claude, or both
Slash command
/bad-daves-robot-army:process-prd-feedbackThe summary Claude sees in its command listing — used to decide when to auto-load this command
Using @agent-product-manager, process stakeholder feedback on an existing Product Requirements Document (PRD) and create an updated version that incorporates their input while maintaining document coherence and tracking changes.
## Context
This command helps product managers systematically process feedback from various stakeholders (engineering, design, business, customers) and create a revised PRD that addresses concerns, incorporates suggestions, and documents decisions about what feedback was accepted or deferred.
## Input Parsing
The user invoked: /process-prd-feedback {prd_file_path}...Using @agent-product-manager, process stakeholder feedback on an existing Product Requirements Document (PRD) and create an updated version that incorporates their input while maintaining document coherence and tracking changes.
This command helps product managers systematically process feedback from various stakeholders (engineering, design, business, customers) and create a revised PRD that addresses concerns, incorporates suggestions, and documents decisions about what feedback was accepted or deferred.
The user invoked: /process-prd-feedback {prd_file_path}
You need to gather stakeholder feedback, analyze it, and create an updated PRD version that thoughtfully incorporates the input while maintaining document quality and coherence.
Ask the user to provide feedback in one of these formats:
Structured feedback (preferred):
Unstructured feedback:
Multiple stakeholder inputs:
Organize feedback into categories:
For each piece of feedback, determine:
For each feedback item:
Accept and Integrate:
Defer to Future Phase:
Decline with Rationale:
Request Clarification:
When stakeholders provide conflicting feedback:
Systematically update the PRD:
Generate a comprehensive change summary including:
Version Information:
Changes Incorporated:
Feedback Deferred:
Feedback Declined:
Outstanding Items:
Create two files:
Save at /prds/prd-{product-name}-v{version}-{timestamp}.md with:
Save at /prds/changelog-{product-name}-{timestamp}.md with:
# PRD Change Log: {Product Name}
**Original Version:** {version}
**Updated Version:** {new version}
**Review Date:** {date}
**Participants:** {list of stakeholders}
## Executive Summary of Changes
[High-level overview of major changes]
## Accepted Changes
### Section: {Section Name}
**Stakeholder:** {Name, Role}
**Original:** {Original text/requirement}
**Updated:** {New text/requirement}
**Rationale:** {Why this change was accepted}
**Impact:** {Scope/Timeline/Resource impact}
[Repeat for each accepted change]
## Deferred Items
### Item: {Description}
**Stakeholder:** {Name, Role}
**Request:** {What was requested}
**Decision:** Deferred to {phase/backlog}
**Rationale:** {Why deferred}
## Declined Feedback
### Item: {Description}
**Stakeholder:** {Name, Role}
**Request:** {What was requested}
**Decision:** Not incorporated
**Rationale:** {Clear explanation}
**Alternative:** {If applicable}
## Conflict Resolutions
### Conflict: {Description}
**Stakeholder A Position:** {Description}
**Stakeholder B Position:** {Description}
**Resolution:** {Decision made}
**Rationale:** {Reasoning}
## Outstanding Questions
1. **For {Stakeholder}:** {Question}
2. **For {Stakeholder}:** {Question}
## Next Steps
- [ ] Follow up on outstanding questions
- [ ] Schedule review of updated PRD
- [ ] Communicate changes to team
Initial Setup:
Feedback Collection:
Conflict Resolution:
Quality Checks:
User Confirmation:
npx claudepluginhub dgriffith/bad-daves-robot-army/refine-prdRefines existing PRD file by reviewing for issues like missing IDs/ACs/priorities, user-selecting fixes, incorporating feedback, and outputting version-bumped PRD with health summaries and readiness scores.
/refineAnalyzes existing PRD for gaps using a section checklist, generates markdown gap analysis, and refines via targeted interactive questions.
/refineEdits and sharpens existing product briefs or feature specs with new context. Accepts document path, ID, or interactive mode to select recent documents.
/write-prdGenerates a structured PRD by chaining problem framing, persona alignment, requirements definition, and story scaffolding into a single workflow.
/write-prdGenerates a structured Product Requirements Document from feature ideas or problem statements, interactively gathering context via questions and saving as Markdown.