beads

Synchronize Beads task status and metadata with SDP workflows.

Updated Feb 19, 2026

Search Tags:#workflow #integration #synchronization #beads #mapping #task-tracking #sdp

Ready to run

npx skills add https://github.com/fall-out-bug/sdp_lab --skill beads-fall-out-bug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/fall-out-bug/sdp_lab/tree/main/.agents/skills/beads
Command: npx skills add https://github.com/fall-out-bug/sdp_lab --skill beads-fall-out-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Beads task tracker and SDP workflows operate in parallel; this integration links Beads tasks to SDP work items to synchronize status, dependencies, and progress across tools.

Core Features & Use Cases

Cross-system linking: Maps Beads tasks to SDP work items via .beads-sdp-mapping.jsonl.
Status synchronization: Keeps task state in Beads and SDP aligned using the beads_transport.sh script.
Use Case: Manage a single workstream with Beads tasks and SDP milestones, automatically updating progress across both systems.

Quick Start

Create or identify a Beads task, ensure the mapping file links it to an SDP work item, and run the beads_transport.sh export to synchronize states.

Frequently Asked Questions about beads

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

FAQPage Schema

How do I synchronize task status between Beads and SDP workflows?▼

Task status synchronization between Beads and SDP uses the beads_transport.sh script to export and align task states across both systems. You configure the links via a .beads-sdp-mapping.jsonl mapping file before execution.

What is the .beads-sdp-mapping.jsonl file used for in task tracking integration?▼

The .beads-sdp-mapping.jsonl file defines the cross-system linking required to map individual Beads tasks to their corresponding SDP work items. It serves as the required configuration to synchronize status and dependencies across tools.

Can I manage cross-tool task dependencies using this SDP workflow integration?▼

Yes, this integration supports managing cross-tool task dependencies between Beads and SDP. It applies to SDP planning, design, and development workstreams, automatically updating progress and dependencies across both systems.

Do I need a specific transport script to link Beads tasks with SDP milestones?▼

Yes, linking Beads tasks with SDP milestones requires the beads_transport.sh transport script located in the scripts directory. This script handles the automated export and synchronization of task metadata and states.

What are the limitations of syncing Beads tasks with SDP planning workstreams?▼

Syncing Beads tasks with SDP planning workstreams is limited by its reliance on a manually maintained .beads-sdp-mapping.jsonl mapping file. If tasks are not explicitly mapped, the beads_transport.sh script cannot synchronize their status or dependencies.