kimchi:beads

Convert synthesized plans into standalone bead YAML task specifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms a detailed plan into self-contained, executable task specifications (beads) that can be independently run by agents, ensuring clarity and reducing ambiguity in multi-agent workflows.

Core Features & Use Cases

  • Bead Generation: Creates standalone YAML task specifications from a synthesized plan.
  • Contextualization: Embeds necessary code context using find: landmarks for agent execution.
  • Orchestration Support: Generates beads compatible with ACFS or GasTown orchestration.
  • Use Case: After a complex feature plan is finalized, use this Skill to break it down into individual, actionable tasks that different agents can pick up and execute without needing the entire plan context.

Quick Start

Use the kimchi:beads skill to convert the synthesized plan into bead YAML files for ACFS orchestration.

Frequently Asked Questions about kimchi:beads

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

FAQPage Schema
How do I convert a project plan into standalone YAML task specifications for multi-agent execution?

You convert a synthesized plan into standalone bead YAML task specifications by generating self-contained definitions with context, deliverables, and test specifications for multi-agent execution. This ensures agents can execute tasks independently with zero external context.

What is a bead in multi-agent orchestration?

A bead in multi-agent orchestration is a standalone YAML task specification containing context, deliverables, and test specifications. It enables agents to execute tasks independently without needing the entire plan context, reducing ambiguity in complex workflows.

How do I generate task specifications compatible with ACFS or GasTown orchestration?

To generate task specifications compatible with ACFS or GasTown orchestration, you provide a synthesized plan to generate self-contained bead YAML files. These files include necessary context, deliverables, and test specifications tailored for the chosen orchestration mode.

How are code references embedded in task specs for agents with zero external context?

Code references are embedded in task specs using find: landmarks, ensuring agents can locate and utilize necessary code context independently. This approach guarantees beads are executable by agents with zero external context.

Does bead generation enforce test case minimums for task specifications?

Yes, bead generation enforces test case minimums within the YAML task specifications. This ensures every self-contained bead includes adequate test specifications, allowing agents to validate deliverables independently during multi-agent execution.

When do I need to break down a feature plan into individual agent tasks?

You need to break down a feature plan into individual agent tasks after a complex feature plan is finalized and you want different agents to pick up actionable tasks independently. This eliminates the need for agents to access the entire plan context.