bmad-method 5.1.3 → 6.0.0-Beta.1

package/expansion-packs/bmad-2d-unity-game-dev/checklists/game-design-checklist.md

@@ -1,201 +0,0 @@
-# Game Design Document Quality Checklist
-
-## Document Completeness
-
-### Executive Summary
-
-- [ ] **Core Concept** - Game concept is clearly explained in 2-3 sentences
-- [ ] **Target Audience** - Primary and secondary audiences defined with demographics
-- [ ] **Platform Requirements** - Technical platforms and requirements specified
-- [ ] **Unique Selling Points** - 3-5 key differentiators from competitors identified
-- [ ] **Technical Foundation** - Unity & C# requirements confirmed
-
-### Game Design Foundation
-
-- [ ] **Game Pillars** - 3-5 core design pillars defined and actionable
-- [ ] **Core Gameplay Loop** - 30-60 second loop documented with specific timings
-- [ ] **Win/Loss Conditions** - Clear victory and failure states defined
-- [ ] **Player Motivation** - Clear understanding of why players will engage
-- [ ] **Scope Realism** - Game scope is achievable with available resources
-
-## Gameplay Mechanics
-
-### Core Mechanics Documentation
-
-- [ ] **Primary Mechanics** - 3-5 core mechanics detailed with implementation notes
-- [ ] **Mechanic Integration** - How mechanics work together is clear
-- [ ] **Player Input** - All input methods specified for each platform
-- [ ] **System Responses** - Game responses to player actions documented
-- [ ] **Performance Impact** - Performance considerations for each mechanic noted
-
-### Controls and Interaction
-
-- [ ] **Multi-Platform Controls** - Desktop, mobile, and gamepad controls defined
-- [ ] **Input Responsiveness** - Requirements for responsive game feel specified
-- [ ] **Accessibility Options** - Control customization and accessibility considered
-- [ ] **Touch Optimization** - Mobile-specific control adaptations designed
-- [ ] **Edge Case Handling** - Unusual input scenarios addressed
-
-## Progression and Balance
-
-### Player Progression
-
-- [ ] **Progression Type** - Linear, branching, or metroidvania approach defined
-- [ ] **Key Milestones** - Major progression points documented
-- [ ] **Unlock System** - What players unlock and when is specified
-- [ ] **Difficulty Scaling** - How challenge increases over time is detailed
-- [ ] **Player Agency** - Meaningful player choices and consequences defined
-
-### Game Balance
-
-- [ ] **Balance Parameters** - Numeric values for key game systems provided
-- [ ] **Difficulty Curve** - Appropriate challenge progression designed
-- [ ] **Economy Design** - Resource systems balanced for engagement
-- [ ] **Player Testing** - Plan for validating balance through playtesting
-- [ ] **Iteration Framework** - Process for adjusting balance post-implementation
-
-## Level Design Framework
-
-### Level Structure
-
-- [ ] **Level Types** - Different level categories defined with purposes
-- [ ] **Level Progression** - How players move through levels specified
-- [ ] **Duration Targets** - Expected play time for each level type
-- [ ] **Difficulty Distribution** - Appropriate challenge spread across levels
-- [ ] **Replay Value** - Elements that encourage repeated play designed
-
-### Content Guidelines
-
-- [ ] **Level Creation Rules** - Clear guidelines for level designers
-- [ ] **Mechanic Introduction** - How new mechanics are taught in levels
-- [ ] **Pacing Variety** - Mix of action, puzzle, and rest moments planned
-- [ ] **Secret Content** - Hidden areas and optional challenges designed
-- [ ] **Accessibility Options** - Multiple difficulty levels or assist modes considered
-
-## Technical Implementation Readiness
-
-### Performance Requirements
-
-- [ ] **Frame Rate Targets** - Stable FPS target with minimum acceptable rates
-- [ ] **Memory Budgets** - Maximum memory usage limits defined
-- [ ] **Load Time Goals** - Acceptable loading times for different content
-- [ ] **Battery Optimization** - Mobile battery usage considerations addressed
-- [ ] **Scalability Plan** - How performance scales across different devices
-
-### Platform Specifications
-
-- [ ] **Desktop Requirements** - Minimum and recommended PC/Mac specs
-- [ ] **Mobile Optimization** - iOS and Android specific requirements
-- [ ] **Browser Compatibility** - Supported browsers and versions listed
-- [ ] **Cross-Platform Features** - Shared and platform-specific features identified
-- [ ] **Update Strategy** - Plan for post-launch updates and patches
-
-### Asset Requirements
-
-- [ ] **Art Style Definition** - Clear visual style with reference materials
-- [ ] **Asset Specifications** - Technical requirements for all asset types
-- [ ] **Audio Requirements** - Music and sound effect specifications
-- [ ] **UI/UX Guidelines** - User interface design principles established
-- [ ] **Localization Plan** - Text and cultural localization requirements
-
-## Development Planning
-
-### Implementation Phases
-
-- [ ] **Phase Breakdown** - Development divided into logical phases
-- [ ] **Epic Definitions** - Major development epics identified
-- [ ] **Dependency Mapping** - Prerequisites between features documented
-- [ ] **Risk Assessment** - Technical and design risks identified with mitigation
-- [ ] **Milestone Planning** - Key deliverables and deadlines established
-
-### Team Requirements
-
-- [ ] **Role Definitions** - Required team roles and responsibilities
-- [ ] **Skill Requirements** - Technical skills needed for implementation
-- [ ] **Resource Allocation** - Time and effort estimates for major features
-- [ ] **External Dependencies** - Third-party tools, assets, or services needed
-- [ ] **Communication Plan** - How team members will coordinate work
-
-## Quality Assurance
-
-### Success Metrics
-
-- [ ] **Technical Metrics** - Measurable technical performance goals
-- [ ] **Gameplay Metrics** - Player engagement and retention targets
-- [ ] **Quality Benchmarks** - Standards for bug rates and polish level
-- [ ] **User Experience Goals** - Specific UX objectives and measurements
-- [ ] **Business Objectives** - Commercial or project success criteria
-
-### Testing Strategy
-
-- [ ] **Playtesting Plan** - How and when player feedback will be gathered
-- [ ] **Technical Testing** - Performance and compatibility testing approach
-- [ ] **Balance Validation** - Methods for confirming game balance
-- [ ] **Accessibility Testing** - Plan for testing with diverse players
-- [ ] **Iteration Process** - How feedback will drive design improvements
-
-## Documentation Quality
-
-### Clarity and Completeness
-
-- [ ] **Clear Writing** - All sections are well-written and understandable
-- [ ] **Complete Coverage** - No major game systems left undefined
-- [ ] **Actionable Detail** - Enough detail for developers to create implementation stories
-- [ ] **Consistent Terminology** - Game terms used consistently throughout
-- [ ] **Reference Materials** - Links to inspiration, research, and additional resources
-
-### Maintainability
-
-- [ ] **Version Control** - Change log established for tracking revisions
-- [ ] **Update Process** - Plan for maintaining document during development
-- [ ] **Team Access** - All team members can access and reference the document
-- [ ] **Search Functionality** - Document organized for easy reference and searching
-- [ ] **Living Document** - Process for incorporating feedback and changes
-
-## Stakeholder Alignment
-
-### Team Understanding
-
-- [ ] **Shared Vision** - All team members understand and agree with the game vision
-- [ ] **Role Clarity** - Each team member understands their contribution
-- [ ] **Decision Framework** - Process for making design decisions during development
-- [ ] **Conflict Resolution** - Plan for resolving disagreements about design choices
-- [ ] **Communication Channels** - Regular meetings and feedback sessions planned
-
-### External Validation
-
-- [ ] **Market Validation** - Competitive analysis and market fit assessment
-- [ ] **Technical Validation** - Feasibility confirmed with technical team
-- [ ] **Resource Validation** - Required resources available and committed
-- [ ] **Timeline Validation** - Development schedule is realistic and achievable
-- [ ] **Quality Validation** - Quality standards align with available time and resources
-
-## Final Readiness Assessment
-
-### Implementation Preparedness
-
-- [ ] **Story Creation Ready** - Document provides sufficient detail for story creation
-- [ ] **Architecture Alignment** - Game design aligns with technical capabilities
-- [ ] **Asset Production** - Asset requirements enable art and audio production
-- [ ] **Development Workflow** - Clear path from design to implementation
-- [ ] **Quality Assurance** - Testing and validation processes established
-
-### Document Approval
-
-- [ ] **Design Review Complete** - Document reviewed by all relevant stakeholders
-- [ ] **Technical Review Complete** - Technical feasibility confirmed
-- [ ] **Business Review Complete** - Project scope and goals approved
-- [ ] **Final Approval** - Document officially approved for implementation
-- [ ] **Baseline Established** - Current version established as development baseline
-
-## Overall Assessment
-
-**Document Quality Rating:** ⭐⭐⭐⭐⭐
-
-**Ready for Development:** [ ] Yes [ ] No
-
-**Key Recommendations:**
-_List any critical items that need attention before moving to implementation phase._
-
-**Next Steps:**
-_Outline immediate next actions for the team based on this assessment._

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

