# Feature Link <!-- Written by: Project Manager or Product Owner --> <!-- Each story should belong to a bigger Feature. --> <!-- Link or reference the Feature this story is part of. --> <!-- Example: --> <!-- Feature #15: User Authentication System --> --- # Description <!-- Written by: Stakeholder or Product Owner --> <!-- A user story is written from the perspective of the user. --> <!-- Use the standard format: --> <!-- "As a [role], I want [goal] so that [benefit]." --> <!-- Example: --> <!-- "As a user, I want to reset my password so that I can regain access to my account." --> --- # Requirement (Acceptance Criteria) - Holds HP - Holds resource count - Holds position (might later be stored on board information) - Movement (stubbed out) - Damage calculated from board (stubbed out) --- # Definition of Done <!-- Written by: The Development Team --> <!-- This section ensures clarity on what it means for the story to be “done.” --> <!-- Usually includes coding, testing, documentation, and deployment requirements. --> <!-- Example: --> <!-- - Code has been reviewed and merged --> <!-- - Unit tests written and passed --> <!-- - End-to-end tests passed --> <!-- - Deployed to staging environment --> --- # Complexity Score (Story Pointing) (Optional) <!-- Written by: Development Team during Sprint Planning --> <!-- Assign a score (using story points, T-shirt sizes, or Fibonacci scale). --> <!-- Story points reflect complexity, uncertainty, and effort — NOT hours. --> <!-- Example: --> <!-- - 1 point = very small (simple UI change) --> <!-- - 3 points = medium (backend logic, some testing) --> <!-- - 8 points = complex (new API integration, multiple edge cases) --> --- # Dependency Links <!-- Written by: Project Manager or Scrum Master --> <!-- What does this story depend on? Other stories, features, or external systems? --> <!-- Example: --> <!-- - Feature #15: Authentication System --> <!-- - Story #18: Email Notification Service --> --- # Notes <!-- Open to anyone on the team. --> <!-- Use this for extra details, risks, questions, or clarifications. --> <!-- Example Notes: --> <!-- - Coordinate with QA for token expiration testing --> <!-- - Ensure the password reset link works across mobile and desktop -->
Feature Link
Description
Requirement (Acceptance Criteria)
Definition of Done
Complexity Score (Story Pointing) (Optional)
Dependency Links
Notes