linear-todo-runner

Orchestrate parallel Linear issue processing with isolated worktree-bound agents.

6|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/withpiper/pipekit --skill linear-todo-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-todo-runner
Source: https://github.com/withpiper/pipekit/tree/main/skills/06-linear-todo-runner
Command: npx skills add https://github.com/withpiper/pipekit --skill linear-todo-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating a batch of Linear issues by spawning multiple isolated worktree agents to run in parallel, increasing throughput while preserving per-issue isolation.

Core Features & Use Cases

  • Orchestrates parallel worker agents bound to isolated Linear worktrees to process queues and respect blockers.
  • Manages queue assembly, dependency graph building, and dynamic refilling as work completes.
  • Provides a scalable workflow for multi-issue delivery, from AC preparation through UAT handoff and status logging.

Quick Start

Run /linear-todo-runner to start processing the queue with default settings.

Frequently Asked Questions about linear-todo-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I process multiple Linear issues in parallel using isolated worktrees?

Parallel processing of Linear issues is achieved by orchestrating batch queues and spawning multiple worktree-bound agents that run concurrently. The system manages queue assembly, dependency graphs, and dynamic refilling as work completes while preserving per-issue isolation.

What is dependency graph orchestration for batch ticket delivery?

Dependency graph orchestration for batch ticket delivery is the process of mapping blocker relationships across a queue of issues to determine execution order. This Skill builds the dependency graph and applies explicit gating to ensure parallel agents respect blockers and state transitions.

How do I manage queue refilling when parallel agents complete their assigned issues?

Queue refilling happens dynamically as work completes. The orchestrator manages queue assembly, building dependency graphs and dynamically refilling the queue with new issues to maintain continuous parallel agent throughput across project-wide delivery workflows.

Can I use parallel agents for project-wide delivery workflows from AC preparation through UAT handoff?

Yes, this Skill supports project-wide delivery workflows from AC preparation through UAT handoff. It handles per-issue state transitions across phases, enforces safety constraints, applies deployment checks, and logs pipeline states while respecting Linear state changes.

What are the limitations of using parallel worktree agents for queue management?

Limitations of using parallel worktree agents include the necessity of explicit gating and deployment checks to prevent conflicts. The system enforces safety constraints and respects Linear state changes, but complex dependency graphs require careful queue assembly to avoid blocker deadlocks.