External/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmadcode/BMAD-METHOD.git synced 2025-12-29 16:14:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix phase numbering throughout documentation

Browse Source 
- Removed all references to Phase 0 (should be Documentation prerequisite)
- Updated phase transitions from 'Phase 3→4' to 'Phase 3 to Phase 4'
- Ensured all phases are numbered 1-4 consistently
- Documentation for brownfield projects is now correctly referred to as 'Documentation prerequisite' rather than Phase 0
This commit is contained in:
Brian Madison
2025-11-26 20:59:46 -06:00
parent 04b328bd2a
commit dcaf02f665
6 changed files with 36 additions and 71 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
src/modules/bmm/docs/workflows-analysis.md
View File

@@ -40,7 +40,6 @@ These workflows feed into Phase 2 (Planning) workflows, particularly the `prd` w
| ---------------------- | ------- | ----------- | -------------------------------------------------------------- | ---------------------------- |
| **brainstorm-project** | Analyst | No | Explore solution approaches and architectures | Solution options + rationale |
| **research** | Analyst | No | Multi-type research (market/technical/competitive/user/domain) | Research reports |
| **domain-research** | Analyst | No | Industry-specific deep dive research | Domain analysis report |
| **product-brief** | Analyst | Recommended | Define product vision and strategy (interactive) | Product Brief document |
---
@@ -99,38 +98,6 @@ These workflows feed into Phase 2 (Planning) workflows, particularly the `prd` w
---
### domain-research
**Purpose:** Industry-specific deep dive research to understand domain context, regulations, standards, and patterns relevant to complex projects.
**Agent:** Analyst
**When to Use:**
- Entering new industry verticals
- Highly regulated domains (healthcare, finance, education)
- Complex business domains with specialized terminology
- Need to understand industry standards and compliance requirements
**Key Features:**
- Industry analysis and trends
- Regulatory landscape
- Standards and compliance requirements
- Domain-specific patterns and best practices
- Key players and ecosystem analysis
**Key Outputs:**
- Domain analysis report
- Compliance checklist
- Standards reference guide
- Risk assessment for domain-specific challenges
**Example:** "Healthcare application" → HIPAA compliance requirements, FDA regulations, HL7/FHIR standards, healthcare ecosystem players, domain-specific data patterns.
---
### product-brief
**Purpose:** Interactive product brief creation that guides strategic product vision definition.
@@ -292,7 +259,7 @@ A: Typically hours to 1-2 days. If taking longer, you may be over-analyzing. Mov
A: That's the point! Analysis helps you fail fast and pivot before heavy planning investment.
**Q: Should brownfield projects do Analysis?**
A: Usually no. Start with `document-project` (Phase 0), then skip to Planning (Phase 2).
A: Usually no. Start with `document-project` (Documentation prerequisite), then skip to Planning (Phase 2).
---