plan-to-beads

Decompose plan docs into epics and tasks with dependencies.

157|12|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/dcosson/h2 --skill plan-to-beads-dcosson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-to-beads
Source: https://github.com/dcosson/h2/tree/main/internal/config/templates/styles/opinionated/skills/plan-to-beads
Command: npx skills add https://github.com/dcosson/h2 --skill plan-to-beads-dcosson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decomposing large planning documents into structured, implementable work items is error-prone and time-consuming. This skill automates the process by translating reviewed plan docs into epics, tasks, and their dependencies for orchestration.

Core Features & Use Cases

  • Catalog planning inputs: reads the plan index and each plan doc, its addenda, and the test harness to build a comprehensive bead catalog.
  • Sizing & bundling: applies planning rules to create meaningful beads sized for implementation and testing, avoiding overly granular tasks.
  • Dependency analysis: builds intra- and cross-doc dependencies, detects cycles, and outlines the critical path for parallel work.
  • Bead generation: creates an epic with child tasks and a verification bead; supports dry-run to preview proposals without creating work.

Quick Start

Identify the scope from docs/plans and generate bead proposals for the main plan doc and its addenda.

Frequently Asked Questions about plan-to-beads

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

FAQPage Schema
How do I decompose a project plan document into actionable tasks and dependencies?

To decompose a project plan document into actionable tasks, this skill reads the plan docs and addenda to generate a catalog of implementation beads (epics and tasks) with correct intra- and cross-doc dependencies for orchestration.

What is the best way to analyze task dependencies in a planning document for parallel work?

Analyzing task dependencies in a planning document involves building intra- and cross-doc dependency graphs to detect cycles and outline the critical path. This skill automates that dependency analysis to enable parallel work orchestration.

Can I preview task generation from a plan doc without creating work items?

Yes, you can preview task generation from a plan doc without creating work items by using the dry-run output mode. This generates bead proposals and metadata for review without committing them to the orchestration system.

How do I size and bundle development tasks from a project plan?

Sizing and bundling development tasks from a project plan requires applying planning rules to create meaningful beads sized for implementation and testing. This skill automates that sizing process to avoid overly granular work items.

Does this workflow orchestration tool support test harness integration for task generation?

Yes, this workflow orchestration tool supports test harness integration for task generation. It reads the plan docs, addenda, and test harness together to build a comprehensive bead catalog with verification beads.

What are the limitations of automating plan doc decomposition into epics and tasks?

A key limitation of automating plan doc decomposition is that it requires reviewed plan docs as input. The skill relies on existing plan indices and specified docs/plans scopes to generate accurate epics, tasks, and dependency graphs.