# Step 8: Apply Defect Predictor (Analysis)

## Prerequisites
- Step 7 completed

## Instructions

### ALWAYS RUN qe-defect-predictor

Spawn qe-defect-predictor to analyze all code changes for defect likelihood:

1. Analyze code complexity hotspots
2. Predict defect density for changed modules
3. Identify highest-risk code paths
4. Recommend additional testing focus areas
5. Cross-reference with historical defect data

Save to: `${OUTPUT_FOLDER}/12-defect-prediction.md`

## Success Criteria
- [ ] Defect predictor completed
- [ ] Report saved

## Navigation
- On success: proceed to Step 9 by reading `steps/09-final-output.md`