# 📘 Sprint Implementation Guidelines (Improved) These enhanced guidelines define how the AI agent must implement a Sprint based on the approved **Sprint Playbook**. They ensure consistent execution, comprehensive testing, proactive risk management, and optimal user collaboration. --- ## 0. Key Definitions (Enhanced) **Logical Unit of Work (LUW)**: A single, cohesive code change that: - Implements one specific functionality or fixes one specific issue - Can be described in 1-2 sentences with clear before/after behavior - Passes all relevant tests and quality gates - Can be committed independently without breaking the system - Takes 30-90 minutes of focused implementation time **Testing Checkpoint**: A mandatory pause where AI provides specific test instructions to user: - Clear step-by-step test procedures - Expected behavior descriptions - Pass/fail criteria - What to look for (visual, functional, performance) - How to report issues or failures **Blocked Status (`🚫 blocked`)**: A user story cannot proceed due to: - Missing external dependencies that cannot be mocked/simulated - Conflicting requirements discovered during implementation - Failed tests that require domain knowledge to resolve - Technical limitations requiring architecture decisions - User input needed for UX/business logic decisions **Iterative Refinement**: Process of making improvements based on user testing: - User reports specific issues or improvement requests - AI analyzes feedback and proposes solutions - Implementation of fixes follows same LUW/commit pattern - Re-testing until user confirms satisfaction --- ## 1. Enhanced Git & Version Control Rules ### 1.1 Commit Granularity (Refined) **MANDATORY COMMIT PATTERNS:** * **Feature Implementation**: One LUW per commit * **Test Addition**: Included in same commit as feature (not separate) * **Documentation Updates**: Included in same commit as related code changes * **Bug Fixes**: One fix per commit with clear reproduction steps in message * **Refactoring**: Separate commits, no functional changes mixed in **COMMIT QUALITY CRITERIA:** * Build passes after each commit * Tests pass after each commit * No temporary/debug code included * All related files updated (tests, docs, types) ### 1.2 Commit Message Style (Enhanced) **STRICT FORMAT:** ``` (scope):