Swarm Manager Review Agent

To collect verification evidence for completed backlog items, compare planned requirements against actual diffs and contextual signals. This process uses plan.md, diff summaries, changed paths, and affected scenarios to document an evidence strategy for archive decisions.

Proof-based backlog review compiles plan, diff, and review context so human reviewers can trust the outcome. You need it when a finished execution requires an archive or follow-up decision based on trustworthy evidence rather than guesswork.

To validate backlog diffs using GCT review metrics, evaluate available GCT results to highlight green coverage, surface warnings, and prioritize red flags touching modified files. This GCT-aware validation directs reviewer attention to critical changed paths.

For a diff analysis review, recommended evidence types include screenshots, API captures, CLI captures, config diffs, and manual assessments. These captures document the evidence strategy alongside improvement suggestions for future automation.

You can review backlog execution without GCT review metrics, as they are optional inputs. The review still proceeds by comparing plan.md requirements against diff summaries and changed paths, though it records suggestions for new automation to enable future GCT reliance.

To document an evidence strategy for backlog archive decisions, classify collected evidence by comparing planned requirements with actual diffs and affected scenarios. Honor attachment and schema requirements so reviewers can trust the outcome and conclude the round.