work

Coordinate parallel tracker issue implementation via deterministic git worktrees and automated PRs.

30|2|Updated Feb 13, 2026

Search Tags:#automation #git #workflow #worktrees #parallel #issues #pull-request

Ready to run

npx skills add https://github.com/joestump/claude-plugin-design --skill work-joestump

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: work
Source: https://github.com/joestump/claude-plugin-design/tree/main/skills/work
Command: npx skills add https://github.com/joestump/claude-plugin-design --skill work-joestump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams coordinate and execute parallel work on tracker issues by creating isolated git worktrees per issue, preserving a clean main branch while work progresses concurrently.

Core Features & Use Cases

Deterministic per-issue worktrees created via git worktrees to enable parallel implementation without polluting the main history.
Backlog-aware batching and dependency ordering to maximize throughput while respecting issue dependencies.
End-to-end workflow automation: issue discovery, branch naming from issue bodies, PR creation, worker assignment, and post-PR cleanup with configurable behavior.
Safety and governance: dry-run mode, tests flags, and review-ready PR generation, with clear failure reporting and preserved worktrees for failed work.

Quick Start

Request a batch by saying '/design:work SPEC-0003' and let Claude select eligible issues from the backlog.

Frequently Asked Questions about work

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

FAQPage Schema

How do I coordinate parallel git worktrees for multiple tracker issues?▼

This Skill coordinates parallel git worktrees by provisioning deterministically named worktrees per tracker issue and assigning workers to deliver feature branches and PRs automatically. It uses issue body sections to guide branch creation and PR conventions while preserving a clean main branch.

What is the best way to automate pull request creation from a backlog of issues?▼

The best way to automate pull request creation from a backlog is using backlog-aware batching and dependency ordering. The workflow discovers issues, names branches based on issue bodies, assigns workers, and generates review-ready PRs with optional draft modes.

Can I execute a dry-run for parallel workflow automation before creating branches?▼

Yes, you can execute a dry-run for parallel workflow automation before creating branches. The Skill includes a dry-run mode and configurable tests flags to validate planned issue discovery and worker assignment without making actual changes.

How does dependency-aware planning work for multi-agent execution?▼

Dependency-aware planning for multi-agent execution works by respecting issue dependencies during backlog batching to maximize throughput. It orders eligible issues so workers only pick up tasks when dependencies are met, ensuring governed parallel implementation.

What happens to failed worktrees when parallel issue implementation encounters errors?▼

When parallel issue implementation encounters errors, failed worktrees are preserved for manual pickup. The Skill provides clear failure reporting instead of discarding the work, allowing developers to resume or fix the isolated branch manually.