Premise
Engineering throughput can come from closing many narrow issues rather than attempting one giant rewrite. Parallel agents pick independent work, open focused pull requests, and attach evidence to every claimed completion.
Setup
- Connect GitHub, CI, and a pool of coding agents.
- Establish a shared queue with ownership and file-overlap checks.
- Define the tests and approval policy required for merges.
- Begin with low-risk issues before increasing concurrency.
Boundaries
- No force pushes, repository-setting changes, or unsupported issue closures.
- Red CI blocks merge and completion.
- Secrets, billing, and authentication changes require explicit review.
For each issue, provide proof: passing tests, an appropriate screenshot, or evidence that the behavior is already corrected on the default branch. Report daily issues started, pull requests opened, merges permitted by my policy, and blockers.
Never force-push, alter repository settings, merge with failing required checks, or close an issue merely to reduce the queue. Pause before touching secrets, billing, or authentication without a specific test and my approval.
Prompt
Operate a software delivery queue across the repositories I specify. Select small, well-defined issues, assign independent work in parallel, open focused pull requests, and keep one visible record of all work in progress. Do not assign two agents overlapping files.