beads-task-dep-add
Add a dependency relationship between Beads tasks
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.
| name | beads-task-dep-add |
|---|---|
| description | Add 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
- Confirm which task is the child and which is the parent (blocker).
- Run:
bd dep add <child-id> <parent-id>
- Optionally verify by showing the child:
bd show <child-id> --json
Notes
- Follow up with
bd syncbefore ending the session if you made changes.