spurpower-beads-lifecycle

Manages Bees issue lifecycle state machine and label vocabulary for Brain-Worker orchestration.

2|Updated Apr 15, 2026

Search Tags:#workflow #orchestration #issue-tracking #state-machine #agent-collaboration #spur

Ready to run

npx skills add https://github.com/getspur/spur --skill spurpower-beads-lifecycle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spurpower-beads-lifecycle
Source: https://github.com/getspur/spur/tree/main/.claude/skills/spurpower-beads-lifecycle
Command: npx skills add https://github.com/getspur/spur --skill spurpower-beads-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents operational confusion and scope drift by enforcing a strict status state machine and label vocabulary for beads issues, ensuring brain-worker collaboration remains consistent.

Core Features & Use Cases

Status State Machine Enforcement: Provides clear transition rules for issue statuses like open, in_progress, and blocked to prevent race conditions.
Structured Labeling: Standardizes the use of plan, delegation, signal, and mutation labels to maintain auditability.
Use Case: When a worker needs to signal a blockage or a brain needs to approve a task, this Skill provides the exact status and label protocol to ensure the orchestrator and other agents interpret the state correctly.

Quick Start

Use the spurpower-beads-lifecycle skill to transition the current issue to in_progress and apply the required delegation labels for the assigned worker.

Frequently Asked Questions about spurpower-beads-lifecycle

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

FAQPage Schema

How do I enforce a state machine for issue tracking in agent orchestration?▼

To enforce a state machine for issue tracking in agent orchestration, apply strict status transition rules like open, in_progress, and blocked to prevent race conditions. This ensures consistent audit trails and correct brain-worker collaboration behavior.

What is the best way to standardize labels for workflow orchestration between agents?▼

Standardizing labels for workflow orchestration requires applying a structured vocabulary like plan, delegation, signal, and mutation labels. This maintains auditability and ensures the orchestrator interprets task delegation and signal handling correctly.

How do I transition an issue status to in_progress without causing race conditions?▼

Transitioning an issue status to in_progress safely requires following a defined status FSM that enforces clear transition rules. This prevents race conditions and ensures worker agents correctly signal blockages or task approvals.

Can I use structured labeling to maintain audit trails for brain-worker task delegation?▼

Yes, you can maintain audit trails for brain-worker task delegation by applying structured plan, delegation, signal, and mutation labels. This standardizes communication and ensures the orchestrator interprets the issue state correctly.

Why does scope drift occur in agent collaboration and how do I prevent it?▼

Scope drift occurs in agent collaboration due to operational confusion from inconsistent status updates. Prevent it by enforcing a strict status state machine and label vocabulary for beads issues to maintain consistent orchestrator behavior.

Does the spur orchestration framework support blocked status signaling for worker agents?▼

Yes, the spur orchestration framework supports blocked status signaling. Worker agents can use the defined status FSM to signal blockages, allowing the brain agent to interpret the state correctly and respond with the appropriate protocol.