skills.rest
tmsjngx0
tmsjngx0COMMUNITY
Explore all skills by this author →
GitHub

bd-sync

Synchronize OpenSpec changes with Beads epics and audit for gaps.

Updated Aug 23, 2026
Search Tags:#devops#task management#synchronization#beads#openspec#epic management
One-click install
npx skills add https://github.com/tmsjngx0/mindcontext-core --skill bd-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bd-sync
Source: https://github.com/tmsjngx0/mindcontext-core/tree/main/skills/bd-sync
Command: npx skills add https://github.com/tmsjngx0/mindcontext-core --skill bd-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the synchronization between your OpenSpec documentation and your project's epics in the Beads task management system, ensuring consistency and identifying discrepancies.

Core Features & Use Cases

  • Synchronization: Keeps OpenSpec changes and Beads epics aligned.
  • Gap Auditing: Identifies missing or orphaned items between the two systems.
  • Import & Update: Facilitates importing new changes from OpenSpec and updating existing epics.
  • Untracked Work Detection: Finds commits or tasks not yet reflected in your specifications.
  • Use Case: After updating a feature specification in OpenSpec, use this Skill to automatically create or update the corresponding epic and tasks in Beads, ensuring your development team is always working with the latest requirements.

Quick Start

Run the bd-sync skill to audit for any discrepancies between your OpenSpec changes and Beads epics.

Frequently Asked Questions about bd-sync

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

FAQPage Schema
How do I synchronize OpenSpec changes with Beads epics?▼

The synchronization mechanism routes requests to specialized agents for auditing, building, importing, and scanning, performing bi-directional synchronization to keep OpenSpec changes and Beads epics aligned.

What is the best way to find untracked work not reflected in OpenSpec specifications?▼

Finding untracked work requires scanning your commits or tasks against specifications; this skill identifies missing or orphaned items between your OpenSpec documentation and Beads epics to detect discrepancies.

How do I audit for gaps between Beads task management and OpenSpec documentation?▼

Auditing for gaps involves running a scan to identify missing or orphaned items between the two systems, ensuring your development team works with the latest requirements and specifications.

Can I perform bi-directional synchronization between OpenSpec and Beads?▼

Yes, bi-directional synchronization is supported, allowing you to import new changes from OpenSpec to Beads and update existing epics while identifying untracked work across both systems.

Why does my Beads epic management have orphaned items after updating OpenSpec?▼

Orphaned items occur when Beads epic management and OpenSpec changes fall out of alignment; running an audit identifies these discrepancies and updates existing epics to restore consistency.

Related Skills

Explore More Software Engineering Skills→
maslennikov-igmaslennikov-ig
2

Import Tasks from Central Inbox

Import tasks from a central Beads task-inbox into a local project.

Community
Intermediate
dayvidphamdayvidpham
1

status

Monitor project status and implementation progress using Beads queries.

Community
Intermediate
dorriodorrio

ln-003-push-all

Commit and push all local changes to the remote repository.

Community
Basic
stoodderstoodder
1

reconcile-epic

Synchronize epic documents with shipped member specifications and cascade changes.

Community
Intermediate