kimchi:bead-protocol

Executes bead tasks enforcing protocol rules based on GitTown or upstream-compatible source selection.

8|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Tromml/kimchi --skill kimchi-bead-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kimchi:bead-protocol
Source: https://github.com/Tromml/kimchi/tree/main/plugins/kimchi/skills/bead-protocol
Command: npx skills add https://github.com/Tromml/kimchi --skill kimchi-bead-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that AI agents execute self-contained task specifications (beads) in a consistent, safe, and predictable manner, regardless of the underlying orchestration system.

Core Features & Use Cases

  • Orchestration Mode Detection: Automatically identifies whether to follow the ACFS or GasTown protocol based on .beads/manifest.yaml.
  • Protocol Enforcement: Guides agents through the correct steps for reading beads, loading context, reserving files (ACFS), reporting status, and handling blockers.
  • Use Case: When an agent is assigned a bead task, this Skill is invoked first to determine the correct execution environment and enforce the necessary protocols, preventing errors and ensuring smooth multi-agent collaboration.

Quick Start

Follow the ACFS protocol to execute the bead task.

Frequently Asked Questions about kimchi:bead-protocol

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

FAQPage Schema
What is a bead protocol for agent execution?

A bead protocol enforces execution standards for self-contained task specifications, detecting orchestration modes like ACFS or GasTown to guide agents through context loading, file reservation, and status reporting.

How do I execute beads with discipline in a multi-agent system?

To execute beads with discipline, agents must detect the orchestration mode from `.beads/manifest.yaml`, then follow specific checklists for loading context, reserving files, reporting status, and communicating blockers.

Does bead execution work with both ACFS and GasTown orchestration modes?

Yes, bead execution works with both ACFS and GasTown by automatically detecting the correct protocol from the `.beads/manifest.yaml` file and enforcing the appropriate steps for reliable multi-agent task completion.

What are the limitations of agent task execution without a standardized protocol?

Without a standardized protocol, agent task execution risks errors and disrupted collaboration due to unmanaged context loading, missing file reservations, unreported statuses, and unhandled blockers.

Why does my agent fail to reserve files during bead task execution?

Agents fail to reserve files when the bead execution protocol is not properly enforced, requiring adherence to the specific ACFS file reservation checklists and anti-patterns to ensure reliable task completion.

When do I need to use a bead protocol for task specification?

You need a bead protocol when assigning self-contained task specifications to AI agents, ensuring consistent, safe, and predictable execution across different multi-agent coordination systems.