fix: BMAD Brownfield Document Naming Inconsistency Bug (#627)

This commit is contained in:
lihangmissu
2025-09-20 07:08:31 +08:00
committed by GitHub
parent f09e282d72
commit 52f6889089
9 changed files with 27 additions and 27 deletions

View File

@@ -15,7 +15,7 @@ First, determine the project type by checking:
2. Is this a BROWNFIELD project (enhancing existing system)? 2. Is this a BROWNFIELD project (enhancing existing system)?
- Look for: References to existing codebase, enhancement/modification language - 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? 3. Does the project include UI/UX components?
- Check for: frontend-architecture.md, UI/UX specifications, design files - Check for: frontend-architecture.md, UI/UX specifications, design files
@@ -33,8 +33,8 @@ For GREENFIELD projects:
For BROWNFIELD projects: For BROWNFIELD projects:
- brownfield-prd.md - The brownfield enhancement requirements - prd.md - The brownfield enhancement requirements
- brownfield-architecture.md - The enhancement architecture - architecture.md - The enhancement architecture
- Existing project codebase access (CRITICAL - cannot proceed without this) - Existing project codebase access (CRITICAL - cannot proceed without this)
- Current deployment configuration and infrastructure details - Current deployment configuration and infrastructure details
- Database schemas, API documentation, monitoring setup - Database schemas, API documentation, monitoring setup

View File

@@ -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." 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**: 2. **REQUIRED INPUTS**:
- Completed brownfield-prd.md - Completed prd.md
- Existing project technical documentation (from docs folder or user-provided) - Existing project technical documentation (from docs folder or user-provided)
- Access to existing project structure (IDE or uploaded files) - Access to existing project structure (IDE or uploaded files)

View File

@@ -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." 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**: 2. **REQUIRED INPUTS**:
- Completed brownfield-prd.md - Completed prd.md
- Existing project technical documentation (from docs folder or user-provided) - Existing project technical documentation (from docs folder or user-provided)
- Access to existing project structure (IDE or uploaded files) - Access to existing project structure (IDE or uploaded files)

View File

@@ -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." 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**: 2. **REQUIRED INPUTS**:
- Completed brownfield-prd.md - Completed prd.md
- Existing project technical documentation (from docs folder or user-provided) - Existing project technical documentation (from docs folder or user-provided)
- Access to existing project structure (IDE or uploaded files) - 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)? 2. Is this a BROWNFIELD project (enhancing existing system)?
- Look for: References to existing codebase, enhancement/modification language - 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? 3. Does the project include UI/UX components?
- Check for: frontend-architecture.md, UI/UX specifications, design files - Check for: frontend-architecture.md, UI/UX specifications, design files
@@ -7132,8 +7132,8 @@ For GREENFIELD projects:
For BROWNFIELD projects: For BROWNFIELD projects:
- brownfield-prd.md - The brownfield enhancement requirements - prd.md - The brownfield enhancement requirements
- brownfield-architecture.md - The enhancement architecture - architecture.md - The enhancement architecture
- Existing project codebase access (CRITICAL - cannot proceed without this) - Existing project codebase access (CRITICAL - cannot proceed without this)
- Current deployment configuration and infrastructure details - Current deployment configuration and infrastructure details
- Database schemas, API documentation, monitoring setup - Database schemas, API documentation, monitoring setup

6
dist/agents/po.txt vendored
View File

@@ -933,7 +933,7 @@ First, determine the project type by checking:
2. Is this a BROWNFIELD project (enhancing existing system)? 2. Is this a BROWNFIELD project (enhancing existing system)?
- Look for: References to existing codebase, enhancement/modification language - 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? 3. Does the project include UI/UX components?
- Check for: frontend-architecture.md, UI/UX specifications, design files - Check for: frontend-architecture.md, UI/UX specifications, design files
@@ -951,8 +951,8 @@ For GREENFIELD projects:
For BROWNFIELD projects: For BROWNFIELD projects:
- brownfield-prd.md - The brownfield enhancement requirements - prd.md - The brownfield enhancement requirements
- brownfield-architecture.md - The enhancement architecture - architecture.md - The enhancement architecture
- Existing project codebase access (CRITICAL - cannot proceed without this) - Existing project codebase access (CRITICAL - cannot proceed without this)
- Current deployment configuration and infrastructure details - Current deployment configuration and infrastructure details
- Database schemas, API documentation, monitoring setup - Database schemas, API documentation, monitoring setup

View File

