From 52f68890890a86c303c338f7646207fec99ea315 Mon Sep 17 00:00:00 2001 From: lihangmissu Date: Sat, 20 Sep 2025 07:08:31 +0800 Subject: [PATCH] fix: BMAD Brownfield Document Naming Inconsistency Bug (#627) --- bmad-core/checklists/po-master-checklist.md | 6 +++--- bmad-core/templates/brownfield-architecture-tmpl.yaml | 2 +- dist/agents/architect.txt | 2 +- dist/agents/bmad-master.txt | 8 ++++---- dist/agents/po.txt | 6 +++--- dist/teams/team-all.txt | 8 ++++---- dist/teams/team-fullstack.txt | 8 ++++---- dist/teams/team-ide-minimal.txt | 6 +++--- dist/teams/team-no-ui.txt | 8 ++++---- 9 files changed, 27 insertions(+), 27 deletions(-) diff --git a/bmad-core/checklists/po-master-checklist.md b/bmad-core/checklists/po-master-checklist.md index d0c7aeca..277b7c05 100644 --- a/bmad-core/checklists/po-master-checklist.md +++ b/bmad-core/checklists/po-master-checklist.md @@ -15,7 +15,7 @@ First, determine the project type by checking: 2. Is this a BROWNFIELD project (enhancing existing system)? - Look for: References to existing codebase, enhancement/modification language - - Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis + - Check for: prd.md, architecture.md, existing system analysis 3. Does the project include UI/UX components? - Check for: frontend-architecture.md, UI/UX specifications, design files @@ -33,8 +33,8 @@ For GREENFIELD projects: For BROWNFIELD projects: -- brownfield-prd.md - The brownfield enhancement requirements -- brownfield-architecture.md - The enhancement architecture +- prd.md - The brownfield enhancement requirements +- architecture.md - The enhancement architecture - Existing project codebase access (CRITICAL - cannot proceed without this) - Current deployment configuration and infrastructure details - Database schemas, API documentation, monitoring setup diff --git a/bmad-core/templates/brownfield-architecture-tmpl.yaml b/bmad-core/templates/brownfield-architecture-tmpl.yaml index c24f89ab..3f634371 100644 --- a/bmad-core/templates/brownfield-architecture-tmpl.yaml +++ b/bmad-core/templates/brownfield-architecture-tmpl.yaml @@ -23,7 +23,7 @@ sections: 1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead." 2. **REQUIRED INPUTS**: - - Completed brownfield-prd.md + - Completed prd.md - Existing project technical documentation (from docs folder or user-provided) - Access to existing project structure (IDE or uploaded files) diff --git a/dist/agents/architect.txt b/dist/agents/architect.txt index 992cbfbe..778054fa 100644 --- a/dist/agents/architect.txt +++ b/dist/agents/architect.txt @@ -1608,7 +1608,7 @@ sections: 1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead." 2. **REQUIRED INPUTS**: - - Completed brownfield-prd.md + - Completed prd.md - Existing project technical documentation (from docs folder or user-provided) - Access to existing project structure (IDE or uploaded files) diff --git a/dist/agents/bmad-master.txt b/dist/agents/bmad-master.txt index a0ffd1f4..36c8b854 100644 --- a/dist/agents/bmad-master.txt +++ b/dist/agents/bmad-master.txt @@ -2817,7 +2817,7 @@ sections: 1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead." 2. **REQUIRED INPUTS**: - - Completed brownfield-prd.md + - Completed prd.md - Existing project technical documentation (from docs folder or user-provided) - Access to existing project structure (IDE or uploaded files) @@ -7114,7 +7114,7 @@ First, determine the project type by checking: 2. Is this a BROWNFIELD project (enhancing existing system)? - Look for: References to existing codebase, enhancement/modification language - - Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis + - Check for: prd.md, architecture.md, existing system analysis 3. Does the project include UI/UX components? - Check for: frontend-architecture.md, UI/UX specifications, design files @@ -7132,8 +7132,8 @@ For GREENFIELD projects: For BROWNFIELD projects: -- brownfield-prd.md - The brownfield enhancement requirements -- brownfield-architecture.md - The enhancement architecture +- prd.md - The brownfield enhancement requirements +- architecture.md - The enhancement architecture - Existing project codebase access (CRITICAL - cannot proceed without this) - Current deployment configuration and infrastructure details - Database schemas, API documentation, monitoring setup diff --git a/dist/agents/po.txt b/dist/agents/po.txt index 2ab445d5..69371456 100644 --- a/dist/agents/po.txt +++ b/dist/agents/po.txt @@ -933,7 +933,7 @@ First, determine the project type by checking: 2. Is this a BROWNFIELD project (enhancing existing system)? - Look for: References to existing codebase, enhancement/modification language - - Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis + - Check for: prd.md, architecture.md, existing system analysis 3. Does the project include UI/UX components? - Check for: frontend-architecture.md, UI/UX specifications, design files @@ -951,8 +951,8 @@ For GREENFIELD projects: For BROWNFIELD projects: -- brownfield-prd.md - The brownfield enhancement requirements -- brownfield-architecture.md - The enhancement architecture +- prd.md - The brownfield enhancement requirements +- architecture.md - The enhancement architecture - Existing project codebase access (CRITICAL - cannot proceed without this) - Current deployment configuration and infrastructure details - Database schemas, API documentation, monitoring setup diff --git a/dist/teams/team-all.txt b/dist/teams/team-all.txt index 22cf3855..5ef07145 100644 --- a/dist/teams/team-all.txt +++ b/dist/teams/team-all.txt @@ -4528,7 +4528,7 @@ sections: 1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead." 2. **REQUIRED INPUTS**: - - Completed brownfield-prd.md + - Completed prd.md - Existing project technical documentation (from docs folder or user-provided) - Access to existing project structure (IDE or uploaded files) @@ -8654,7 +8654,7 @@ First, determine the project type by checking: 2. Is this a BROWNFIELD project (enhancing existing system)? - Look for: References to existing codebase, enhancement/modification language - - Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis + - Check for: prd.md, architecture.md, existing system analysis 3. Does the project include UI/UX components? - Check for: frontend-architecture.md, UI/UX specifications, design files @@ -8672,8 +8672,8 @@ For GREENFIELD projects: For BROWNFIELD projects: -- brownfield-prd.md - The brownfield enhancement requirements -- brownfield-architecture.md - The enhancement architecture +- prd.md - The brownfield enhancement requirements +- architecture.md - The enhancement architecture - Existing project codebase access (CRITICAL - cannot proceed without this) - Current deployment configuration and infrastructure details - Database schemas, API documentation, monitoring setup diff --git a/dist/teams/team-fullstack.txt b/dist/teams/team-fullstack.txt index f85754de..dc7bbebb 100644 --- a/dist/teams/team-fullstack.txt +++ b/dist/teams/team-fullstack.txt @@ -6407,7 +6407,7 @@ sections: 1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead." 2. **REQUIRED INPUTS**: - - Completed brownfield-prd.md + - Completed prd.md - Existing project technical documentation (from docs folder or user-provided) - Access to existing project structure (IDE or uploaded files) @@ -8648,7 +8648,7 @@ First, determine the project type by checking: 2. Is this a BROWNFIELD project (enhancing existing system)? - Look for: References to existing codebase, enhancement/modification language - - Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis + - Check for: prd.md, architecture.md, existing system analysis 3. Does the project include UI/UX components? - Check for: frontend-architecture.md, UI/UX specifications, design files @@ -8666,8 +8666,8 @@ For GREENFIELD projects: For BROWNFIELD projects: -- brownfield-prd.md - The brownfield enhancement requirements -- brownfield-architecture.md - The enhancement architecture +- prd.md - The brownfield enhancement requirements +- architecture.md - The enhancement architecture - Existing project codebase access (CRITICAL - cannot proceed without this) - Current deployment configuration and infrastructure details - Database schemas, API documentation, monitoring setup diff --git a/dist/teams/team-ide-minimal.txt b/dist/teams/team-ide-minimal.txt index bc7e5fb7..29a98b03 100644 --- a/dist/teams/team-ide-minimal.txt +++ b/dist/teams/team-ide-minimal.txt @@ -2588,7 +2588,7 @@ First, determine the project type by checking: 2. Is this a BROWNFIELD project (enhancing existing system)? - Look for: References to existing codebase, enhancement/modification language - - Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis + - Check for: prd.md, architecture.md, existing system analysis 3. Does the project include UI/UX components? - Check for: frontend-architecture.md, UI/UX specifications, design files @@ -2606,8 +2606,8 @@ For GREENFIELD projects: For BROWNFIELD projects: -- brownfield-prd.md - The brownfield enhancement requirements -- brownfield-architecture.md - The enhancement architecture +- prd.md - The brownfield enhancement requirements +- architecture.md - The enhancement architecture - Existing project codebase access (CRITICAL - cannot proceed without this) - Current deployment configuration and infrastructure details - Database schemas, API documentation, monitoring setup diff --git a/dist/teams/team-no-ui.txt b/dist/teams/team-no-ui.txt index 57d9a790..40c0a89c 100644 --- a/dist/teams/team-no-ui.txt +++ b/dist/teams/team-no-ui.txt @@ -5945,7 +5945,7 @@ sections: 1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead." 2. **REQUIRED INPUTS**: - - Completed brownfield-prd.md + - Completed prd.md - Existing project technical documentation (from docs folder or user-provided) - Access to existing project structure (IDE or uploaded files) @@ -8186,7 +8186,7 @@ First, determine the project type by checking: 2. Is this a BROWNFIELD project (enhancing existing system)? - Look for: References to existing codebase, enhancement/modification language - - Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis + - Check for: prd.md, architecture.md, existing system analysis 3. Does the project include UI/UX components? - Check for: frontend-architecture.md, UI/UX specifications, design files @@ -8204,8 +8204,8 @@ For GREENFIELD projects: For BROWNFIELD projects: -- brownfield-prd.md - The brownfield enhancement requirements -- brownfield-architecture.md - The enhancement architecture +- prd.md - The brownfield enhancement requirements +- architecture.md - The enhancement architecture - Existing project codebase access (CRITICAL - cannot proceed without this) - Current deployment configuration and infrastructure details - Database schemas, API documentation, monitoring setup