bmad-elsabro 1.0.0

package/src/bmm/workflows/parallel-work/sprint-mode/steps/step-06-sprint-report.md

@@ -0,0 +1,290 @@
+---
+name: step-06-sprint-report
+description: Generate comprehensive sprint execution report
+---
+
+# Step 6: Sprint Report
+
+## OBJECTIVE
+
+Generate a comprehensive report summarizing the entire sprint execution, results, and next steps.
+
+## EXECUTION
+
+### 1. Gather All Data
+
+Collect from previous steps:
+- Sprint manifest (step 1)
+- Execution plan (step 2)
+- Story execution results (step 3)
+- Code review findings (step 4)
+- Integration test results (step 5)
+
+### 2. Calculate Metrics
+
+```yaml
+sprint_metrics:
+  # Time metrics
+  total_duration: "4h 32m"
+  sequential_estimate: "12h"
+  actual_speedup: "2.6x"
+
+  # Story metrics
+  total_stories: 8
+  completed: 7
+  failed: 1
+  success_rate: "87.5%"
+
+  # Quality metrics
+  tests_written: 45
+  test_coverage: "82%"
+  code_review_issues: 12
+  critical_issues: 1
+
+  # Efficiency metrics
+  avg_story_time: "34m"
+  parallel_efficiency: "78%"
+  retry_count: 2
+```
+
+### 3. Generate Sprint Report
+
+Create report at `{implementation_artifacts}/sprint-report-{date}.md`:
+
+```markdown
+# Sprint Report
+
+## Executive Summary
+
+| Metric | Value |
+|--------|-------|
+| Sprint ID | SPRINT-2024-01-15 |
+| Duration | 4h 32m |
+| Stories Completed | 7/8 (87.5%) |
+| Test Coverage | 82% |
+| Speedup vs Sequential | 2.6x |
+
+---
+
+## Story Results
+
+| Story | Title | Status | Duration | Tests |
+|-------|-------|--------|----------|-------|
+| STORY-001 | User Authentication | Completed | 45m | 15/15 |
+| STORY-002 | API Endpoints | Completed | 38m | 12/12 |
+| STORY-003 | Dashboard UI | Completed | 52m | 18/18 |
+| STORY-004 | Data Export | Completed | 28m | 8/8 |
+| STORY-005 | Notifications | Completed | 35m | 10/10 |
+| STORY-006 | Settings Page | Completed | 22m | 6/6 |
+| STORY-007 | Search Feature | Completed | 41m | 14/14 |
+| STORY-008 | Reporting | Failed | - | - |
+
+---
+
+## Execution Timeline
+
+```
+Wave 1 (Parallel): [STORY-001, STORY-002, STORY-004]
+  Started: 09:00 | Completed: 09:45 | Duration: 45m
+
+Wave 2 (Parallel): [STORY-003, STORY-005, STORY-006]
+  Started: 09:45 | Completed: 10:37 | Duration: 52m
+
+Wave 3 (Parallel): [STORY-007, STORY-008]
+  Started: 10:37 | Completed: 11:18 | Duration: 41m
+  Note: STORY-008 failed after 2 retries
+```
+
+---
+
+## Failed Stories
+
+### STORY-008: Reporting Module
+
+**Error:** Integration test failed - Unable to connect to reporting service
+
+**Attempts:** 3 (1 initial + 2 retries)
+
+**Root Cause:** External service dependency not available in test environment
+
+**Recommended Action:**
+- Add mock for reporting service
+- Retry implementation with proper mocking
+- Consider adding circuit breaker pattern
+
+---
+
+## Code Quality
+
+### Review Summary
+- Files Reviewed: 42
+- Issues Found: 12
+- Auto-Fixed: 9
+- Manual Review Needed: 3
+
+### Critical Issues
+1. **src/auth/token.ts:89** - Token not properly invalidated on logout
+   - Status: Flagged for manual fix
+
+### Code Metrics
+- Average function length: 24 lines
+- Cyclomatic complexity (avg): 4.2
+- Documentation coverage: 68%
+
+---
+
+## Test Results
+
+### Summary
+| Suite | Passed | Failed | Skipped |
+|-------|--------|--------|---------|
+| Unit | 156 | 0 | 0 |
+| Integration | 24 | 0 | 2 |
+| E2E | 12 | 0 | 0 |
+
+### Coverage by Module
+| Module | Line | Branch | Function |
+|--------|------|--------|----------|
+| Auth | 92% | 85% | 95% |
+| API | 88% | 80% | 90% |
+| UI | 75% | 70% | 82% |
+| Utils | 95% | 90% | 98% |
+
+---
+
+## Performance
+
+### API Response Times
+- p50: 45ms
+- p95: 120ms
+- p99: 250ms
+
+### Resource Usage
+- Peak Memory: 312MB
+- Avg CPU: 45%
+- Database Connections: 8 (peak)
+
+---
+
+## Recommendations
+
+### Immediate Actions
+1. Fix critical token invalidation issue in auth module
+2. Manually review STORY-008 failure and re-implement
+3. Address 3 code review issues flagged for manual review
+
+### Future Improvements
+1. Add mocks for external services to improve test reliability
+2. Consider increasing test coverage for UI module (currently 75%)
+3. Implement circuit breaker pattern for external dependencies
+
+---
+
+## Sprint Velocity
+
+| Sprint | Stories | Points | Duration |
+|--------|---------|--------|----------|
+| Current | 7/8 | 21/24 | 4h 32m |
+| Previous | 6/6 | 18/18 | 6h 15m |
+| Delta | +17% | +17% | -28% |
+
+---
+
+## Files Changed
+
+**Total:** 42 files
+
+### By Type
+- Source (`.ts`): 28 files
+- Tests (`.test.ts`): 12 files
+- Config (`.yaml`, `.json`): 2 files
+
+### Key Files
+- `src/auth/login.ts` - New authentication flow
+- `src/api/routes.ts` - API endpoint definitions
+- `src/components/Dashboard.tsx` - Dashboard UI
+
+---
+
+## Next Steps
+
+1. [ ] Review and fix failed story (STORY-008)
+2. [ ] Address critical code review issue
+3. [ ] Merge completed stories to main branch
+4. [ ] Deploy to staging environment
+5. [ ] Plan next sprint
+
+---
+
+*Report generated automatically by Sprint Mode*
+*Duration: 4h 32m | Completed: 2024-01-15 11:18*
+```
+
+### 4. Save Sprint Status
+
+Update final sprint status:
+
+```yaml
+# sprint-status.yaml
+sprint_id: "SPRINT-2024-01-15"
+status: "completed"
+completed_at: "2024-01-15T11:18:00Z"
+duration: "4h 32m"
+
+summary:
+  total_stories: 8
+  completed: 7
+  failed: 1
+  success_rate: "87.5%"
+
+stories:
+  - id: "STORY-001"
+    status: "completed"
+    duration: "45m"
+  # ... all stories
+
+code_review:
+  issues_found: 12
+  critical: 1
+  resolved: 9
+
+testing:
+  total_tests: 192
+  passed: 190
+  coverage: "82%"
+
+report_path: "sprint-report-2024-01-15.md"
+```
+
+### 5. Output Summary
+
+Display final summary to user:
+
+```
+╔══════════════════════════════════════════════════════════╗
+║                    SPRINT COMPLETE                       ║
+╠══════════════════════════════════════════════════════════╣
+║  Stories: 7/8 completed (87.5%)                          ║
+║  Duration: 4h 32m (2.6x faster than sequential)          ║
+║  Tests: 190 passed, 82% coverage                         ║
+║  Code Review: 1 critical issue needs attention           ║
+╠══════════════════════════════════════════════════════════╣
+║  Report: {implementation_artifacts}/sprint-report.md     ║
+║  Status: {implementation_artifacts}/sprint-status.yaml   ║
+╚══════════════════════════════════════════════════════════╝
+
+Action Required:
+  1. Fix critical issue in src/auth/token.ts
+  2. Review failed story: STORY-008
+  3. Merge to main when ready
+```
+
+## WORKFLOW COMPLETE
+
+Sprint executed automatically. Full report generated.
+
+The user can now:
+- Review the detailed report
+- Address failed stories manually
+- Merge successful work to main branch
+- Plan the next sprint

