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: restore content, remove misapplied tags, eliminate Display: keyword 

- Restore emojis/checkmarks stripped during delimiter conversion
- Unwrap subprocess instructions incorrectly wrapped in <display>
- Convert Present: "..." to <display> tags for consistency
- Strip redundant Display: labels preceding <display> blocks
- Wrap bare Display: + content blocks in <display> tags
This commit is contained in:
Alex Verkhovsky 2026-02-01 15:36:55 -07:00
parent 35c7ec55d1
commit a13f399997
27 changed files with 34 additions and 85 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
View File

@ -57,18 +57,18 @@ Complete the product brief workflow, update status files, and provide guidance o
**Completion Announcement:**
<display>
**Product Brief Complete, {{user_name}}!**
🎉 **Product Brief Complete, {{user_name}}!**
I've successfully collaborated with you to create a comprehensive Product Brief for {{project_name}}.
**What we've accomplished:**
- Executive Summary with clear vision and problem statement
- Core Vision with solution definition and unique differentiators
- Target Users with rich personas and user journeys
- Success Metrics with measurable outcomes and business objectives
- MVP Scope with focused feature set and clear boundaries
- Future Vision that inspires while maintaining current focus
- ✅ Executive Summary with clear vision and problem statement
- ✅ Core Vision with solution definition and unique differentiators
- ✅ Target Users with rich personas and user journeys
- ✅ Success Metrics with measurable outcomes and business objectives
- ✅ MVP Scope with focused feature set and clear boundaries
- ✅ Future Vision that inspires while maintaining current focus
**The complete Product Brief is now available at:** `{outputFile}`

4
src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02-discovery.md
View File

@ -99,7 +99,6 @@ From step 1, I have loaded:
**Project Type Lookup:**
<display>
Your task: Lookup data in {projectTypesCSV}
**Search criteria:**
@ -110,11 +109,9 @@ Return ONLY the matching row as a YAML-formatted object with these fields:
project_type, detection_signals
**Do NOT return the entire CSV - only the matching row.**
</display>
**Domain Complexity Lookup:**
<display>
Your task: Lookup data in {domainComplexityCSV}
**Search criteria:**
@ -125,7 +122,6 @@ Return ONLY the matching row as a YAML-formatted object with these fields:
domain, complexity, typical_concerns, compliance_requirements
**Do NOT return the entire CSV - only the matching row.**
</display>
**Graceful degradation (if Task tool unavailable):**
- Load the CSV files directly

2
src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-05-domain.md
View File

@ -95,7 +95,6 @@ Proceed with domain exploration.
**Attempt subprocess data lookup:**
<display>
Your task: Lookup data in {domainComplexityCSV}
**Search criteria:**
@ -106,7 +105,6 @@ Return ONLY the matching row as a YAML-formatted object with these fields:
domain, complexity, typical_concerns, compliance_requirements
**Do NOT return the entire CSV - only the matching row.**
</display>
**Graceful degradation (if Task tool unavailable):**
- Load the CSV file directly

3
src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01-discovery.md
View File

@ -98,7 +98,6 @@ ls -t {prd_folder_path}/validation-report-*.md 2>/dev/null | head -1
**If validation report found:**
Display:
<display>
**📋 Found Validation Report**
@ -189,7 +188,6 @@ Analyze the loaded PRD:
**IF validation report provided OR PRD is BMAD Standard/Variant:**
Display:
<display>
**Edit Requirements Understood**
@ -204,7 +202,6 @@ Read fully and follow: next step (step-e-02-review.md)
**IF PRD is Legacy (Non-Standard) AND no validation report:**
Display:
<display>
**Format Detected:** Legacy PRD

3
src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01b-legacy-conversion.md
View File

