bmad-method 4.37.0 → 4.39.0

package/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt

@@ -318,7 +318,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
 ## Instructions
 
 1. **Initial Assessment**
-
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
@@ -331,14 +330,12 @@ If the user asks or does not specify a specific checklist, list the checklists a
      - All at once (YOLO mode - recommended for checklists, there will be a summary of sections at the end to discuss)
 
 2. **Document and Artifact Gathering**
-
    - Each checklist will specify its required documents/artifacts at the beginning
    - Follow the checklist's specific instructions for what to gather, generally a file can be resolved in the docs folder, if not or unsure, halt and ask or confirm with the user.
 
 3. **Checklist Processing**
 
    If in interactive mode:
-
    - Work through each section of the checklist one at a time
    - For each section:
      - Review all items in the section following instructions for that section embedded in the checklist
@@ -347,7 +344,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
      - Get user confirmation before proceeding to next section or if any thing major do we need to halt and take corrective action
 
    If in YOLO mode:
-
    - Process all sections at once
    - Create a comprehensive report of all findings
    - Present the complete analysis to the user
@@ -355,7 +351,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
 4. **Validation Approach**
 
    For each checklist item:
-
    - Read and understand the requirement
    - Look for evidence in the documentation that satisfies the requirement
    - Consider both explicit mentions and implicit coverage
@@ -369,7 +364,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
 5. **Section Analysis**
 
    For each section:
-
    - think step by step to calculate pass rate
    - Identify common themes in failed items
    - Provide specific recommendations for improvement
@@ -379,7 +373,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
 6. **Final Report**
 
    Prepare a summary that includes:
-
    - Overall checklist completion status
    - Pass rates by section
    - List of failed items with context
@@ -419,13 +412,13 @@ sections:
   - id: initial-setup
     instruction: |
       This template creates detailed game development stories that are immediately actionable by game developers. Each story should focus on a single, implementable feature that contributes to the overall game functionality.
-      
+
       Before starting, ensure you have access to:
-      
+
       - Game Design Document (GDD)
       - Game Architecture Document
       - Any existing stories in this epic
-      
+
       The story should be specific enough that a developer can implement it without requiring additional design decisions.
 
   - id: story-header
@@ -474,12 +467,12 @@ sections:
         title: Files to Create/Modify
         template: |
           **New Files:**
-          
+
           - `{{file_path_1}}` - {{purpose}}
           - `{{file_path_2}}` - {{purpose}}
-          
+
           **Modified Files:**
-          
+
           - `{{existing_file_1}}` - {{changes_needed}}
           - `{{existing_file_2}}` - {{changes_needed}}
       - id: class-interface-definitions
@@ -494,15 +487,15 @@ sections:
               {{property_2}}: {{type}};
               {{method_1}}({{params}}): {{return_type}};
           }
-          
+
           // {{class_name}}
           class {{class_name}} extends {{phaser_class}} {
               private {{property}}: {{type}};
-          
+
               constructor({{params}}) {
                   // Implementation requirements
               }
-          
+
               public {{method}}({{params}}): {{return_type}} {
                   // Method requirements
               }
@@ -512,15 +505,15 @@ sections:
         instruction: Specify how this feature integrates with existing systems
         template: |
           **Scene Integration:**
-          
+
           - {{scene_name}}: {{integration_details}}
-          
+
           **System Dependencies:**
-          
+
           - {{system_name}}: {{dependency_description}}
-          
+
           **Event Communication:**
-          
+
           - Emits: `{{event_name}}` when {{condition}}
           - Listens: `{{event_name}}` to {{response}}
 
@@ -532,7 +525,7 @@ sections:
         title: Dev Agent Record
         template: |
           **Tasks:**
-          
+
           - [ ] {{task_1_description}}
           - [ ] {{task_2_description}}
           - [ ] {{task_3_description}}
@@ -540,18 +533,18 @@ sections:
           - [ ] Write unit tests for {{component}}
           - [ ] Integration testing with {{related_system}}
           - [ ] Performance testing and optimization
-          
+
           **Debug Log:**
           | Task | File | Change | Reverted? |
           |------|------|--------|-----------|
           | | | | |
-          
+
           **Completion Notes:**
-          
+
           <!-- Only note deviations from requirements, keep under 50 words -->
-          
+
           **Change Log:**
-          
+
           <!-- Only requirement changes during implementation -->
 
   - id: game-design-context
@@ -559,13 +552,13 @@ sections:
     instruction: Reference the specific sections of the GDD that this story implements
     template: |
       **GDD Reference:** {{section_name}} ({{page_or_section_number}})
-      
+
       **Game Mechanic:** {{mechanic_name}}
-      
+
       **Player Experience Goal:** {{experience_description}}
-      
+
       **Balance Parameters:**
-      
+
       - {{parameter_1}}: {{value_or_range}}
       - {{parameter_2}}: {{value_or_range}}
 
@@ -577,11 +570,11 @@ sections:
         title: Unit Tests
         template: |
           **Test Files:**
-          
+
           - `tests/{{component_name}}.test.ts`
-          
+
           **Test Scenarios:**
-          
+
           - {{test_scenario_1}}
           - {{test_scenario_2}}
           - {{edge_case_test}}
@@ -589,12 +582,12 @@ sections:
         title: Game Testing
         template: |
           **Manual Test Cases:**
-          
+
           1. {{test_case_1_description}}
-          
+
              - Expected: {{expected_behavior}}
              - Performance: {{performance_expectation}}
-          
+
           2. {{test_case_2_description}}
              - Expected: {{expected_behavior}}
              - Edge Case: {{edge_case_handling}}
@@ -602,7 +595,7 @@ sections:
         title: Performance Tests
         template: |
           **Metrics to Verify:**
-          
+
           - Frame rate maintains {{fps_target}} FPS
           - Memory usage stays under {{memory_limit}}MB
           - {{feature_specific_performance_metric}}
@@ -612,15 +605,15 @@ sections:
     instruction: List any dependencies that must be completed before this story can be implemented
     template: |
       **Story Dependencies:**
-      
+
       - {{story_id}}: {{dependency_description}}
-      
+
       **Technical Dependencies:**
-      
+
       - {{system_or_file}}: {{requirement}}
-      
+
       **Asset Dependencies:**
-      
+
       - {{asset_type}}: {{asset_description}}
       - Location: `{{asset_path}}`
 
@@ -643,17 +636,17 @@ sections:
     instruction: Any additional context, design decisions, or implementation notes
     template: |
       **Implementation Notes:**
-      
+
       - {{note_1}}
       - {{note_2}}
-      
+
       **Design Decisions:**
-      
+
       - {{decision_1}}: {{rationale}}
       - {{decision_2}}: {{rationale}}
-      
+
       **Future Considerations:**
-      
+
       - {{future_enhancement_1}}
       - {{future_optimization_1}}
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================