massive architecture creation overhaul

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

View File

@@ -178,7 +178,7 @@ The workflow adapts automatically based on project assessment, but key configura
- `PRD.md` - Comprehensive product specification
- `epics.md` - Complete epic/story breakdown
- Hands off to solution-architecture workflow (Phase 3)
- `solution-architecture.md` - Generated by architect workflow
- `architecture.md` - Generated by architect workflow
- Then to implementation
## Requirements

View File

@@ -198,7 +198,7 @@ When a game project completes the GDD and moves to solutioning:
2. Loads GDD.md instead of PRD.md
3. Matches game platforms to solutioning `registry.csv` game-\* entries
4. Provides engine-specific guidance (Unity, Godot, Phaser, etc.)
5. Generates solution-architecture.md with platform decisions
5. Generates architecture.md with platform decisions
6. Creates per-epic tech specs
Example solutioning registry entries:

View File

@@ -382,7 +382,7 @@ Since this is a Level {{project_level}} game project, you need solutioning for p
**The solutioning workflow will:**
- Determine game engine/platform (Unity, Godot, Phaser, custom, etc.)
- Generate solution-architecture.md with engine-specific decisions
- Generate architecture.md with engine-specific decisions
- Create per-epic tech specs
- Handle platform-specific architecture (from registry.csv game-\* entries)
@@ -395,7 +395,7 @@ Since this is a Level {{project_level}} game project, you need solutioning for p
- [ ] **Run solutioning workflow** (REQUIRED)
- Command: `workflow solution-architecture`
- Input: GDD.md, bmm-workflow-status.md
- Output: solution-architecture.md with engine/platform specifics
- Output: architecture.md with engine/platform specifics
- Note: Registry.csv will provide engine-specific guidance
### Phase 2: Prototype and Playtesting
@@ -426,7 +426,7 @@ Since this is a Level {{project_level}} game project, you need solutioning for p
- [ ] **Generate detailed user stories**
- Command: `workflow generate-stories`
- Input: GDD.md + solution-architecture.md
- Input: GDD.md + architecture.md
- [ ] **Sprint planning**
- Vertical slices

View File

@@ -58,7 +58,7 @@ If no: We'll gather basic requirements to create the UX spec
- PRD.md (primary source for requirements and user journeys)
- epics.md (helps understand feature grouping)
- tech-spec.md (understand technical constraints)
- solution-architecture.md (if Level 3-4 project)
- architecture.md (if Level 3-4 project)
- bmm-workflow-status.md (understand project level and scope)
</check>