@@ -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." 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**: 2. **REQUIRED INPUTS**:
- Completed brownfield-prd.md - Completed prd.md
- Existing project technical documentation (from docs folder or user-provided) - Existing project technical documentation (from docs folder or user-provided)
- Access to existing project structure (IDE or uploaded files) - 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)? 2. Is this a BROWNFIELD project (enhancing existing system)?
- Look for: References to existing codebase, enhancement/modification language - 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? 3. Does the project include UI/UX components?
- Check for: frontend-architecture.md, UI/UX specifications, design files - Check for: frontend-architecture.md, UI/UX specifications, design files
@@ -8672,8 +8672,8 @@ For GREENFIELD projects:
For BROWNFIELD projects: For BROWNFIELD projects:
- brownfield-prd.md - The brownfield enhancement requirements - prd.md - The brownfield enhancement requirements
- brownfield-architecture.md - The enhancement architecture - architecture.md - The enhancement architecture
- Existing project codebase access (CRITICAL - cannot proceed without this) - Existing project codebase access (CRITICAL - cannot proceed without this)
- Current deployment configuration and infrastructure details - Current deployment configuration and infrastructure details
- Database schemas, API documentation, monitoring setup - Database schemas, API documentation, monitoring setup

View File

@@ -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." 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**: 2. **REQUIRED INPUTS**:
- Completed brownfield-prd.md - Completed prd.md
- Existing project technical documentation (from docs folder or user-provided) - Existing project technical documentation (from docs folder or user-provided)
- Access to existing project structure (IDE or uploaded files) - 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)? 2. Is this a BROWNFIELD project (enhancing existing system)?
- Look for: References to existing codebase, enhancement/modification language - 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? 3. Does the project include UI/UX components?
- Check for: frontend-architecture.md, UI/UX specifications, design files - Check for: frontend-architecture.md, UI/UX specifications, design files
@@ -8666,8 +8666,8 @@ For GREENFIELD projects:
For BROWNFIELD projects: For BROWNFIELD projects:
- brownfield-prd.md - The brownfield enhancement requirements - prd.md - The brownfield enhancement requirements
- brownfield-architecture.md - The enhancement architecture - architecture.md - The enhancement architecture
- Existing project codebase access (CRITICAL - cannot proceed without this) - Existing project codebase access (CRITICAL - cannot proceed without this)
- Current deployment configuration and infrastructure details - Current deployment configuration and infrastructure details
- Database schemas, API documentation, monitoring setup - Database schemas, API documentation, monitoring setup

View File

@@ -2588,7 +2588,7 @@ First, determine the project type by checking:
2. Is this a BROWNFIELD project (enhancing existing system)? 2. Is this a BROWNFIELD project (enhancing existing system)?
- Look for: References to existing codebase, enhancement/modification language - 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? 3. Does the project include UI/UX components?
- Check for: frontend-architecture.md, UI/UX specifications, design files - Check for: frontend-architecture.md, UI/UX specifications, design files
@@ -2606,8 +2606,8 @@ For GREENFIELD projects:
For BROWNFIELD projects: For BROWNFIELD projects:
- brownfield-prd.md - The brownfield enhancement requirements - prd.md - The brownfield enhancement requirements
- brownfield-architecture.md - The enhancement architecture - architecture.md - The enhancement architecture
- Existing project codebase access (CRITICAL - cannot proceed without this) - Existing project codebase access (CRITICAL - cannot proceed without this)
- Current deployment configuration and infrastructure details - Current deployment configuration and infrastructure details
- Database schemas, API documentation, monitoring setup - Database schemas, API documentation, monitoring setup

View File

@@ -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." 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**: 2. **REQUIRED INPUTS**:
- Completed brownfield-prd.md - Completed prd.md
- Existing project technical documentation (from docs folder or user-provided) - Existing project technical documentation (from docs folder or user-provided)
- Access to existing project structure (IDE or uploaded files) - 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)? 2. Is this a BROWNFIELD project (enhancing existing system)?
- Look for: References to existing codebase, enhancement/modification language - 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? 3. Does the project include UI/UX components?
- Check for: frontend-architecture.md, UI/UX specifications, design files - Check for: frontend-architecture.md, UI/UX specifications, design files
@@ -8204,8 +8204,8 @@ For GREENFIELD projects:
For BROWNFIELD projects: For BROWNFIELD projects:
- brownfield-prd.md - The brownfield enhancement requirements - prd.md - The brownfield enhancement requirements
- brownfield-architecture.md - The enhancement architecture - architecture.md - The enhancement architecture
- Existing project codebase access (CRITICAL - cannot proceed without this) - Existing project codebase access (CRITICAL - cannot proceed without this)
- Current deployment configuration and infrastructure details - Current deployment configuration and infrastructure details
- Database schemas, API documentation, monitoring setup - Database schemas, API documentation, monitoring setup