beads-execute

Orchestrate Beads tickets with subagents for parallel execution.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jjeremycai/claudekit --skill beads-execute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads-execute
Source: https://github.com/jjeremycai/claudekit/tree/main/skills/beads-execute
Command: npx skills add https://github.com/jjeremycai/claudekit --skill beads-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines Beads ticket management by coordinating multiple subagents to execute ready tasks with configurable parallelism.

Core Features & Use Cases

  • Orchestrated Ticket Execution: plan, implement, verify, and close steps for each ticket.
  • Parallel/Subagent Execution: run multiple tickets concurrently (2-4) when independent to speed up delivery.
  • Blocker Handling: detect blockers and route for resolution while continuing with other tasks.
  • Progress Summary: produces a concise status of completed, open, and blocked tickets.

Quick Start

Use beads-execute to run all ready tickets with optional parallelism. Example: beads-execute --mode parallel --batch 2

Frequently Asked Questions about beads-execute

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

FAQPage Schema
How do I execute multiple tickets in parallel to speed up workflow delivery?

You can execute multiple independent tickets concurrently using parallel subagents. This workflow coordinates 2-4 ready tasks simultaneously, applying plan, implement, verify, and close steps to accelerate backlog delivery.

What is the best way to manage blockers during parallel ticket execution?

Blocker handling during parallel ticket execution detects issues and routes them for resolution. The workflow continues processing other independent tasks concurrently, ensuring blockers only pause the affected ticket rather than stalling the entire batch.

How does subagent orchestration work for backlog management?

Subagent orchestration for backlog management assigns ready tickets to independent agents. Each subagent follows a structured workflow sequence—read, plan, implement, verify, and close—allowing multiple tickets to progress simultaneously without manual intervention.

Can I configure batch size for concurrent ticket processing?

Yes, you can configure batch size for concurrent ticket processing. You specify the number of tickets to run in parallel (typically 2-4) based on task independence, allowing you to balance execution speed against resource constraints.

How do I evaluate ticket readiness before parallel execution?

Ticket readiness evaluation assesses whether items in the backlog are prepared for execution. The workflow checks if tickets are unblocked and independent, ensuring only suitable tasks are selected for parallel subagent processing.

What reporting is generated after executing a batch of tickets?

After executing a batch of tickets, the workflow produces a progress summary report. This concise status output details completed, open, and blocked tickets, providing clear visibility into the final state of your backlog.