Goal
Use semantic review signals from pr_monitor (approval patterns, reviewer sentiment, coverage gaps) to route debugging work and trigger follow-up tasks when merged PRs have low confidence or quality flags.
Success Criteria
- Task dispatcher can query pr_monitor review signals for merged PRs
- Planner adjusts follow-up task priority based on review concerns
- At least 1 follow-up per sprint auto-created from review signals
- No false-positive follow-ups; signals must have >80% precision
Constraints
- Review signals inform follow-up routing, not merge gating
- Start with 2-3 high-confidence signals (approval rate, coverage delta)
- Bound auto-generated follow-ups to prevent noise
Goal
Use semantic review signals from pr_monitor (approval patterns, reviewer sentiment, coverage gaps) to route debugging work and trigger follow-up tasks when merged PRs have low confidence or quality flags.
Success Criteria
Constraints