next-bead

Discover, verify, and claim the next Beads task with conflict checks.

Updated Dec 12, 2025
One-click install
npx skills add https://github.com/eaasxt/Farmhand --skill next-bead
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-bead
Source: https://github.com/eaasxt/Farmhand/tree/main/config/skills/next-bead
Command: npx skills add https://github.com/eaasxt/Farmhand --skill next-bead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates safe discovery and claiming of the next Beads task, preventing conflicts and coordinating with other agents to keep work flowing smoothly.

Core Features & Use Cases

  • Orchestrates a four-phase workflow (Closeout, Discover, Verify, Claim) to surface and reserve the next available bead.
  • Performs conflict checking and file reservations to prevent overlapping work.
  • Announces claims to all agents to maintain a synchronized state during multi-agent coordination.

Quick Start

To trigger the next-bead workflow, ask the orchestrator to locate, verify, and safely claim the next available bead.

Frequently Asked Questions about next-bead

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

FAQPage Schema
How do I safely claim the next task in a multi-agent orchestrator workflow?

To safely claim the next task in a multi-agent orchestrator workflow, you trigger a four-phase process: closeout, discovery, verify, and claim. This coordinates file reservations and announces claims to all agents to maintain synchronized state.

How does file reservation conflict checking work for multi-agent task coordination?

File reservation conflict checking works by running a verification phase before claiming a task, ensuring no overlapping work exists. It announces claims to all agents to maintain a synchronized state and prevent file conflicts during multi-agent coordination.

What is the best way to prevent overlapping work when multiple agents discover tasks?

The best way to prevent overlapping work is using an orchestrator-driven workflow with dedicated subagents for discovery, verification, and claiming. This resolves in-progress work and performs file reservations before announcing the claimed task to other agents.

Do I need an orchestrator to manage task discovery and claiming in multi-agent environments?

Yes, you need an orchestrator to manage task discovery and claiming in multi-agent environments. The workflow applies an orchestrator-driven approach with dedicated subagents attached to each phase to surface, verify, and safely reserve the next available bead.

Can I closeout and discover tasks simultaneously with multiple agents?

You can closeout and discover tasks simultaneously by using the orchestrator's four-phase workflow. It automates safe discovery and claiming of the next Beads task while coordinating with other agents to keep work flowing smoothly and prevent conflicts.