@ -126,8 +126,6 @@ Return conversion assessment with gap analysis and effort estimate."
### 3. Present Conversion Assessment
Display:
<display>
**Legacy PRD Conversion Assessment**
@ -177,7 +175,6 @@ Store conversion decision for next step:
- **Edit requirements:** [user's requirements from step e-01]
- **Gap analysis:** [summary of gaps identified]
Display:
<display>
**Conversion Strategy Documented**

3
src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-02-review.md
View File

@ -144,8 +144,6 @@ Return detailed change plan with section breakdown."
### 4. Present Change Plan to User
Display:
<display>
**Deep Review Complete - Change Plan**
@ -200,7 +198,6 @@ Store approved change plan for next step:
- **Priority order:** Sequence to apply changes
- **User confirmed:** Yes
Display:
<display>
**Change Plan Approved**

4
src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-03-edit.md
View File

@ -64,7 +64,6 @@ From step e-02, retrieve:
- **Priority order:** Sequence to apply changes
- **User requirements:** Edit goals from step e-01
Display:
<display>
**Starting PRD Edits**
@ -150,7 +149,6 @@ Changes: {brief summary}
8. Functional Requirements
9. Non-Functional Requirements
Display:
<display>
**PRD Restructured**
BMAD standard structure applied.
@ -200,8 +198,6 @@ editHistory:
### 7. Confirm Completion
Display:
<display>
**PRD Edits Complete**

9
src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-04-complete.md
View File

@ -78,8 +78,6 @@ From step e-03 change execution, compile:
### 2. Present Completion Summary
Display:
<display>
**✓ PRD Edit Complete**
@ -103,12 +101,12 @@ Display:
### 3. Present MENU OPTIONS
Display:
<display>
**[V] Run Full Validation** - Execute complete validation workflow (steps-v) to verify PRD quality
**[E] Edit More** - Make additional edits to the PRD
**[S] Summary** - End with detailed summary of changes
**[X] Exit** - Exit edit workflow
</display>
#### EXECUTION RULES:
@ -118,8 +116,7 @@ Display:
#### Menu Handling Logic:
- **IF V (Run Full Validation):**
- Display:
<display>
- <display>
**Starting Validation Workflow**
This will run all 13 validation checks on the updated PRD.

2
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md
View File

@ -184,8 +184,6 @@ validationStatus: IN_PROGRESS
### 9. Present MENU OPTIONS
Display:
<display>
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Format Detection
</display>

4
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02-format-detection.md
View File

@ -132,8 +132,6 @@ Append to validation report:
**IF format is BMAD Standard or BMAD Variant:**
Display:
<display>
**Format Detected:** {classification}
@ -144,8 +142,6 @@ Without delay, read fully and follow: {nextStepFile} (step-v-03-density-validati
**IF format is Non-Standard (< 3 core sections):**
Display:
<display>
**Format Detected:** Non-Standard PRD

2
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02b-parity-check.md
View File

@ -153,8 +153,6 @@ Append to validation report:
### 4. Present Parity Analysis and Options
Display:
<display>
**Parity Analysis Complete**

2
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-03-density-validation.md
View File

@ -142,8 +142,6 @@ Append to validation report:
### 5. Display Progress and Auto-Proceed
Display:
<display>
**Information Density Validation Complete**

4
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-04-brief-coverage-validation.md
View File

@ -72,8 +72,6 @@ Append to validation report:
**Status:** N/A - No Product Brief was provided as input
```
Display:
<display>
**Product Brief Coverage: Skipped** (No Product Brief provided)
@ -184,8 +182,6 @@ Append to validation report:
### 6. Display Progress and Auto-Proceed
Display:
<display>
**Product Brief Coverage Validation Complete**

2
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-05-measurability-validation.md
View File

@ -195,8 +195,6 @@ Append to validation report:
### 5. Display Progress and Auto-Proceed
Display:
<display>
**Measurability Validation Complete**

2
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-06-traceability-validation.md
View File

@ -183,8 +183,6 @@ Append to validation report:
### 5. Display Progress and Auto-Proceed
Display:
<display>
**Traceability Validation Complete**

2
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-07-implementation-leakage-validation.md
View File

@ -172,8 +172,6 @@ Append to validation report:
### 5. Display Progress and Auto-Proceed
Display:
<display>
**Implementation Leakage Validation Complete**

4
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-08-domain-compliance-validation.md
View File

@ -155,8 +155,6 @@ Append to validation report:
**Note:** This PRD is for a standard domain without regulatory compliance requirements.
```
Display:
<display>
**Domain Compliance Validation Skipped**
@ -210,8 +208,6 @@ Append to validation report:
### 7. Display Progress and Auto-Proceed
Display:
<display>
**Domain Compliance Validation Complete**

2
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-09-project-type-validation.md
View File

@ -227,8 +227,6 @@ Append to validation report:
### 7. Display Progress and Auto-Proceed
Display:
<display>
**Project-Type Compliance Validation Complete**

2
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-10-smart-validation.md
View File

@ -173,8 +173,6 @@ Append to validation report:
### 5. Display Progress and Auto-Proceed
Display:
<display>
**SMART Requirements Validation Complete**

2
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-11-holistic-quality-validation.md
View File

@ -226,8 +226,6 @@ Append to validation report:
### 4. Display Progress and Auto-Proceed
Display:
<display>
**Holistic Quality Assessment Complete**

2
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-12-completeness-validation.md
View File

@ -206,8 +206,6 @@ Append to validation report:
### 4. Display Progress and Auto-Proceed
Display:
<display>
**Completeness Validation Complete**

6
src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md
View File

@ -123,8 +123,6 @@ overallStatus: '{Pass/Warning/Critical based on all findings}'
### 4. Present Summary to User Conversationally
Display:
<display>
**✓ PRD Validation Complete**
@ -160,12 +158,12 @@ Display:
### 5. Present MENU OPTIONS
Display:
<display>
**[R] Review Detailed Findings** - Walk through validation report section by section
**[E] Use Edit Workflow** - Use validation report with Edit workflow for systematic improvements
**[F] Fix Simpler Items** - Immediate fixes for simple issues (anti-patterns, leakage, missing headers)
**[X] Exit** - Exit and Suggest Next Steps.
</display>
#### EXECUTION RULES:

1
src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md
View File

@ -106,7 +106,6 @@ This assessment identified [X] issues across [Y] categories. Address the critica
### 5. Present Completion
Display:
<display>
**Implementation Readiness Assessment Complete**

4
src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md
View File

@ -140,12 +140,12 @@ For each epic in the approved epics_list:
#### A. Epic Overview
Display:
<display>
- Epic number and title
- Epic goal statement
- FRs covered by this epic
- Any NFRs or additional requirements relevant
</display>
#### B. Story Breakdown

16
src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-01-mode-detection.md
View File

@ -106,13 +106,15 @@ Use holistic judgment, not mechanical keyword matching.
### Escalation Triggered - Level 0-2
Present: "This looks like a focused feature with multiple components."
Display:
<display>
This looks like a focused feature with multiple components.
</display>
<display>
**[P] Plan first (tech-spec)** (recommended)
**[W] Seems bigger than quick-dev** - Recommend the Full BMad Flow PRD Process
**[E] Execute directly**
</display>
#### Menu Handling Logic:
@ -129,13 +131,15 @@ Display:
### Escalation Triggered - Level 3+
Present: "This sounds like platform/system work."
Display:
<display>
This sounds like platform/system work.
</display>
<display>
**[W] Start BMad Method** (recommended)
**[P] Plan first (tech-spec)** (lighter planning)
**[E] Execute directly** - feeling lucky
</display>
#### Menu Handling Logic:

8
src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-06-resolve-findings.md
View File

@ -25,13 +25,15 @@ From previous steps:
## RESOLUTION OPTIONS
Present: "How would you like to handle these findings?"
Display:
<display>
How would you like to handle these findings?
</display>
<display>
**[W] Walk through** - Discuss each finding individually
**[F] Fix automatically** - Automatically fix issues classified as "real"
**[S] Skip** - Acknowledge and proceed to commit
</display>
### Menu Handling Logic:

10
src/bmm/workflows/generate-project-context/steps/step-03-complete.md
View File

@ -168,7 +168,7 @@ Your project context is complete and optimized for AI agents!
**Beginner Mode:**
<display>
Excellent! Your project context guide is ready!
Excellent! Your project context guide is ready! 🎉
**What this does:**
Think of this as a 'rules of the road' guide for AI agents working on your project. It ensures they all follow the same patterns and avoid common mistakes.
@ -232,26 +232,26 @@ Final checks before completion:
Present final completion to user:
<display>
**Project Context Generation Complete!**
✅ **Project Context Generation Complete!**
Your optimized project context file is ready at:
`{output_folder}/project-context.md`
**Context Summary:**
**📊 Context Summary:**
- {{rule_count}} critical rules for AI agents
- {{section_count}} comprehensive sections
- Optimized for LLM context efficiency
- Ready for immediate agent integration
**Key Benefits:**
**🎯 Key Benefits:**
- Consistent implementation across all AI agents
- Reduced common mistakes and edge cases
- Clear guidance for project-specific patterns
- Minimal LLM context usage
**Next Steps:**
**📋 Next Steps:**
1. AI agents will automatically read this file when implementing
2. Update this file when your technology stack or patterns evolve