create-beads

Import BEADS.md into the bd issue tracker and wire dependencies.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/quantfiction/dotfiles --skill create-beads
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-beads
Source: https://github.com/quantfiction/dotfiles/tree/main/claude/plugins/global-skills/skills/create-beads
Command: npx skills add https://github.com/quantfiction/dotfiles --skill create-beads

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Imports a reviewed BEADS.md into the bd issue tracker and configures all dependencies for end-to-end bead workflows.

Core Features & Use Cases

  • Import BEADS.md into bd as a set of beads with IDs and priorities.
  • Apply project-level labels and map symbolic IDs to actual bead IDs for dependency wiring.
  • Validate BEADS.md format and generate a ready-to-sync bead graph for planning.

Quick Start

Run /create-beads docs/plans/<project>/BEADS.md to import beads and establish dependencies.

Frequently Asked Questions about create-beads

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

FAQPage Schema
How do I import a BEADS.md file into the bd issue tracker?▼

To import a BEADS.md file into the bd issue tracker, run the create-beads command on your file path. It validates the format, creates beads with IDs and priorities, and establishes dependencies for end-to-end project planning.

What is dependency wiring in bd issue tracking?▼

Dependency wiring in bd issue tracking maps symbolic bead IDs from your BEADS.md file to actual bead IDs. This process applies project-level labels and establishes dependencies across projects to enable end-to-end planning.

How do I validate BEADS.md format before importing into bd?▼

You validate BEADS.md format by running the import process, which checks the file structure before creation. This validation ensures the file is properly formatted to generate a ready-to-sync bead graph for planning.

Can I wire dependencies across multiple projects using BEADS.md?▼

Yes, you can wire dependencies across multiple projects using BEADS.md. The import process maps symbolic bead IDs to actual bead IDs and applies project-level labels to establish dependencies for cross-project planning.

What is the best way to configure project-level labels for beads?▼

The best way to configure project-level labels for beads is through the BEADS.md import process. It automatically applies project-level labels while mapping symbolic IDs to actual bead IDs to enable dependency wiring.

Why are my symbolic bead IDs not mapping to actual bead IDs?▼

Symbolic bead IDs fail to map to actual bead IDs when the BEADS.md format is invalid. The import process validates the file structure first; if validation fails, it prevents the creation of beads and the establishment of dependencies.