parallelize-work

Launch one worktree and detached tmux worker per parallel Linear issue.

Updated May 18, 2025
One-click install
npx skills add https://github.com/nthpaul/dotfiles --skill parallelize-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallelize-work
Source: https://github.com/nthpaul/dotfiles/tree/main/cursor/.cursor/skills/parallelize-work
Command: npx skills add https://github.com/nthpaul/dotfiles --skill parallelize-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tmux, wt, zsh, codex, linear, and includes scripts (resource) components.

What problem does it solve?

It eliminates the bottleneck of handling multiple independent Linear implementation tasks sequentially by splitting them into parallel execution.

Core Features & Use Cases

  • Worktree + worker orchestration: Creates one wt worktree and one detached worker tmux session per explicitly parallel task.
  • Strict task-to-issue mapping: Ensures each child worker owns exactly one Linear issue (no multi-issue mixing) and escalates when required mappings are missing.
  • Launch-plan driven execution: Uses a JSON execution plan derived from a clearly marked source of truth so concurrency is not guessed from vague project structure.

Quick Start

Provide a required source doc or plan text that explicitly lists the parallelizable tasks and then run the launcher with a JSON plan file to start detached workers for each Linear issue.

Frequently Asked Questions about parallelize-work

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

FAQPage Schema
How do I run parallel Linear implementation tasks using git worktrees and tmux?

To run parallel Linear tasks, you provide a JSON plan with per-task issue IDs and execute launch_parallel_ticket_work.py, which creates one wt worktree and one detached tmux worker session per Linear issue for concurrent execution.

What is the best way to orchestrate parallel development workflows for independent Linear issues?

Orchestrating parallel Linear workflows requires a JSON execution plan derived from a source that explicitly marks concurrency, ensuring each child worker owns exactly one Linear issue without multi-issue mixing or unclear dependencies.

Do I need a JSON plan to split Linear tickets into parallel detached worker sessions?

Yes, a JSON plan is required. It must include a source field, per-task Linear issue_id and project fields, with optional per-task worktree and guidance fields to safely launch parallel detached workers.

Can I use tmux and wt to parallelize Linear tasks that have dependencies between them?

No, parallel execution only works for project or task breakdowns where concurrency is explicitly marked and each task can be executed independently without unclear dependencies.

What happens if a Linear issue mapping is missing from the execution plan?

When required task-to-issue mappings are missing, the launcher escalates rather than guessing, ensuring each child worker strictly owns exactly one Linear issue with no multi-issue mixing.

Does parallel ticket work require specific shell or CLI tools to function?

Yes, parallel ticket work requires tmux for detached worker sessions, wt for worktree resolution, zsh, codex, and Linear CLI integration to orchestrate independent implementation tasks.