gen-beads

Converts a Markdown project plan into a structured bead graph with tasks and dependencies.

66|2|Updated Feb 18, 2015
One-click install
npx skills add https://github.com/tkersey/dotfiles --skill gen-beads
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-beads
Source: https://github.com/tkersey/dotfiles/tree/main/codex/skills/gen-beads
Command: npx skills add https://github.com/tkersey/dotfiles --skill gen-beads

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams break down a project plan into a structured, parallelizable bead graph, enabling safer, faster implementation with clear dependencies and checkpoints.

Core Features & Use Cases

  • Transform a planning document (plan.md, DESIGN/IMPLEMENTATION/ARCHITECTURE docs, etc.) into a complete set of beads for execution.
  • Enforce parallelization with workstreams, contracts, and checkpoint joins to reduce bottlenecks.
  • Generate verifiable acceptance criteria and embed metadata for future maintenance.

Quick Start

Use the gen-beads Skill to convert your Markdown plan into a beads graph by executing the Generate Step Prompt on the plan file.

Frequently Asked Questions about gen-beads

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

FAQPage Schema
How do I convert a Markdown project plan into parallelizable workstreams?

Generating a DAG-based dependency graph from project planning documents requires local bd tooling to enforce parallelization. This process extracts tasks, subtasks, and explicit contracts to establish verifiable checkpoints across independent execution paths with acceptance criteria.

How does a DAG-based bead graph reduce project bottlenecks?

A DAG-based bead graph reduces project bottlenecks by enforcing parallelization with workstreams, contracts, and checkpoint joins. Directed acyclic graph dependencies ensure tasks execute concurrently, embedding verifiable acceptance criteria for each workstream.

What planning document formats work for generating a structured bead graph?

Generating a structured bead graph works with Markdown planning documents including plan.md, design notes, architecture documents, and implementation notes. These formats provide the necessary structure to extract tasks, subtasks, and dependencies for parallel execution.

Do I need external automation tools to generate a bead graph from a plan?

Generating a bead graph from a plan requires only local bd tooling and no external automation dependencies. The process operates on local planning documents to produce workstreams with embedded metadata, acceptance criteria, and verification signals.

When should I use a bead dependency graph for project management?

Use a bead dependency graph for project management when your planning document requires safe, fast implementation with clear dependencies and checkpoints. It is ideal for complex plans needing parallelizable workstreams with verifiable acceptance criteria and embedded maintenance metadata.