beads-workflow

Convert markdown project plans into dependency-linked task graphs with the br CLI.

45|2|Updated Apr 24, 2026

Search Tags:#automation #planning #project management #task management #agent workflow #dependency graph

Ready to run

npx skills add https://github.com/hachej/boring-ui --skill beads-workflow-hachej

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: beads-workflow
Source: https://github.com/hachej/boring-ui/tree/main/.agents/skill-references/plan/jeffrey-emanuel-beads-workflow
Command: npx skills add https://github.com/hachej/boring-ui --skill beads-workflow-hachej

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the disconnect between high-level project planning and granular execution by converting static markdown plans into a structured, dependency-aware task system.

Core Features & Use Cases

Granular Task Management: Converts vague project plans into detailed, self-documenting beads with clear subtasks and dependencies.
Dependency Graphing: Automatically manages task relationships to prevent cycles and ensure logical execution order.
Use Case: Use this skill to take a complex feature specification and break it down into a series of verifiable, testable beads that an agent swarm can implement with minimal oversight.

Quick Start

Use the beads-workflow skill to initialize your project and convert your current plan file into a comprehensive set of actionable beads.

Frequently Asked Questions about beads-workflow

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

FAQPage Schema

How do I convert markdown project plans into a dependency-linked task graph?▼

You can convert markdown plans into a dependency-linked task graph by using a CLI tool that parses the text and generates self-contained task definitions with automatic relationship mapping to prevent cycles and ensure logical execution order.

What is the best way to break down complex feature specifications for automated agent execution?▼

Breaking down complex specifications involves transforming high-level markdown plans into granular, verifiable beads with clear subtasks and dependencies, enabling an agent swarm to implement them with minimal oversight.

Do I need a git worktree to manage automated task dependencies and synchronization?▼

Yes, a configured git worktree is required for synchronization and version control when transitioning from conceptual planning to automated agent execution via the CLI.

How does dependency graphing prevent execution cycles in task management?▼

Dependency graphing prevents execution cycles by automatically managing task relationships within the generated task graph, enforcing logical execution order before the agent swarm begins implementation.

Can I use markdown files for granular task management in an automated workflow?▼

Yes, you can use markdown files for granular task management by converting static project plans into a structured, dependency-aware task system with detailed, self-documenting subtasks.

Why use a structured task graph instead of static markdown plans for software project planning?▼

A structured task graph solves the disconnect between high-level planning and granular execution by replacing static text with dependency-aware, verifiable beads that automated agents can systematically implement.