---
name: Implementation and Verification
description: Implement the fix, verify resolution, and test for regressions
next_step: null
---

## Step 02: Implementation and Verification

### Objective
Implement the root cause fix identified in step-01, verify the resolution, and ensure no regressions.

### 4. RESEARCH: Solution Investigation (inline or websearch)

If root cause needs further research:

- Use `WebSearch` inline for targeted solution search
- Check documentation for affected libraries/frameworks
- Look for known bugs, workarounds, and best practices
- **THINK**: Evaluate solution approaches for this specific context

### 5. IMPLEMENT: Systematic Resolution

#### Implementation Strategy

- Choose the most appropriate solution based on analysis
- Follow existing codebase patterns and conventions
- Implement minimal, targeted fixes
- **STAY IN SCOPE**: Fix only what's needed for this specific bug
- Add defensive programming where appropriate

#### Implementation Rules

- **Minimal changes**: Fix root cause, not symptoms
- **Pattern matching**: Follow existing codebase conventions
- **No scope creep**: Only address the identified bug
- **Defensive programming**: Add guards for edge cases
- **Documentation**: Comment on non-obvious fixes

### 6. VERIFY: Comprehensive Testing

#### Testing Strategy

- Test the specific scenario that was failing
- Run related tests to ensure no regressions
- Check edge cases around the fix
- **CRITICAL**: Verify the original error is completely resolved

#### Test Checklist

- [ ] Original error scenario reproduced and verified as fixed
- [ ] Related unit tests pass
- [ ] Integration tests (if applicable) pass
- [ ] Edge cases around the fix tested
- [ ] Regressions checked in related code
- [ ] Fix behavior validated in different environments (if applicable)

### Execution Rules

- **NEVER guess** — validate all fixes with evidence
- **MINIMAL CHANGES**: Fix root cause, not symptoms
- Test thoroughly before declaring resolution complete
- **ALWAYS cleanup**: shutdown teammates + TeamDelete after investigation (from step-01)

### Priority

Understanding > Speed > Completeness. Every fix must be fully understood before declaring complete.

### Success Criteria

- Root cause identified with evidence (not just symptoms)
- Fix implemented with minimal, targeted changes
- Original error no longer reproducible
- Related tests pass without regressions
- Team properly shut down (no orphan agents from step-01)

### Completion Checklist

- [ ] Root cause from step-01 fully understood
- [ ] Solution approach documented and justified
- [ ] Fix implemented following codebase patterns
- [ ] Original error scenario verified as resolved
- [ ] Regression testing completed
- [ ] Edge cases tested
- [ ] Team agents shut down (if used in step-01)
- [ ] Resolution documented
