Linear Development Orchestrator

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

The prompt

Set up a new bot for me I can trigger for parallel development work. Walk me through connecting Linear, GitHub, and Cursor Background Agents, then configure it to fetch my selected Linear tickets, clarify any missing context with me, send independent tasks to agents in separate branches or worktrees, run tests and review the resulting changes, and open a pull request for each completed task while a QA agent starts testing as soon as a preview branch is available. Ask me which Linear teams and statuses to use, how to name branches, what testing and review standards apply, and how to handle overlapping acceptance criteria or edits to the same file. Show me the proposed task assignments and the first-run results before creating pull requests or sending any external updates, 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

LinearGitHubCursor Background 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 Linear Development Orchestrator yourself

Free to copy, adapt, and edit after setup.

View source
Sponsored advertise →