5d81c75f4d
* Added 1.0 files * Converted agents, and templates to new format. Updated filenames to include extensions like in unity-2d-game-team.yaml, Updated some wordage in workflow, config, and increased minor version number * Forgot to remove unused startup section in game-sm since it's moved to activation-instructions, now fixed. * Updated verbosity for development workflow in development-guidenlines.md * built the web-dist files for the expansion pack * Synched with main repo and rebuilt dist * Added enforcement of game-design-checklist to designer persona * Updated with new changes to phaser epack that seem relevant to discussion we had on discord for summarizing documentation updates * updated dist build for our epack
161 lines
7.8 KiB
Markdown
161 lines
7.8 KiB
Markdown
# Game Development Story Definition of Done Checklist
|
|
|
|
## Story Completeness
|
|
|
|
### Basic Story Elements
|
|
|
|
- [ ] **Story Title** - Clear, descriptive title that identifies the feature
|
|
- [ ] **Epic Assignment** - Story is properly assigned to relevant epic
|
|
- [ ] **Priority Level** - Appropriate priority assigned (High/Medium/Low)
|
|
- [ ] **Story Points** - Realistic estimation for implementation complexity
|
|
- [ ] **Description** - Clear, concise description of what needs to be implemented
|
|
|
|
### Game Design Alignment
|
|
|
|
- [ ] **GDD Reference** - Specific Game Design Document section referenced
|
|
- [ ] **Game Mechanic Context** - Clear connection to game mechanics defined in GDD
|
|
- [ ] **Player Experience Goal** - Describes the intended player experience
|
|
- [ ] **Balance Parameters** - Includes any relevant game balance values
|
|
- [ ] **Design Intent** - Purpose and rationale for the feature is clear
|
|
|
|
## Technical Specifications
|
|
|
|
### Architecture Compliance
|
|
|
|
- [ ] **File Organization** - Follows game architecture document structure (e.g., scripts, prefabs, scenes)
|
|
- [ ] **Class Definitions** - C# classes and interfaces are properly defined
|
|
- [ ] **Integration Points** - Clear specification of how feature integrates with existing systems
|
|
- [ ] **Event Communication** - UnityEvents or C# events usage specified
|
|
- [ ] **Dependencies** - All system dependencies clearly identified
|
|
|
|
### Unity Requirements
|
|
|
|
- [ ] **Scene Integration** - Specifies which scenes are affected and how
|
|
- [ ] **Prefab Usage** - Proper use of prefabs for reusable GameObjects
|
|
- [ ] **Component Design** - Logic is encapsulated in well-defined MonoBehaviour components
|
|
- [ ] **Asset Requirements** - All needed assets (sprites, audio, materials) identified
|
|
- [ ] **Performance Considerations** - Stable frame rate target and optimization requirements
|
|
|
|
### Code Quality Standards
|
|
|
|
- [ ] **C# Best Practices** - All code must comply with modern C# standards
|
|
- [ ] **Error Handling** - Error scenarios and handling requirements specified
|
|
- [ ] **Memory Management** - Coroutine and object lifecycle management requirements where needed
|
|
- [ ] **Cross-Platform Support** - Desktop and mobile considerations addressed
|
|
- [ ] **Code Organization** - Follows established Unity project structure
|
|
|
|
## Implementation Readiness
|
|
|
|
### Acceptance Criteria
|
|
|
|
- [ ] **Functional Requirements** - All functional acceptance criteria are specific and testable
|
|
- [ ] **Technical Requirements** - Technical acceptance criteria are complete and verifiable
|
|
- [ ] **Game Design Requirements** - Game-specific requirements match GDD specifications
|
|
- [ ] **Performance Requirements** - Frame rate and memory usage criteria specified
|
|
- [ ] **Completeness** - No acceptance criteria are vague or unmeasurable
|
|
|
|
### Implementation Tasks
|
|
|
|
- [ ] **Task Breakdown** - Story broken into specific, ordered implementation tasks
|
|
- [ ] **Task Scope** - Each task is completable in 1-4 hours
|
|
- [ ] **Task Clarity** - Each task has clear, actionable instructions
|
|
- [ ] **File Specifications** - Exact file paths and purposes specified (e.g., `Scripts/Player/PlayerMovement.cs`)
|
|
- [ ] **Development Flow** - Tasks follow logical implementation order
|
|
|
|
### Dependencies
|
|
|
|
- [ ] **Story Dependencies** - All prerequisite stories identified with IDs
|
|
- [ ] **Technical Dependencies** - Required systems and files identified
|
|
- [ ] **Asset Dependencies** - All needed assets specified with locations
|
|
- [ ] **External Dependencies** - Any third-party or external requirements noted (e.g., Asset Store packages)
|
|
- [ ] **Dependency Validation** - All dependencies are actually available
|
|
|
|
## Testing Requirements
|
|
|
|
### Test Coverage
|
|
|
|
- [ ] **Unit Test Requirements** - Specific unit test files and scenarios defined for NUnit
|
|
- [ ] **Integration Test Cases** - Integration testing with other game systems specified
|
|
- [ ] **Manual Test Cases** - Game-specific manual testing procedures defined in the Unity Editor
|
|
- [ ] **Performance Tests** - Frame rate and memory testing requirements specified
|
|
- [ ] **Edge Case Testing** - Edge cases and error conditions covered
|
|
|
|
### Test Implementation
|
|
|
|
- [ ] **Test File Paths** - Exact test file locations specified (e.g., `Assets/Tests/EditMode`)
|
|
- [ ] **Test Scenarios** - All test scenarios are complete and executable
|
|
- [ ] **Expected Behaviors** - Clear expected outcomes for all tests defined
|
|
- [ ] **Performance Metrics** - Specific performance targets for testing
|
|
- [ ] **Test Data** - Any required test data or mock objects specified
|
|
|
|
## Game-Specific Quality
|
|
|
|
### Gameplay Implementation
|
|
|
|
- [ ] **Mechanic Accuracy** - Implementation matches GDD mechanic specifications
|
|
- [ ] **Player Controls** - Input handling requirements are complete (e.g., Input System package)
|
|
- [ ] **Game Feel** - Requirements for juice, feedback, and responsiveness specified
|
|
- [ ] **Balance Implementation** - Numeric values and parameters from GDD included
|
|
- [ ] **State Management** - Game state changes and persistence requirements defined
|
|
|
|
### User Experience
|
|
|
|
- [ ] **UI Requirements** - User interface elements and behaviors specified (e.g., UI Toolkit or UGUI)
|
|
- [ ] **Audio Integration** - Sound effect and music requirements defined
|
|
- [ ] **Visual Feedback** - Animation and visual effect requirements specified (e.g., Animator, Particle System)
|
|
- [ ] **Accessibility** - Mobile touch and responsive design considerations
|
|
- [ ] **Error Recovery** - User-facing error handling and recovery specified
|
|
|
|
### Performance Optimization
|
|
|
|
- [ ] **Frame Rate Targets** - Specific FPS requirements for different platforms
|
|
- [ ] **Memory Usage** - Memory consumption limits and monitoring requirements (e.g., Profiler)
|
|
- [ ] **Asset Optimization** - Texture, audio, and data optimization requirements
|
|
- [ ] **Mobile Considerations** - Touch controls and mobile performance requirements
|
|
- [ ] **Loading Performance** - Asset loading and scene transition requirements
|
|
|
|
## Documentation and Communication
|
|
|
|
### Story Documentation
|
|
|
|
- [ ] **Implementation Notes** - Additional context and implementation guidance provided
|
|
- [ ] **Design Decisions** - Key design choices documented with rationale
|
|
- [ ] **Future Considerations** - Potential future enhancements or modifications noted
|
|
- [ ] **Change Tracking** - Process for tracking any requirement changes during development
|
|
- [ ] **Reference Materials** - Links to relevant GDD sections and architecture docs
|
|
|
|
### Developer Handoff
|
|
|
|
- [ ] **Immediate Actionability** - Developer can start implementation without additional questions
|
|
- [ ] **Complete Context** - All necessary context provided within the story
|
|
- [ ] **Clear Boundaries** - What is and isn't included in the story scope is clear
|
|
- [ ] **Success Criteria** - Objective measures for story completion defined
|
|
- [ ] **Communication Plan** - Process for developer questions and updates established
|
|
|
|
## Final Validation
|
|
|
|
### Story Readiness
|
|
|
|
- [ ] **No Ambiguity** - No sections require interpretation or additional design decisions
|
|
- [ ] **Technical Completeness** - All technical requirements are specified and actionable
|
|
- [ ] **Scope Appropriateness** - Story scope matches assigned story points
|
|
- [ ] **Quality Standards** - Story meets all game development quality standards
|
|
- [ ] **Review Completion** - Story has been reviewed for completeness and accuracy
|
|
|
|
### Implementation Preparedness
|
|
|
|
- [ ] **Environment Ready** - Development environment requirements specified (e.g., Unity version)
|
|
- [ ] **Resources Available** - All required resources (assets, docs, dependencies) accessible
|
|
- [ ] **Testing Prepared** - Testing environment and data requirements specified
|
|
- [ ] **Definition of Done** - Clear, objective completion criteria established
|
|
- [ ] **Handoff Complete** - Story is ready for developer assignment and implementation
|
|
|
|
## Checklist Completion
|
|
|
|
**Overall Story Quality:** ⭐⭐⭐⭐⭐
|
|
|
|
**Ready for Development:** [ ] Yes [ ] No
|
|
|
|
**Additional Notes:**
|
|
_Any specific concerns, recommendations, or clarifications needed before development begins._
|