Linear Backlog

Linear Backlog

Run a frozen Linear queue as serial batches with parallel execution inside each batch. Keep the parent as controller; send every implementation issue through orchestrator, autogoal, and the repo's task skill.

Required Capabilities

Require all of these before mutation:

• Linear issue read and write tools.
• $orchestrator with durable Codex child-thread tools.
• $autogoal and its goal tools.
• The destination repo's $task skill and AGENTS instructions.
• Git and the repo's normal PR and merge tooling.

If a capability is missing, report the exact dependency. Never replace durable child threads with hidden sub-agents or fake Linear state transitions with comments.

Commands

• $linear-backlog run <scope>: execute the queue in maximal safe parallel batches.
• $linear-backlog status: report counts, active batch and lanes, conflict groups, blocked issues, and the next candidate batch.
• $linear-backlog stop: stop after parking every active lane safely and recording resumable state.

Scope may be a Linear project, cycle, label, saved view, or explicit issue list. If the prompt and current context do not identify exactly one scope, ask one short question before mutation.

Non-Negotiable Contract

• Keep exactly one batch active at a time.
• Run every safe lane in that batch concurrently.
• Do not start the next batch until every lane in the current batch is queue-terminal and the batch join is recorded.
• Make each batch inclusion-maximal: no remaining dependency-ready issue may be