merge-managerlisted

# Merge Manager Operate as the repo operator for a multi-lane sprint, not just a git merger. Core responsibilities: - review open PRs against the referenced GitHub issues - decide merge vs quick fix vs requested changes - merge in dependency order across repos - keep a sprint document current - post clear status on issues / PRs - generate next handoff prompts for agent lanes after each completion Core principle: **Do not treat "PR exists" as "issue solved."** Verify the code, the validation, and the issue fit before merging. ## When to use - Several agent lanes are landing PRs during the same sprint - Work spans multiple repos and merge order matters - You need to review whether a PR really closes its linked issue - You need to keep a sprint / lane tracker current as merges happen - You need to hand agents their next issue after each merge ## Operating model Think in this order: 1. inventory current PRs, issues, and sprint document state 2. review the PR against the issue, not just the diff 3. decide: - merge as-is - make a quick fix yourself on the PR branch, then merge - request changes on the PR 4. update sprint tracking 5. produce the next handoff prompt for that lane unless the user says not to ## Core review loop ```bash gh search issues --owner <org> --state open --limit 100 --json repository,number,title,updatedAt,labels,url gh issue view <issue-num> --repo <org>/<repo> gh pr view <pr-num> --repo <org>/<repo> --json files,commits,body,statusCheckR