kramme:resolve-review:team

Parallel review resolution divides 5+ findings across multiple file areas into separate, non-overlapping work streams so fixes proceed simultaneously. This reduces overall turnaround time by assigning each teammate exclusive write access to their assigned files.

Agent teams automate review resolution by following a structured workflow: the lead creates a plan, spawns resolver teammates, assigns exclusive file ownership to prevent conflicts, monitors progress, and verifies the changes. Each teammate works on their assigned files independently.

Fixing review findings across multiple modules is best handled by parallel assignment. When a review has 5+ findings across areas like auth, api, or tests, dedicated teammates handle each module concurrently to finish faster without overlapping file access.

Yes, you must enable Agent Teams by setting the CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS environment variable. This experimental feature is required because the system needs it to spawn resolver teammates for processing findings in parallel.

Run the resolution command with a REVIEW_OVERVIEW.md file describing the findings. The system will read the overview, spawn a resolver team, and assign files across the identified work areas accordingly to execute the fixes.

You should avoid this approach when a code review has fewer than 5 findings or when findings are concentrated in a single file area. The parallel workflow is designed for 5+ findings spread across multiple modules to be effective.