bmad-method 4.43.0 → 4.44.0

package/expansion-packs/bmad-godot-game-dev/tasks/game-design-brainstorming.md

@@ -0,0 +1,290 @@
+# Game Design Brainstorming Techniques Task
+
+This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
+
+## Process
+
+### 1. Session Setup
+
+[[LLM: Begin by understanding the game design context and goals. Ask clarifying questions if needed to determine the best approach for game-specific ideation.]]
+
+1. **Establish Game Context**
+   - Understand the game genre or opportunity area
+   - Identify target audience and platform constraints
+   - Determine session goals (concept exploration vs. mechanic refinement)
+   - Clarify scope (full game vs. specific feature)
+
+2. **Select Technique Approach**
+   - Option A: User selects specific game design techniques
+   - Option B: Game Designer recommends techniques based on context
+   - Option C: Random technique selection for creative variety
+   - Option D: Progressive technique flow (broad concepts to specific mechanics)
+
+### 2. Game Design Brainstorming Techniques
+
+#### Game Concept Expansion Techniques
+
+1. **"What If" Game Scenarios**
+   [[LLM: Generate provocative what-if questions that challenge game design assumptions and expand thinking beyond current genre limitations.]]
+   - What if players could rewind time in any genre?
+   - What if the game world reacted to the player's real-world location?
+   - What if failure was more rewarding than success?
+   - What if players controlled the antagonist instead?
+   - What if the game played itself when no one was watching?
+
+2. **Cross-Genre Fusion**
+   [[LLM: Help user combine unexpected game genres and mechanics to create unique experiences.]]
+   - "How might [genre A] mechanics work in [genre B]?"
+   - Puzzle mechanics in action games
+   - Dating sim elements in strategy games
+   - Horror elements in racing games
+   - Educational content in roguelike structure
+
+3. **Player Motivation Reversal**
+   [[LLM: Flip traditional player motivations to reveal new gameplay possibilities.]]
+   - What if losing was the goal?
+   - What if cooperation was forced in competitive games?
+   - What if players had to help their enemies?
+   - What if progress meant giving up abilities?
+
+4. **Core Loop Deconstruction**
+   [[LLM: Break down successful games to fundamental mechanics and rebuild differently.]]
+   - What are the essential 3 actions in this game type?
+   - How could we make each action more interesting?
+   - What if we changed the order of these actions?
+   - What if players could skip or automate certain actions?
+
+#### Mechanic Innovation Frameworks
+
+1. **SCAMPER for Game Mechanics**
+   [[LLM: Guide through each SCAMPER prompt specifically for game design.]]
+   - **S** = Substitute: What mechanics can be substituted? (walking → flying → swimming)
+   - **C** = Combine: What systems can be merged? (inventory + character growth)
+   - **A** = Adapt: What mechanics from other media? (books, movies, sports)
+   - **M** = Modify/Magnify: What can be exaggerated? (super speed, massive scale)
+   - **P** = Put to other uses: What else could this mechanic do? (jumping → attacking)
+   - **E** = Eliminate: What can be removed? (UI, tutorials, fail states)
+   - **R** = Reverse/Rearrange: What sequence changes? (end-to-start, simultaneous)
+
+2. **Player Agency Spectrum**
+   [[LLM: Explore different levels of player control and agency across game systems.]]
+   - Full Control: Direct character movement, combat, building
+   - Indirect Control: Setting rules, giving commands, environmental changes
+   - Influence Only: Suggestions, preferences, emotional reactions
+   - No Control: Observation, interpretation, passive experience
+
+3. **Temporal Game Design**
+   [[LLM: Explore how time affects gameplay and player experience.]]
+   - Real-time vs. turn-based mechanics
+   - Time travel and manipulation
+   - Persistent vs. session-based progress
+   - Asynchronous multiplayer timing
+   - Seasonal and event-based content
+
+#### Player Experience Ideation
+
+1. **Emotion-First Design**
+   [[LLM: Start with target emotions and work backward to mechanics that create them.]]
+   - Target Emotion: Wonder → Mechanics: Discovery, mystery, scale
+   - Target Emotion: Triumph → Mechanics: Challenge, skill growth, recognition
+   - Target Emotion: Connection → Mechanics: Cooperation, shared goals, communication
+   - Target Emotion: Flow → Mechanics: Clear feedback, progressive difficulty
+
+2. **Player Archetype Brainstorming**
+   [[LLM: Design for different player types and motivations.]]
+   - Achievers: Progression, completion, mastery
+   - Explorers: Discovery, secrets, world-building
+   - Socializers: Interaction, cooperation, community
+   - Killers: Competition, dominance, conflict
+   - Creators: Building, customization, expression
+
+3. **Accessibility-First Innovation**
+   [[LLM: Generate ideas that make games more accessible while creating new gameplay.]]
+   - Visual impairment considerations leading to audio-focused mechanics
+   - Motor accessibility inspiring one-handed or simplified controls
+   - Cognitive accessibility driving clear feedback and pacing
+   - Economic accessibility creating free-to-play innovations
+
+#### Narrative and World Building
+
+1. **Environmental Storytelling**
+   [[LLM: Brainstorm ways the game world itself tells stories without explicit narrative.]]
+   - How does the environment show history?
+   - What do interactive objects reveal about characters?
+   - How can level design communicate mood?
+   - What stories do systems and mechanics tell?
+
+2. **Player-Generated Narrative**
+   [[LLM: Explore ways players create their own stories through gameplay.]]
+   - Emergent storytelling through player choices
+   - Procedural narrative generation
+   - Player-to-player story sharing
+   - Community-driven world events
+
+3. **Genre Expectation Subversion**
+   [[LLM: Identify and deliberately subvert player expectations within genres.]]
+   - Fantasy RPG where magic is mundane
+   - Horror game where monsters are friendly
+   - Racing game where going slow is optimal
+   - Puzzle game where there are multiple correct answers
+
+#### Technical Innovation Inspiration
+
+1. **Platform-Specific Design**
+   [[LLM: Generate ideas that leverage unique platform capabilities.]]
+   - Mobile: GPS, accelerometer, camera, always-connected
+   - Web: URLs, tabs, social sharing, real-time collaboration
+   - Console: Controllers, TV viewing, couch co-op
+   - VR/AR: Physical movement, spatial interaction, presence
+
+2. **Constraint-Based Creativity**
+   [[LLM: Use technical or design constraints as creative catalysts.]]
+   - One-button games
+   - Games without graphics
+   - Games that play in notification bars
+   - Games using only system sounds
+   - Games with intentionally bad graphics
+
+### 3. Game-Specific Technique Selection
+
+[[LLM: Help user select appropriate techniques based on their specific game design needs.]]
+
+**For Initial Game Concepts:**
+
+- What If Game Scenarios
+- Cross-Genre Fusion
+- Emotion-First Design
+
+**For Stuck/Blocked Creativity:**
+
+- Player Motivation Reversal
+- Constraint-Based Creativity
+- Genre Expectation Subversion
+
+**For Mechanic Development:**
+
+- SCAMPER for Game Mechanics
+- Core Loop Deconstruction
+- Player Agency Spectrum
+
+**For Player Experience:**
+
+- Player Archetype Brainstorming
+- Emotion-First Design
+- Accessibility-First Innovation
+
+**For World Building:**
+
+- Environmental Storytelling
+- Player-Generated Narrative
+- Platform-Specific Design
+
+### 4. Game Design Session Flow
+
+[[LLM: Guide the brainstorming session with appropriate pacing for game design exploration.]]
+
+1. **Inspiration Phase** (10-15 min)
+   - Reference existing games and mechanics
+   - Explore player experiences and emotions
+   - Gather visual and thematic inspiration
+
+2. **Divergent Exploration** (25-35 min)
+   - Generate many game concepts or mechanics
+   - Use expansion and fusion techniques
+   - Encourage wild and impossible ideas
+
+3. **Player-Centered Filtering** (15-20 min)
+   - Consider target audience reactions
+   - Evaluate emotional impact and engagement
+   - Group ideas by player experience goals
+
+4. **Feasibility and Synthesis** (15-20 min)
+   - Assess technical and design feasibility
+   - Combine complementary ideas
+   - Develop most promising concepts
+
+### 5. Game Design Output Format
+
+[[LLM: Present brainstorming results in a format useful for game development.]]
+
+**Session Summary:**
+
+- Techniques used and focus areas
+- Total concepts/mechanics generated
+- Key themes and patterns identified
+
+**Game Concept Categories:**
+
+1. **Core Game Ideas** - Complete game concepts ready for prototyping
+2. **Mechanic Innovations** - Specific gameplay mechanics to explore
+3. **Player Experience Goals** - Emotional and engagement targets
+4. **Technical Experiments** - Platform or technology-focused concepts
+5. **Long-term Vision** - Ambitious ideas for future development
+
+**Development Readiness:**
+
+**Prototype-Ready Ideas:**
+
+- Ideas that can be tested immediately
+- Minimum viable implementations
+- Quick validation approaches
+
+**Research-Required Ideas:**
+
+- Concepts needing technical investigation
+- Player testing and market research needs
+- Competitive analysis requirements
+
+**Future Innovation Pipeline:**
+
+- Ideas requiring significant development
+- Technology-dependent concepts
+- Market timing considerations
+
+**Next Steps:**
+
+- Which concepts to prototype first
+- Recommended research areas
+- Suggested playtesting approaches
+- Documentation and GDD planning
+
+## Game Design Specific Considerations
+
+### Platform and Audience Awareness
+
+- Always consider target platform limitations and advantages
+- Keep target audience preferences and expectations in mind
+- Balance innovation with familiar game design patterns
+- Consider monetization and business model implications
+
+### Rapid Prototyping Mindset
+
+- Focus on ideas that can be quickly tested
+- Emphasize core mechanics over complex features
+- Design for iteration and player feedback
+- Consider digital and paper prototyping approaches
+
+### Player Psychology Integration
+
+- Understand motivation and engagement drivers
+- Consider learning curves and skill development
+- Design for different play session lengths
+- Balance challenge and reward appropriately
+
+### Technical Feasibility
+
+- Keep development resources and timeline in mind
+- Consider art and audio asset requirements
+- Think about performance and optimization needs
+- Plan for testing and debugging complexity
+
+## Important Notes for Game Design Sessions
+
+- Encourage "impossible" ideas - constraints can be added later
+- Build on game mechanics that have proven engagement
+- Consider how ideas scale from prototype to full game
+- Document player experience goals alongside mechanics
+- Think about community and social aspects of gameplay
+- Consider accessibility and inclusivity from the start
+- Balance innovation with market viability
+- Plan for iteration based on player feedback

