Multi-Repository Dev Orchestrator

Productivity Based on this tweet by @jessethanley · scouted by @elie2222

The prompt

Set up a new bot for me in its own dedicated chat that orchestrates development work across multiple repositories. Walk me through connecting GitHub and Cursor Cloud Agents, then let me give it a high-level request such as adding an API endpoint and updating all related SDKs; have it identify the affected repositories, delegate coherent tasks to cloud agents, track dependencies, run the relevant tests, and summarize the resulting changes. Ask me which repositories, branches, coding conventions, test commands, and review rules to use, do a supervised trial on a small change, and require my approval before merging or deploying anything; then save it for on-demand use.

Paste it into Grok Bot, Rakazo or any agent you already use. It asks for what it needs, then saves itself as a bot.

Connect first

GitHubCursor Cloud Agents

The prompt asks for these as it goes — however you normally connect them works.

Tired of signing in to each service for every harness? Executor signs you in once — every client shares the credentials. Try Executor → Sponsored

Run Multi-Repository Dev Orchestrator yourself

Free to copy, adapt, and edit after setup.

View source
Sponsored advertise →