bead-workflow

Coordinate bead task ownership and lifecycle across multiple agents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bead-based projects often require multiple agents to coordinate ownership, progress, and dependencies. This skill provides a structured lifecycle: claim, work, close, with clear announcements and file reservations to prevent conflicts.

Core Features & Use Cases

  • Claim Protocol: ensure the parent bead and all sub-beads are claimed together to avoid conflicts.
  • Reserve Files: lock touched files to prevent concurrent edits.
  • Announcements: broadcast status changes to all agents.
  • Close Protocol: close sub-beads before the parent and release reservations.
  • Security & TDDE: TDD-first approach and mandatory gates to ensure quality and safety in multi-agent workflows.
  • Multi-agent Coordination: detect and respond to multiple agents active to coordinate tasks.

Quick Start

Start a bead by claiming ownership, reserve necessary files, coordinate updates via announcements, and then close the bead when complete.

Frequently Asked Questions about bead-workflow

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

FAQPage Schema
How do I coordinate task ownership across multiple agents to prevent file conflicts?

To coordinate task ownership across multiple agents, you enforce a structured lifecycle of claiming, reserving, announcing, and closing protocols. This locks touched files to prevent concurrent edits and broadcasts status changes to keep all agents synchronized.

How does the claim and reserve protocol work for multi-agent task management?

The claim and reserve protocol ensures parent and sub-beads are claimed together to avoid ownership conflicts, while simultaneously locking touched files. This prevents concurrent edits and establishes clear task boundaries for active agents.

When do I need to enforce a close protocol for multi-agent task dependencies?

You need to enforce a close protocol when managing task dependencies to ensure sub-beads are closed before their parent. This structured sequence releases file reservations and safely finalizes the multi-agent coordination lifecycle.

Does multi-agent workflow coordination require TDD-first development to manage lifecycle tracking?

Multi-agent workflow coordination applies a TDD-first approach with mandatory security gates to ensure quality and safety during lifecycle tracking. This prevents conflicts when multiple agents claim and manage concurrent bead tasks.

What is the best way to broadcast task status updates to multiple active agents?

The best way to broadcast task status updates is through structured announcements integrated into the task lifecycle. This ensures all active agents detect status changes and coordinate dependencies efficiently without file conflicts.