BusyBee

--- description: Resume TddBee autonomous work from checkpoint --- # Resume TddBee You are resuming the TddBee autonomous TDD work from a previous session. ## CRITICAL RULES - Same as /tddbee:run - **NEVER modify acceptance criteria** - They are the contract - **One feature at a time** - Complete before moving on - **Actually RUN tests** - Don't just inspect code ## Session Startup Sequence 1. **Confirm working directory** - Run `pwd` 2. **Read state files**: - `.tddbee/features.json` - the feature list (DO NOT MODIFY criteria) - `.tddbee/config.json` - current state - `.tddbee/progress.md` - what was done in previous sessions 3. **Check git history** - Run `git log --oneline -10` to understand recent work 4. **Run existing tests** - Ensure nothing is broken before continuing: ``` # Run full test suite # All tests should pass before starting new work ``` 5. **Find where to resume**: - If `current_feature` is set in config, that feature was in-progress - Otherwise, find first feature where `completed: false` 6. **Report status to user**: - Progress: X/Y completed (Z%) - Next feature to work on - Any tests currently failing ## Continue with TDD Follow the same TDD cycle as `/tddbee:run`: 1. Update status FIRST (set `current_feature`) 2. READ Acceptance Criteria - Display the criteria from features.json 3. RED - Write failing tests for acceptance criteria 4. GREEN - Minimal code to pass 5. REFACTOR - Clean up, keep tests green 6. VERIFY - Run ALL tests, document each criterion passing 7. Complete - Set `completed: true`, commit, update progress.md 8. Continue to next feature ## Session Handoff Review `.tddbee/progress.md` to understand: - What was completed in previous sessions - Any notes or context from the previous agent - Current state of the project This is like a shift handoff - review what the previous engineer did before starting your work. ## Notes - Works after `/tddbee:pause` or starting fresh session - State is preserved in `.tddbee/` files - Git history provides additional context