ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity

fix: add brainstorming reconciliation step to PRD polish workflow 

When feeding brainstorming sessions into the PRD workflow, soft/qualitative
ideas (tone, personality, interaction design, coaching philosophy) get
silently dropped because they don't map cleanly to the PRD's structured
template (FR/NFR format). The resulting PRD reads as complete, so the
loss is invisible without manually diffing against the brainstorming output.

Add a reconciliation check in step-11 (polish) that cross-references the
brainstorming document against the finished PRD, flags ideas that didn't
land anywhere, and lets the user decide which to incorporate.
This commit is contained in:
Nikolas de Hor 2026-03-11 21:37:45 -03:00
parent 32693f1a6b
commit 6ab2052158
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-11-polish.md
View File

@ -99,6 +99,22 @@ Review the entire document with PRD purpose principles in mind:
- Are technical terms used appropriately? - Are technical terms used appropriately?
- Would stakeholders find this easy to understand? - Would stakeholders find this easy to understand?
### 2b. Brainstorming Reconciliation (if brainstorming input exists)
**Check the PRD frontmatter `inputDocuments` for any brainstorming document** (e.g., `brainstorming-session*.md`, `brainstorming-report.md`). If a brainstorming document was used as input:
1. **Load the brainstorming document** and extract all distinct ideas, themes, and recommendations
2. **Cross-reference against the PRD** — for each brainstorming idea, check if it landed in any PRD section (requirements, success criteria, user journeys, scope, etc.)
3. **Identify dropped ideas** — ideas from brainstorming that do not appear anywhere in the PRD. Pay special attention to:
- Tone, personality, and interaction design ideas (these are most commonly lost)
- Design philosophy and coaching approach ideas
- "What should this feel like" ideas (UX feel, not just UX function)
- Qualitative/soft ideas that don't map cleanly to functional requirements
4. **Present findings to user**: "These brainstorming ideas did not make it into the PRD: [list]. Should any be incorporated?"
5. **If user wants to incorporate dropped ideas**: Add them to the most appropriate PRD section (success criteria, non-functional requirements, or a new section if needed)
**Why this matters**: Brainstorming documents are often long, and the PRD's structured template has an implicit bias toward concrete/structural ideas. Soft ideas (tone, philosophy, interaction feel) frequently get silently dropped because they don't map cleanly to FR/NFR format.
### 3. Optimization Actions ### 3. Optimization Actions
Make targeted improvements: Make targeted improvements:
@ -193,6 +209,7 @@ When user selects 'C', replace the entire document content with the polished ver
✅ User's voice and intent preserved ✅ User's voice and intent preserved
✅ Document is more readable and professional ✅ Document is more readable and professional
✅ A/P/C menu presented and handled correctly ✅ A/P/C menu presented and handled correctly
✅ Brainstorming reconciliation completed (if brainstorming input exists)
✅ Polished document saved when C selected ✅ Polished document saved when C selected
## FAILURE MODES: ## FAILURE MODES: