beads-task-dep-add

dikini's avatarfrom dikini

Add a dependency relationship between Beads tasks

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 25, 2025⬇️3downloads

When & Why to Use This Skill

The Beads Task Dependency skill enables users to establish hierarchical relationships between tasks within the Beads project management system. By defining parent-child dependencies and blockers, it ensures structured workflows, improves project visibility, and facilitates efficient task orchestration through simple command-line automation.

Use Cases

  • Workflow Sequencing: Automatically link a 'Deployment' task to a 'Testing' task to ensure sequential execution of project phases.
  • Blocker Identification: Explicitly define a 'Design Approval' task as a parent to a 'Frontend Development' task to highlight critical path dependencies.
  • Complex Project Mapping: Organize large-scale projects by connecting multiple granular sub-tasks to their primary milestone tasks for better progress tracking.
  • Automated Task Linking: Use the AI agent to quickly set up dependency chains during project initialization without manual CLI input.
namebeads-task-dep-add
descriptionAdd a dependency relationship between Beads tasks

Beads: add dependency

Semantics

This skill links two tasks so that one depends on (is blocked by / is a child of) another.

Note: Beads supports several relationship types; the essential command from the README is:

bd dep add <child> <parent>

Procedure

  1. Confirm which task is the child and which is the parent (blocker).
  2. Run:
bd dep add <child-id> <parent-id>
  1. Optionally verify by showing the child:
bd show <child-id> --json

Notes

  • Follow up with bd sync before ending the session if you made changes.