claim-tasks

Claim tasks from a centralized work queue using file-based locks and Git worktrees.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/bismuthdigital/claude-project-template --skill claim-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claim-tasks
Source: https://github.com/bismuthdigital/claude-project-template/tree/main/.claude/skills/claim-tasks
Command: npx skills add https://github.com/bismuthdigital/claude-project-template --skill claim-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of claiming development tasks from a shared work queue, ensuring that each task is handled by only one agent and preventing duplicate work.

Core Features & Use Cases

  • Automated Worktree Creation: Creates isolated Git worktrees for development, ensuring a clean environment.
  • Conflict Prevention: Uses file-based locks to prevent multiple agents from claiming the same task.
  • Task Prioritization: Claims tasks based on priority, dependencies, and coherence.
  • Use Case: A team of developers uses this Skill to pick up new features from a central NEXT-STEPS.md file. The Skill automatically sets up a new Git branch for each developer, claims tasks, and prevents anyone else from picking up the same task.

Quick Start

Run /claim-tasks to automatically create a worktree and claim up to 3 new tasks.

Frequently Asked Questions about claim-tasks

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

FAQPage Schema
How do I prevent multiple agents from claiming the same task in a shared work queue?

Task claiming uses file-based locking mechanisms to ensure atomic, race-safe task acquisition, preventing concurrent agent conflicts and duplicate work. This guarantees only one agent handles each task.

How do I isolate development work automatically when picking up tasks from a centralized queue?

Automated worktree creation sets up isolated Git worktrees for development, ensuring a clean environment for each claimed task. This isolates changes without affecting the main repository.

Does this task claiming workflow support both per-task file storage and monolithic task storage formats?

Task claiming supports both per-task file storage and monolithic task storage formats, allowing teams to manage development workflow from either a central file or distributed task files.

Do I need Git and Python to automate task claiming and worktree creation?

Git and Python are required dependencies for automating task claiming and worktree creation, as the workflow relies on Git worktrees for environment isolation and Python scripts for execution.

How are tasks prioritized when multiple developers claim work from a centralized queue?

Tasks are claimed based on priority, dependencies, and coherence, ensuring the most relevant and sequential work is picked up first from the centralized work queue file.

What's the best way to coordinate agent workflow automation for a team of developers?

Agent coordination is best handled by automatically claiming tasks from a shared work queue, setting up isolated Git branches for each developer, and preventing concurrent conflicts through file-based locks.