beads

Create and update br bead-based issue tracking items for epics, tasks, and bugs.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/sQVe/cape --skill beads-sqve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/sQVe/cape/tree/main/skills/beads
Command: npx skills add https://github.com/sQVe/cape --skill beads-sqve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads provides authoritative guidance for using br, the git-backed issue tracker, to create, update, and query epics, tasks, and bugs from within cape. It also clarifies how to recognize bead IDs, manage workspaces, and how cape skills should emit br items as outputs.

Core Features & Use Cases

  • Command reference for correct syntax, flags, and common mistakes.
  • Output conventions — how cape skills should create br items as their output artifacts.
  • Bead ID recognition from conversation and how to resolve them with br show.
  • Workflow guidance for creating, updating, and linking br items within epics and tasks.
  • Debugging br command failures (wrong flags, missing workspace).

Quick Start

Log a new br item for a reported issue using the cape beads workflow.

Frequently Asked Questions about beads

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

FAQPage Schema
How do I create epics, tasks, and bugs in a git-backed issue tracker from within cape?

To create epics, tasks, and bugs in a git-backed issue tracker from within cape, use the br command reference to apply correct syntax and flags, ensuring you set the item type and priority for generated outputs.

What is a bead ID and how do I resolve it in a br workspace?

A bead ID is the unique identifier for a br issue tracking item. You resolve a bead ID extracted from conversation by running the br show command within your active .beads workspace to view its details.

How do I maintain parent-child relationships when linking tasks to epics?

To maintain parent-child relationships when linking tasks to epics, follow the br workflow guidance to enforce proper usage, ensuring all created or updated items correctly align with br item conventions and respect the epic hierarchy.

Why are my br commands failing with missing workspace or wrong flags?

Br commands fail with missing workspace or wrong flags due to syntax errors or lacking a .beads directory. Debug these br command failures by verifying you are in a valid .beads workspace and correcting your command flags.

What output conventions should cape skills follow when emitting br items?

Cape skills emitting br items must follow output conventions that enforce proper usage, requiring you to set the item type and priority for generated artifacts while respecting parent-child relationships to align with br item standards.

Can I use br bead-based issue tracking for both bug reporting and feature planning?

Yes, you can use br bead-based issue tracking for bug reporting, task planning, and feature tracking. The workflow applies across these scenarios by recognizing bead IDs and managing items within epics and tasks.