# Description <!-- This section is usually filled in by the **Stakeholder** or **Project Manager**. --> <!-- A feature is a **large, high-level functionality** that adds value to the product. --> <!-- Features are often too big to be completed in a single sprint and will be broken down into smaller user stories. --> <!-- Write a clear description of the feature in plain English. Think of the “big picture.” --> <!-- Example: --> <!-- “Add User Authentication System” --> <!-- This would include everything needed for sign-up, login, password reset, and account management. --> --- # Requirements - Create a board with a movable player - Card with options - Player with HP and location --- # Tech Refinements <!-- This is usually filled in by the **Developers** or **Architects**. --> <!-- Notes about how this feature might be implemented. --> <!-- Can include tools, frameworks, libraries, or specific technical design considerations. --> <!-- Example: --> <!-- - Use OAuth2 for secure login --> <!-- - Store passwords with bcrypt hashing --> <!-- - Use PostgreSQL database to store user credentials --> --- # Dependency Links <!-- This is often written by the **Project Manager** or **Scrum Master** because they know the overall scope of the project --> <!-- Features rarely stand alone. What other features or stories must exist FIRST before this feature can work? --> <!-- Example: --> <!-- - Feature #15: Backend API for authentication --> <!-- - Feature #22: Frontend login form --> <!-- - External dependency: Email service for password reset --> --- # Notes <!-- Anyone on the team can contribute here. --> <!-- Use this section for additional details that don’t fit neatly elsewhere: reminders, risks, design notes, open questions. --> <!-- Example: --> <!-- - Coordinate with frontend team for form design --> <!-- - Ensure mobile responsiveness --> <!-- - Security review required before release -->
