create-beads-orchestration

Initialize Beads task tracking and worktree-per-task orchestration for Claude Code.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/jordanhindo/meridian --skill create-beads-orchestration-jordanhindo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-beads-orchestration
Source: https://github.com/jordanhindo/meridian/tree/main/.claude/skills/create-beads-orchestration
Command: npx skills add https://github.com/jordanhindo/meridian --skill create-beads-orchestration-jordanhindo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines setting up a multi-agent Claude Code workflow by bootstrapping Beads-based task tracking, isolated worktrees, and workflow-enforcing hooks so agents can collaborate safely without heavy MCP overhead.

Core Features & Use Cases

  • Creates a Beads + worktree-per-task workflow: each bead maps to an isolated worktree under .worktrees/bd-{BEAD_ID}/ to keep main clean and enable parallel implementation.
  • Bootstraps Claude Code agents and hooks: installs and configures the project’s orchestration scaffolding, including agent templates and discipline/validation hooks.
  • Detects and integrates Beads Kanban UI (optional): configures worktree management via API when bead-kanban is available, otherwise falls back to git worktrees.
  • Runs discovery after restart: ensures tech stack detection and supervisor creation happen only after hooks/MCP config are loaded.

Quick Start

Run /create-beads-orchestration in Claude Code, answer the project directory/name and provider choice questions, then restart Claude Code when the skill instructs you to continue setup afterward.

Frequently Asked Questions about create-beads-orchestration

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

FAQPage Schema
How do I set up multi-agent orchestration in Claude Code?

Multi-agent orchestration in Claude Code is set up by initializing Beads task tracking, a worktree-per-task workflow, and hook-based enforcement to let agents collaborate safely without heavy MCP overhead.

How do git worktrees work with task tracking for parallel execution?

Git worktrees isolate parallel execution by mapping each task bead to a dedicated worktree under .worktrees/bd-{BEAD_ID}/, keeping the main branch clean while multiple agents implement tasks simultaneously.

What is the best way to bootstrap a worktree-per-task workflow for AI agents?

The best way is to run a bootstrap skill that installs orchestration scaffolding, agent templates, and discipline hooks, then restart Claude Code to load configurations before executing discovery agents.

Do I need the Beads Kanban UI to manage multi-agent worktrees?

No, the Beads Kanban UI is optional; the workflow detects and integrates it for worktree management via API if available, otherwise it automatically falls back to standard git worktrees.

Why does my Claude Code orchestration setup require a restart?

A mandatory restart is required to ensure hooks and MCP configurations are fully loaded before running discovery agents to detect your tech stack and create supervisors in .claude/agents/.

Can I use this orchestration setup for an existing project with active agents?

No, this setup applies to fresh project initialization where an orchestrator delegates to core agents, establishing the worktree and hook scaffolding before any implementation tasks begin.