package/src/bmm/workflows/parallel-work/sprint-mode/workflow.md

@@ -0,0 +1,58 @@
+---
+name: sprint-mode
+description: 'Auto-execute entire sprint of stories without intervention'
+---
+
+# Sprint Mode Workflow
+
+**Goal:** Execute an ENTIRE SPRINT automatically. Set it and forget it.
+
+**Use Case:** You have a well-defined epic with stories. Let the system implement them all.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for sprint execution:
+
+- Step 1: Load sprint and analyze stories
+- Step 2: Plan execution order with dependencies
+- Step 3: Auto-execute stories (parallel where possible)
+- Step 4: Run code reviews
+- Step 5: Integration testing
+- Step 6: Generate sprint report
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+- `user_name`, `communication_language`, `user_skill_level`
+- `output_folder`, `implementation_artifacts`
+
+### Sprint Settings
+
+```yaml
+sprint_config:
+  mode: "auto"
+  stop_on_error: false
+  retry_failed: true
+  max_retries: 2
+  parallel_stories: true
+  code_review_mode: "auto"
+```
+
+### Paths
+
+- `installed_path` = `{project-root}/_bmad/bmm/workflows/parallel-work/sprint-mode`
+- `sprint_status` = `{implementation_artifacts}/sprint-status.yaml`
+- `stories_path` = `{implementation_artifacts}/stories/`
+
+---
+
+## EXECUTION
+
+Read fully and follow: `steps/step-01-load-sprint.md` to begin the workflow.

