loop-work
Loop Work
Coordinate ticket delivery; delegate all implementation and PR repairs. Repeatedly select work that can be completed without user input, dispatch isolated workers, verify and merge their PRs, then reassess the backlog against the updated repository.
Run this workflow only when the user has requested autonomous ticket delivery through verified PR merges. That request authorizes scoped Linear transitions to In Progress, worker commits/pushes/PRs and review replies through complete-work, and coordinator merges of verified PRs. Loading or automatically selecting this skill does not supply authorization; a request to inspect or plan a backlog is insufficient. Establish missing authorization before claiming tickets or starting workers. Honour narrower instructions and repository restrictions. Deployment, releases, bypassing protections, and unrelated tracker mutations require separate authorization.
1. Resolve inputs and prerequisites
Recover inputs from the invocation and conversation. Ask once, in a bundled question, for missing or ambiguous required values before claiming tickets or starting workers. Accept natural-language equivalents of these parameter names.
| Parameter | Required value |
|---|---|
linear_team |
Unambiguous team name, ID, or URL. Resolve and retain its ID. |
linear_project |
Unambiguous project name, ID, or URL belonging to that team. Resolve and retain its ID. |
max_parallel_subagents |
Positive integer; maximum simultaneously live workers, including their nested subagents. The coordinator does not count. |
max_tickets |
Positive integer or explicitly unlimited / no max. Count distinct tickets completed by verified merges during this run, not starts, opened PRs, or failed attempts. |
Use the current repository unless another is explicitly supplied; ask if the team/project maps to multiple repositories or the intended checkout is unclear. Optional inputs are ticket_filter (issue IDs, labels, milestone, or cycle; default all open project issues) and stop_at (deadline with timezone; default none). Preserve any other explicit user constraints. Discover the default branch, remotes, workflow states, merge method, and repository checks; they are not mandatory user parameters. The branch prefix is fixed at agent/, never a parameter.