work

Spawn isolated Claude Code worker sessions for GitHub and JIRA issues.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/jimhester/work --skill work-jimhester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work
Source: https://github.com/jimhester/work/tree/main/skills/work
Command: npx skills add https://github.com/jimhester/work --skill work-jimhester

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of efficiently managing GitHub and JIRA work by spawning isolated Claude Code worker sessions for each issue, ensuring work is organized, auditable, and not executed in the current session.

Core Features & Use Cases

  • Isolated worker sessions: Spawn dedicated workers per issue to avoid context leakage and parallelize work.
  • Cross-repo & multi-issue support: Manage workers across multiple repositories, issues, PRs, and JIRA keys.
  • Status tracking & messaging: Monitor worker status and send messages to workers for coordination.
  • Branch and worktree management: Create and manage per-issue git worktrees to isolate changes.

Quick Start

Start one or more workers for GitHub/JIRA issues: work 97 98 99 work https://github.com/owner/repo/issues/42 work AIE-123

Frequently Asked Questions about work

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

FAQPage Schema
How do I spawn isolated Claude Code worker sessions for GitHub and JIRA issues?

You can spawn isolated Claude Code worker sessions by passing issue numbers or JIRA keys to spawn dedicated workers, which automatically sets up per-issue git worktrees and registers workers in SQLite for centralized tracking.

What is the best way to manage multiple GitHub issues across different repositories in parallel?

Managing multiple GitHub issues across repositories is handled by spawning dedicated workers per issue, creating isolated git worktrees to separate changes, and tracking all worker sessions centrally to prevent context leakage during parallel execution.

How do I set up git worktrees for parallel issue processing to avoid context leakage?

Git worktrees are set up automatically per issue when spawning workers, isolating changes for each GitHub or JIRA issue in a dedicated directory to prevent context leakage and allow parallel work without conflicts.

Can I monitor worker status and send messages to active Claude Code worker sessions?

Yes, you can monitor worker status and send messages to active Claude Code worker sessions for coordination, using the centralized SQLite tracking system to manage and communicate with spawned workers across repositories.

Does the worker session skill support parsing GitHub issue URLs and JIRA keys for worktree setup?

Yes, the skill supports parsing full GitHub issue URLs, numeric issue references, and JIRA keys like AIE-123 to automatically configure worktree setup and launch the corresponding Claude Code worker prompts.