package/expansion-packs/bmad-godot-game-dev/tasks/game-risk-profile.md

@@ -0,0 +1,368 @@
+<!-- Powered by BMAD™ Core -->
+
+# game-risk-profile
+
+Generate a comprehensive risk assessment matrix for a Godot game story implementation using probability × impact analysis focused on game development challenges.
+
+## Inputs
+
+```yaml
+required:
+  - story_id: '{epic}.{story}' # e.g., "1.3"
+  - story_path: 'docs/stories/{epic}.{story}.*.md'
+  - story_title: '{title}' # If missing, derive from story file H1
+  - story_slug: '{slug}' # If missing, derive from title (lowercase, hyphenated)
+```
+
+## Purpose
+
+Identify, assess, and prioritize risks in Godot game feature implementation. Provide risk mitigation strategies and playtesting focus areas based on game development risk levels.
+
+## Risk Assessment Framework
+
+### Risk Categories
+
+**Category Prefixes:**
+
+- `TECH`: Technical/Engine Risks
+- `PERF`: Performance/Optimization Risks
+- `GAME`: Gameplay/Mechanics Risks
+- `ART`: Art/Asset Pipeline Risks
+- `PLAT`: Platform/Deployment Risks
+- `PLAY`: Player Experience Risks
+
+1. **Technical/Engine Risks (TECH)**
+   - Godot version compatibility issues
+   - GDScript/C# integration problems
+   - Node tree architecture complexity
+   - Signal connection failures
+   - Plugin/addon conflicts
+   - Memory leak in scene transitions
+
+2. **Performance/Optimization Risks (PERF)**
+   - Frame rate drops below 60 FPS
+   - Draw call bottlenecks
+   - Physics engine slowdowns
+   - Particle system overload
+   - Texture memory exhaustion
+   - Shader compilation spikes
+
+3. **Gameplay/Mechanics Risks (GAME)**
+   - Game balance issues
+   - Control responsiveness problems
+   - Collision detection failures
+   - AI behavior bugs
+   - Progression breaking bugs
+   - Save/load system corruption
+
+4. **Art/Asset Pipeline Risks (ART)**
+   - Asset import failures
+   - Texture atlas overflow
+   - Animation sync issues
+   - Audio streaming problems
+   - Font rendering issues
+   - Sprite batching failures
+
+5. **Platform/Deployment Risks (PLAT)**
+   - Export template issues
+   - Platform-specific bugs
+   - Mobile performance degradation
+   - Web build compatibility
+   - Console certification failures
+   - Steam/itch.io integration problems
+
+6. **Player Experience Risks (PLAY)**
+   - Tutorial unclear or broken
+   - Difficulty curve too steep/shallow
+   - Multiplayer desync issues
+   - Achievements not triggering
+   - Localization text overflow
+   - Accessibility features missing
+
+## Risk Analysis Process
+
+### 1. Risk Identification
+
+For each category, identify specific risks:
+
+```yaml
+risk:
+  id: 'PERF-001' # Use prefixes: TECH, PERF, GAME, ART, PLAT, PLAY
+  category: performance
+  title: 'Particle system causing frame drops in boss battle'
+  description: 'Multiple particle emitters active during boss fight drops FPS below 30'
+  affected_components:
+    - 'BossArena.tscn'
+    - 'ParticleManager.gd'
+    - 'BossAttackEffects'
+  detection_method: 'Profiler showed 80% GPU usage on particles'
+```
+
+### 2. Risk Assessment
+
+Evaluate each risk using probability × impact:
+
+**Probability Levels:**
+
+- `High (3)`: Likely to occur (>70% chance)
+- `Medium (2)`: Possible occurrence (30-70% chance)
+- `Low (1)`: Unlikely to occur (<30% chance)
+
+**Impact Levels:**
+
+- `High (3)`: Severe consequences (game unplayable, save corruption, platform rejection)
+- `Medium (2)`: Moderate consequences (noticeable lag, minor bugs, progression issues)
+- `Low (1)`: Minor consequences (visual glitches, UI issues, quality of life problems)
+
+### Risk Score = Probability × Impact
+
+- 9: Critical Risk (Red)
+- 6: High Risk (Orange)
+- 4: Medium Risk (Yellow)
+- 2-3: Low Risk (Green)
+- 1: Minimal Risk (Blue)
+
+### 3. Risk Prioritization
+
+Create risk matrix:
+
+```markdown
+## Risk Matrix
+
+| Risk ID  | Description                  | Probability | Impact     | Score | Priority |
+| -------- | ---------------------------- | ----------- | ---------- | ----- | -------- |
+| GAME-001 | Boss fight progression block | High (3)    | High (3)   | 9     | Critical |
+| PERF-001 | Particle FPS drops           | Medium (2)  | Medium (2) | 4     | Medium   |
+| PLAT-001 | Mobile export crashes        | Low (1)     | High (3)   | 3     | Low      |
+```
+
+### 4. Risk Mitigation Strategies
+
+For each identified risk, provide mitigation:
+
+```yaml
+mitigation:
+  risk_id: 'PERF-001'
+  strategy: 'preventive' # preventive|detective|corrective
+  actions:
+    - 'Implement particle pooling system'
+    - 'Add LOD (Level of Detail) for particle effects'
+    - 'Use GPU particles instead of CPU particles'
+    - 'Limit max particle count per emitter'
+  testing_requirements:
+    - 'Performance profiling on min spec hardware'
+    - 'Stress test with all effects active'
+    - 'FPS monitoring during boss encounters'
+  residual_risk: 'Low - May still drop to 45 FPS on very low-end devices'
+  owner: 'game-dev'
+  timeline: 'Before beta release'
+```
+
+## Outputs
+
+### Output 1: Gate YAML Block
+
+Generate for pasting into gate file under `risk_summary`:
+
+**Output rules:**
+
+- Only include assessed risks; do not emit placeholders
+- Sort risks by score (desc) when emitting highest and any tabular lists
+- If no risks: totals all zeros, omit highest, keep recommendations arrays empty
+
+```yaml
+# risk_summary (paste into gate file):
+risk_summary:
+  totals:
+    critical: X # score 9
+    high: Y # score 6
+    medium: Z # score 4
+    low: W # score 2-3
+  highest:
+    id: GAME-001
+    score: 9
+    title: 'Boss fight progression blocker'
+  recommendations:
+    must_fix:
+      - 'Fix collision detection in boss arena'
+    monitor:
+      - 'Track FPS metrics during gameplay'
+```
+
+### Output 2: Markdown Report
+
+**Save to:** `qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md`
+
+```markdown
+# Risk Profile: Story {epic}.{story}
+
+Date: {date}
+Reviewer: Linus (Test Architect)
+
+## Executive Summary
+
+- Total Risks Identified: X
+- Critical Risks: Y
+- High Risks: Z
+- Risk Score: XX/100 (calculated)
+
+## Critical Risks Requiring Immediate Attention
+
+### 1. [ID]: Risk Title
+
+**Score: 9 (Critical)**
+**Probability**: High - Detailed reasoning
+**Impact**: High - Potential consequences
+**Mitigation**:
+
+- Immediate action required
+- Specific steps to take
+  **Testing Focus**: Specific test scenarios needed
+
+## Risk Distribution
+
+### By Category
+
+- Technical/Engine: X risks (Y critical)
+- Performance: X risks (Y critical)
+- Gameplay: X risks (Y critical)
+- Art/Assets: X risks (Y critical)
+- Platform: X risks (Y critical)
+- Player Experience: X risks (Y critical)
+
+### By Component
+
+- Game Scenes: X risks
+- Player Controller: X risks
+- Enemy AI: X risks
+- UI/Menus: X risks
+- Audio System: X risks
+- Save System: X risks
+
+## Detailed Risk Register
+
+[Full table of all risks with scores and mitigations]
+
+## Risk-Based Testing Strategy
+
+### Priority 1: Critical Risk Tests
+
+- Playtesting scenarios for game-breaking bugs
+- Performance testing on target platforms
+- Save/load integrity testing
+- Multiplayer stress testing (if applicable)
+
+### Priority 2: High Risk Tests
+
+- Integration test scenarios
+- Edge case coverage
+
+### Priority 3: Medium/Low Risk Tests
+
+- Standard functional tests
+- Regression test suite
+
+## Risk Acceptance Criteria
+
+### Must Fix Before Production
+
+- All critical risks (score 9)
+- High risks affecting security/data
+
+### Can Deploy with Mitigation
+
+- Medium risks with compensating controls
+- Low risks with monitoring in place
+
+### Accepted Risks
+
+- Document any risks team accepts
+- Include sign-off from appropriate authority
+
+## Monitoring Requirements
+
+Post-release monitoring for:
+
+- Frame rate metrics and performance stats
+- Crash reports and error logs
+- Player progression analytics
+- Achievement completion rates
+- Player retention metrics
+
+## Risk Review Triggers
+
+Review and update risk profile when:
+
+- Major gameplay mechanics added
+- New platforms targeted
+- Godot engine version upgraded
+- Performance issues reported by playtesters
+- Art style or asset pipeline changes
+- Multiplayer features added
+```
+
+## Risk Scoring Algorithm
+
+Calculate overall story risk score:
+
+```text
+Base Score = 100
+For each risk:
+  - Critical (9): Deduct 20 points
+  - High (6): Deduct 10 points
+  - Medium (4): Deduct 5 points
+  - Low (2-3): Deduct 2 points
+
+Minimum score = 0 (extremely risky)
+Maximum score = 100 (minimal risk)
+```
+
+## Risk-Based Recommendations
+
+Based on risk profile, recommend:
+
+1. **Testing Priority**
+   - Which tests to run first
+   - Additional test types needed
+   - Test environment requirements
+
+2. **Development Focus**
+   - Code review emphasis areas
+   - Additional validation needed
+   - Security controls to implement
+
+3. **Deployment Strategy**
+   - Phased rollout for high-risk changes
+   - Feature flags for risky features
+   - Rollback procedures
+
+4. **Monitoring Setup**
+   - Metrics to track
+   - Alerts to configure
+   - Dashboard requirements
+
+## Integration with Quality Gates
+
+**Deterministic gate mapping:**
+
+- Any risk with score ≥ 9 → Gate = FAIL (unless waived)
+- Else if any score ≥ 6 → Gate = CONCERNS
+- Else → Gate = PASS
+- Unmitigated risks → Document in gate
+
+### Output 3: Story Hook Line
+
+**Print this line for review task to quote:**
+
+```text
+Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
+```
+
+## Key Principles
+
+- Identify risks early and systematically
+- Use consistent probability × impact scoring
+- Provide actionable mitigation strategies
+- Link risks to specific test requirements
+- Track residual risk after mitigation
+- Update risk profile as story evolves