@@ -1,124 +0,0 @@
-# Game Development Story Definition of Done (DoD) Checklist
-
-## Instructions for Developer Agent
-
-Before marking a story as 'Review', please go through each item in this checklist. Report the status of each item (e.g., [x] Done, [ ] Not Done, [N/A] Not Applicable) and provide brief comments if necessary.
-
-[[LLM: INITIALIZATION INSTRUCTIONS - GAME STORY DOD VALIDATION
-
-This checklist is for GAME DEVELOPER AGENTS to self-validate their work before marking a story complete.
-
-IMPORTANT: This is a self-assessment. Be honest about what's actually done vs what should be done. It's better to identify issues now than have them found in review.
-
-EXECUTION APPROACH:
-
-1. Go through each section systematically
-2. Mark items as [x] Done, [ ] Not Done, or [N/A] Not Applicable
-3. Add brief comments explaining any [ ] or [N/A] items
-4. Be specific about what was actually implemented
-5. Flag any concerns or technical debt created
-
-The goal is quality delivery, not just checking boxes.]]
-
-## Checklist Items
-
-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.
-   - [ ] Player experience goals specified in the story are achieved.
-
-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.
-   - [ ] Adherence to `Api Reference` and `Data Models` (if story involves API or data model changes).
-   - [ ] Unity best practices followed (prefab usage, component design, event handling).
-   - [ ] C# coding standards followed (naming conventions, error handling, memory management).
-   - [ ] Basic security best practices applied for new/modified code.
-   - [ ] No new linter errors or warnings introduced.
-   - [ ] Code is well-commented where necessary (clarifying complex logic, not obvious statements).
-
-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.
-   - [ ] All tests (unit, integration, manual) pass successfully.
-   - [ ] Test coverage meets project standards (if defined).
-   - [ ] Performance tests conducted (frame rate, memory usage).
-   - [ ] Edge cases and error conditions tested.
-
-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.
-   - [ ] UI elements function properly (if applicable).
-   - [ ] Audio integration works correctly (if applicable).
-   - [ ] Visual feedback and animations work as intended.
-   - [ ] Edge cases and potential error conditions handled gracefully.
-   - [ ] Cross-platform functionality verified (desktop/mobile as applicable).
-
-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).
-   - [ ] The story wrap up section has been completed with notes of changes.
-   - [ ] Changelog properly updated with Unity version and package changes.
-
-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.
-   - [ ] If new dependencies were added, they are recorded with justification.
-   - [ ] No known security vulnerabilities in newly added dependencies.
-   - [ ] Project settings and configurations properly updated.
-   - [ ] Asset import settings optimized for target platforms.
-
-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.
-   - [ ] Balance parameters from GDD correctly implemented.
-   - [ ] State management and persistence work correctly.
-   - [ ] Loading times and scene transitions acceptable.
-   - [ ] Mobile-specific requirements met (touch controls, aspect ratios).
-
-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.
-   - [ ] Technical documentation (architecture, system diagrams) updated.
-   - [ ] Asset documentation (prefab usage, scene setup) complete.
-
-## Final Confirmation
-
-[[LLM: FINAL GAME DOD SUMMARY
-
-After completing the checklist:
-
-1. Summarize what game features/mechanics were implemented
-2. List any items marked as [ ] Not Done with explanations
-3. Identify any technical debt or performance concerns
-4. Note any challenges with Unity implementation or game design
-5. Confirm whether the story is truly ready for review
-6. Report final performance metrics (FPS, memory usage)
-
-Be honest - it's better to flag issues now than have them discovered during playtesting.]]
-
-- [ ] I, the Game Developer Agent, confirm that all applicable items above have been addressed.

package/expansion-packs/bmad-2d-unity-game-dev/config.yaml

@@ -1,6 +0,0 @@
-name: bmad-2d-unity-game-dev
-version: 1.5.0
-short-title: Unity C# 2D Game Dev Pack
-description: 2D Game Development expansion pack for BMad Method - Unity & C# focused
-author: pbean (PinkyD)
-slashPrefix: bmad2du