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

massive architecture creation overhaul

Browse Source
This commit is contained in:
Brian Madison
2025-10-19 23:28:38 -05:00
parent d3402c3132
commit 2a6eb71612
75 changed files with 2440 additions and 4070 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md
View File

@@ -32,7 +32,7 @@ After setup, return here to validate implementation readiness.
- Level 0-1: Tech spec and simple stories only (no PRD, minimal solutioning)
- Level 2: PRD, tech spec, epics/stories (no separate architecture doc)
- Level 3-4: Full suite - PRD, solution architecture, epics/stories, possible UX artifacts
- Level 3-4: Full suite - PRD, architecture document, epics/stories, possible UX artifacts
</action>
<critical>The validation approach must adapt to the project level - don't look for documents that shouldn't exist at lower levels</critical>
@@ -54,7 +54,7 @@ After setup, return here to validate implementation readiness.
<action>For Level 2-4 projects, locate:
- Product Requirements Document (PRD)
- Solution Architecture document (Level 3-4 only)
- Architecture document (architecture.md) (Level 3-4 only)
- Technical Specification (Level 2 includes architecture within)
- Epic and story breakdowns
- UX artifacts if the active path includes UX workflow
@@ -119,9 +119,10 @@ After setup, return here to validate implementation readiness.
<action>PRD ↔ Architecture Alignment (Level 3-4):
- Verify every PRD requirement has corresponding architectural support
- Check that architecture decisions don't contradict PRD constraints
- Identify any architecture additions beyond PRD scope (potential gold-plating)
- Ensure non-functional requirements from PRD are addressed in architecture
- Check that architectural decisions don't contradict PRD constraints
- Identify any architectural additions beyond PRD scope (potential gold-plating)
- Ensure non-functional requirements from PRD are addressed in architecture document
- If using new architecture workflow: verify implementation patterns are defined
</action>
<action>PRD ↔ Stories Coverage (Level 2-4):