After five parallel subagents complete their module refactoring work, the orchestrator needs to create a unified artifact that summarizes all changes for human review and final approval before merging. What is the best approach?
Select an answer to reveal the explanation.
Short Explanation
You want one coordination summary pull request so a human reviewer can see every agent's changes, why they were made, and which agent made them before approving the merge. Five separate pull requests force reviewers to hold five contexts in their head at once.
Full Explanation
A coordination summary pull request is the standard final artifact for multi-agent orchestration. The orchestrator merges all agent branches into a single coordination branch, runs the full test suite to verify overall system correctness, opens a pull request against main with a generated description that summarizes each agent's changes, including module, scope, tests added, and issues closed, and links all relevant subagent issues for traceability. Human reviewers get a single, consolidated view with test results, linked issues, and each agent's contributions in one approval gate.
Emailing a summary of all agent activities to the team lead is informal, not linked to the repository, not version-controlled, provides no approval mechanism, and does not integrate with branch protection rules. It is not an appropriate artifact for production code review.
Having each agent open its own separate pull request and requiring reviewers to review all five pull requests independently distributes the review burden and creates coordination problems. Reviewers must mentally integrate the changes across five pull requests, changes that interact across modules are hard to see in isolation, and there is no single approval gate. Sequential merging of five pull requests also creates ordering dependency problems.
Closing all agent branches after merging them to the coordination branch and asking developers to check the coordination branch directly provides no formal review mechanism. Developers checking a branch directly have no structured review interface, no comment thread, no approval record, and no required status checks enforced. The pull request is what provides the review workflow.
The coordination summary pull request is the human-readable, reviewable, approval-gated final artifact for multi-agent work.