package/src/bmm/workflows/testarch/atdd/atdd-checklist-template.md

@@ -0,0 +1,363 @@
+# ATDD Checklist - Epic {epic_num}, Story {story_num}: {story_title}
+
+**Date:** {date}
+**Author:** {user_name}
+**Primary Test Level:** {primary_level}
+
+---
+
+## Story Summary
+
+{Brief 2-3 sentence summary of the user story}
+
+**As a** {user_role}
+**I want** {feature_description}
+**So that** {business_value}
+
+---
+
+## Acceptance Criteria
+
+{List all testable acceptance criteria from the story}
+
+1. {Acceptance criterion 1}
+2. {Acceptance criterion 2}
+3. {Acceptance criterion 3}
+
+---
+
+## Failing Tests Created (RED Phase)
+
+### E2E Tests ({e2e_test_count} tests)
+
+**File:** `{e2e_test_file_path}` ({line_count} lines)
+
+{List each E2E test with its current status and expected failure reason}
+
+- ✅ **Test:** {test_name}
+  - **Status:** RED - {failure_reason}
+  - **Verifies:** {what_this_test_validates}
+
+### API Tests ({api_test_count} tests)
+
+**File:** `{api_test_file_path}` ({line_count} lines)
+
+{List each API test with its current status and expected failure reason}
+
+- ✅ **Test:** {test_name}
+  - **Status:** RED - {failure_reason}
+  - **Verifies:** {what_this_test_validates}
+
+### Component Tests ({component_test_count} tests)
+
+**File:** `{component_test_file_path}` ({line_count} lines)
+
+{List each component test with its current status and expected failure reason}
+
+- ✅ **Test:** {test_name}
+  - **Status:** RED - {failure_reason}
+  - **Verifies:** {what_this_test_validates}
+
+---
+
+## Data Factories Created
+
+{List all data factory files created with their exports}
+
+### {Entity} Factory
+
+**File:** `tests/support/factories/{entity}.factory.ts`
+
+**Exports:**
+
+- `create{Entity}(overrides?)` - Create single entity with optional overrides
+- `create{Entity}s(count)` - Create array of entities
+
+**Example Usage:**
+
+```typescript
+const user = createUser({ email: 'specific@example.com' });
+const users = createUsers(5); // Generate 5 random users
+```
+
+---
+
+## Fixtures Created
+
+{List all test fixture files created with their fixture names and descriptions}
+
+### {Feature} Fixtures
+
+**File:** `tests/support/fixtures/{feature}.fixture.ts`
+
+**Fixtures:**
+
+- `{fixtureName}` - {description_of_what_fixture_provides}
+  - **Setup:** {what_setup_does}
+  - **Provides:** {what_test_receives}
+  - **Cleanup:** {what_cleanup_does}
+
+**Example Usage:**
+
+```typescript
+import { test } from './fixtures/{feature}.fixture';
+
+test('should do something', async ({ {fixtureName} }) => {
+  // {fixtureName} is ready to use with auto-cleanup
+});
+```
+
+---
+
+## Mock Requirements
+
+{Document external services that need mocking and their requirements}
+
+### {Service Name} Mock
+
+**Endpoint:** `{HTTP_METHOD} {endpoint_url}`
+
+**Success Response:**
+
+```json
+{
+  {success_response_example}
+}
+```
+
+**Failure Response:**
+
+```json
+{
+  {failure_response_example}
+}
+```
+
+**Notes:** {any_special_mock_requirements}
+
+---
+
+## Required data-testid Attributes
+
+{List all data-testid attributes required in UI implementation for test stability}
+
+### {Page or Component Name}
+
+- `{data-testid-name}` - {description_of_element}
+- `{data-testid-name}` - {description_of_element}
+
+**Implementation Example:**
+
+```tsx
+<button data-testid="login-button">Log In</button>
+<input data-testid="email-input" type="email" />
+<div data-testid="error-message">{errorText}</div>
+```
+
+---
+
+## Implementation Checklist
+
+{Map each failing test to concrete implementation tasks that will make it pass}
+
+### Test: {test_name_1}
+
+**File:** `{test_file_path}`
+
+**Tasks to make this test pass:**
+
+- [ ] {Implementation task 1}
+- [ ] {Implementation task 2}
+- [ ] {Implementation task 3}
+- [ ] Add required data-testid attributes: {list_of_testids}
+- [ ] Run test: `{test_execution_command}`
+- [ ] ✅ Test passes (green phase)
+
+**Estimated Effort:** {effort_estimate} hours
+
+---
+
+### Test: {test_name_2}
+
+**File:** `{test_file_path}`
+
+**Tasks to make this test pass:**
+
+- [ ] {Implementation task 1}
+- [ ] {Implementation task 2}
+- [ ] {Implementation task 3}
+- [ ] Add required data-testid attributes: {list_of_testids}
+- [ ] Run test: `{test_execution_command}`
+- [ ] ✅ Test passes (green phase)
+
+**Estimated Effort:** {effort_estimate} hours
+
+---
+
+## Running Tests
+
+```bash
+# Run all failing tests for this story
+{test_command_all}
+
+# Run specific test file
+{test_command_specific_file}
+
+# Run tests in headed mode (see browser)
+{test_command_headed}
+
+# Debug specific test
+{test_command_debug}
+
+# Run tests with coverage
+{test_command_coverage}
+```
+
+---
+
+## Red-Green-Refactor Workflow
+
+### RED Phase (Complete) ✅
+
+**TEA Agent Responsibilities:**
+
+- ✅ All tests written and failing
+- ✅ Fixtures and factories created with auto-cleanup
+- ✅ Mock requirements documented
+- ✅ data-testid requirements listed
+- ✅ Implementation checklist created
+
+**Verification:**
+
+- All tests run and fail as expected
+- Failure messages are clear and actionable
+- Tests fail due to missing implementation, not test bugs
+
+---
+
+### GREEN Phase (DEV Team - Next Steps)
+
+**DEV Agent Responsibilities:**
+
+1. **Pick one failing test** from implementation checklist (start with highest priority)
+2. **Read the test** to understand expected behavior
+3. **Implement minimal code** to make that specific test pass
+4. **Run the test** to verify it now passes (green)
+5. **Check off the task** in implementation checklist
+6. **Move to next test** and repeat
+
+**Key Principles:**
+
+- One test at a time (don't try to fix all at once)
+- Minimal implementation (don't over-engineer)
+- Run tests frequently (immediate feedback)
+- Use implementation checklist as roadmap
+
+**Progress Tracking:**
+
+- Check off tasks as you complete them
+- Share progress in daily standup
+
+---
+
+### REFACTOR Phase (DEV Team - After All Tests Pass)
+
+**DEV Agent Responsibilities:**
+
+1. **Verify all tests pass** (green phase complete)
+2. **Review code for quality** (readability, maintainability, performance)
+3. **Extract duplications** (DRY principle)
+4. **Optimize performance** (if needed)
+5. **Ensure tests still pass** after each refactor
+6. **Update documentation** (if API contracts change)
+
+**Key Principles:**
+
+- Tests provide safety net (refactor with confidence)
+- Make small refactors (easier to debug if tests fail)
+- Run tests after each change
+- Don't change test behavior (only implementation)
+
+**Completion:**
+
+- All tests pass
+- Code quality meets team standards
+- No duplications or code smells
+- Ready for code review and story approval
+
+---
+
+## Next Steps
+
+1. **Share this checklist and failing tests** with the dev workflow (manual handoff)
+2. **Review this checklist** with team in standup or planning
+3. **Run failing tests** to confirm RED phase: `{test_command_all}`
+4. **Begin implementation** using implementation checklist as guide
+5. **Work one test at a time** (red → green for each)
+6. **Share progress** in daily standup
+7. **When all tests pass**, refactor code for quality
+8. **When refactoring complete**, manually update story status to 'done' in sprint-status.yaml
+
+---
+
+## Knowledge Base References Applied
+
+This ATDD workflow consulted the following knowledge fragments:
+
+- **fixture-architecture.md** - Test fixture patterns with setup/teardown and auto-cleanup using Playwright's `test.extend()`
+- **data-factories.md** - Factory patterns using `@faker-js/faker` for random test data generation with overrides support
+- **component-tdd.md** - Component test strategies using Playwright Component Testing
+- **network-first.md** - Route interception patterns (intercept BEFORE navigation to prevent race conditions)
+- **test-quality.md** - Test design principles (Given-When-Then, one assertion per test, determinism, isolation)
+- **test-levels-framework.md** - Test level selection framework (E2E vs API vs Component vs Unit)
+
+See `tea-index.csv` for complete knowledge fragment mapping.
+
+---
+
+## Test Execution Evidence
+
+### Initial Test Run (RED Phase Verification)
+
+**Command:** `{test_command_all}`
+
+**Results:**
+
+```
+{paste_test_run_output_showing_all_tests_failing}
+```
+
+**Summary:**
+
+- Total tests: {total_test_count}
+- Passing: 0 (expected)
+- Failing: {total_test_count} (expected)
+- Status: ✅ RED phase verified
+
+**Expected Failure Messages:**
+{list_expected_failure_messages_for_each_test}
+
+---
+
+## Notes
+
+{Any additional notes, context, or special considerations for this story}
+
+- {Note 1}
+- {Note 2}
+- {Note 3}
+
+---
+
+## Contact
+
+**Questions or Issues?**
+
+- Ask in team standup
+- Tag @{tea_agent_username} in Slack/Discord
+- Refer to `./bmm/docs/tea-README.md` for workflow documentation
+- Consult `./bmm/testarch/knowledge` for testing best practices
+
+---
+
+**Generated by BMad TEA Agent** - {date}