ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: transform QA agent into Test Architect with advanced quality ca… (#433)

Browse Source 
* feat: transform QA agent into Test Architect with advanced quality capabilities

  - Add 6 specialized quality assessment commands
  - Implement risk-based testing with scoring
  - Create quality gate system with deterministic decisions
  - Add comprehensive test design and NFR validation
  - Update documentation with stage-based workflow integration

* feat: transform QA agent into Test Architect with advanced quality capabilities

  - Add 6 specialized quality assessment commands
  - Implement risk-based testing with scoring
  - Create quality gate system with deterministic decisions
  - Add comprehensive test design and NFR validation
  - Update documentation with stage-based workflow integration

* docs: refined the docs for test architect

* fix: addressed review comments from manjaroblack, round 1

* fix: addressed review comments from manjaroblack, round 1

---------

Co-authored-by: Murat Ozcan <murat@mac.lan>
Co-authored-by: Brian <bmadcode@gmail.com>
This commit is contained in:
Murat K Ozcan
2025-08-15 21:02:37 -05:00
committed by GitHub
parent 33269c888d
commit 0b61175d98
76 changed files with 9245 additions and 1442 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
expansion-packs/bmad-2d-unity-game-dev/checklists/game-architect-checklist.md
View File

@@ -355,34 +355,29 @@ Ask the user if they want to work through the checklist:
Generate a comprehensive validation report that includes:
1. Executive Summary
- Overall game architecture readiness (High/Medium/Low)
- Critical risks for game development
- Key strengths of the game architecture
- Unity-specific assessment
2. Game Systems Analysis
- Pass rate for each major system section
- Most concerning gaps in game architecture
- Systems requiring immediate attention
- Unity integration completeness
3. Performance Risk Assessment
- Top 5 performance risks for the game
- Mobile platform specific concerns
- Frame rate stability risks
- Memory usage concerns
4. Implementation Recommendations
- Must-fix items before development
- Unity-specific improvements needed
- Game development workflow enhancements
5. AI Agent Implementation Readiness
- Game-specific concerns for AI implementation
- Unity component complexity assessment
- Areas needing additional clarification

8
expansion-packs/bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md
View File

@@ -25,7 +25,6 @@ The goal is quality delivery, not just checking boxes.]]
1. **Requirements Met:**
[[LLM: Be specific - list each requirement and whether it's complete. Include game-specific requirements from GDD]]
- [ ] All functional requirements specified in the story are implemented.
- [ ] All acceptance criteria defined in the story are met.
- [ ] Game Design Document (GDD) requirements referenced in the story are implemented.
@@ -34,7 +33,6 @@ The goal is quality delivery, not just checking boxes.]]
2. **Coding Standards & Project Structure:**
[[LLM: Code quality matters for maintainability. Check Unity-specific patterns and C# standards]]
- [ ] All new/modified code strictly adheres to `Operational Guidelines`.
- [ ] All new/modified code aligns with `Project Structure` (Scripts/, Prefabs/, Scenes/, etc.).
- [ ] Adherence to `Tech Stack` for Unity version and packages used.
@@ -48,7 +46,6 @@ The goal is quality delivery, not just checking boxes.]]
3. **Testing:**
[[LLM: Testing proves your code works. Include Unity-specific testing with NUnit and manual testing]]
- [ ] All required unit tests (NUnit) as per the story and testing strategy are implemented.
- [ ] All required integration tests (if applicable) are implemented.
- [ ] Manual testing performed in Unity Editor for all game functionality.
@@ -60,7 +57,6 @@ The goal is quality delivery, not just checking boxes.]]
4. **Functionality & Verification:**
[[LLM: Did you actually run and test your code in Unity? Be specific about game mechanics tested]]
- [ ] Functionality has been manually verified in Unity Editor and play mode.
- [ ] Game mechanics work as specified in the GDD.
- [ ] Player controls and input handling work correctly.
@@ -73,7 +69,6 @@ The goal is quality delivery, not just checking boxes.]]
5. **Story Administration:**
[[LLM: Documentation helps the next developer. Include Unity-specific implementation notes]]
- [ ] All tasks within the story file are marked as complete.
- [ ] Any clarifications or decisions made during development are documented.
- [ ] Unity-specific implementation details documented (scene changes, prefab modifications).
@@ -83,7 +78,6 @@ The goal is quality delivery, not just checking boxes.]]
6. **Dependencies, Build & Configuration:**
[[LLM: Build issues block everyone. Ensure Unity project builds for all target platforms]]
- [ ] Unity project builds successfully without errors.
- [ ] Project builds for all target platforms (desktop/mobile as specified).
- [ ] Any new Unity packages or Asset Store items were pre-approved OR approved by user.
@@ -95,7 +89,6 @@ The goal is quality delivery, not just checking boxes.]]
7. **Game-Specific Quality:**
[[LLM: Game quality matters. Check performance, game feel, and player experience]]
- [ ] Frame rate meets target (30/60 FPS) on all platforms.
- [ ] Memory usage within acceptable limits.
- [ ] Game feel and responsiveness meet design requirements.
@@ -107,7 +100,6 @@ The goal is quality delivery, not just checking boxes.]]
8. **Documentation (If Applicable):**
[[LLM: Good documentation prevents future confusion. Include Unity-specific docs]]
- [ ] Code documentation (XML comments) for public APIs complete.
- [ ] Unity component documentation in Inspector updated.
- [ ] User-facing documentation updated, if changes impact players.