parallelize-work-cursor

What problem does it solve?

Coordinating multiple independent implementation tasks serially wastes time and delays merges when your work can be safely split across concurrent Linear issues.

Core Features & Use Cases

• Per-issue worktree isolation: creates one wt worktree per explicitly identified Linear issue, preventing cross-talk between tasks.
• Detached Cursor agent sessions: starts a detached Cursor agent session per task inside the matching worktree so you can attach and steer each run independently.
• Explicit parallel-safety from source-of-truth: only parallelizes tasks that are clearly marked safe in an input document or spec, avoiding guesswork about dependencies.

Use case: You have an implementation plan or TRD that names multiple independent Linear issues (e.g., frontend work and backend work that do not block each other); run this skill to spawn agents for each issue concurrently and keep their scopes constrained.

Quick Start

Run: call launch_parallel_ticket_work.py with a plan JSON that includes a required source doc URL/path and a tasks array mapping each parallel Linear issue to its project and worktree name.