beads-lifecycle

Standardize coding agent task lifecycle management with a status state machine and label vocabulary.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/getspur/spur --skill beads-lifecycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads-lifecycle
Source: https://github.com/getspur/spur/tree/main/.spur/skills/beads-lifecycle
Command: npx skills add https://github.com/getspur/spur --skill beads-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity in brain-worker collaboration by enforcing a strict state machine and label vocabulary for issues, preventing status drift and communication gaps.

Core Features & Use Cases

  • Status State Machine: Provides a clear, deterministic path for issue transitions from draft to closed, ensuring all participants understand the current workflow stage.
  • Label Semantics: Standardizes metadata for plan scoping, agent delegation, and signal processing to maintain auditability.
  • Use Case: When a worker encounters a blocker, this skill guides the correct signal emission and label application so the brain can intervene effectively without manual status tracking.

Quick Start

Use the beads-lifecycle skill to transition the current issue to in_progress and assign the appropriate worker agent.

Frequently Asked Questions about beads-lifecycle

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

FAQPage Schema
How do I enforce a consistent issue state machine for coding agent orchestration?

Enforce a consistent issue state machine for coding agent orchestration by applying a defined status FSM and structured label vocabulary. This standardizes lifecycle management and prevents status drift during brain-worker collaboration.

What is the best way to standardize communication between planning brains and worker agents?

Standardize communication between planning brains and worker agents by enforcing transition rules and signal semantics. This structured label vocabulary ensures reliable orchestration and full auditability of agent tasks.

How do I handle a worker agent blocker during automated workflow execution?

Handle a worker agent blocker during automated workflow execution by emitting the correct signal and applying the designated label. This guides the planning brain to intervene effectively without manual status tracking.

Can I transition an issue to in_progress and assign it to a specific worker agent?

Yes, you can transition an issue to in_progress and assign it to a specific worker agent. The skill provides deterministic transition paths from draft to closed, ensuring all participants understand the current workflow stage.

Why does status drift occur in agent orchestration and how do I prevent it?

Status drift occurs in agent orchestration due to ambiguous communication and unstructured issue tracking. Prevent it by enforcing a strict state machine and label semantics, which eliminates communication gaps between planning brains and workers.