beads-sdd-orchestrator

Orchestrate Spec-Driven Development workflows and manage cycles with the Beads framework.

15|Updated Jun 22, 2025
One-click install
npx skills add https://github.com/sidereal-io/sidereal --skill beads-sdd-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads-sdd-orchestrator
Source: https://github.com/sidereal-io/sidereal/tree/main/.agent/skills/beads-sdd-orchestrator
Command: npx skills add https://github.com/sidereal-io/sidereal --skill beads-sdd-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps manage complex development cycles by orchestrating various Spec-Driven Development (SDD) workflows, ensuring that all aspects of a project are tracked and executed effectively within the Beads framework.

Core Features & Use Cases

  • Orchestration of SDD Workflows: Integrates with multiple SDD frameworks (Spec Kit, Superpowers, BMad, GSD, etc.) to streamline the development process.
  • Beads Framework: Utilizes the Beads framework to manage state, dependencies, gates, and work memory.
  • GitHub Integration: Synchronizes with GitHub Issues for visibility and tracking, without compromising the Beads' authoritative state.
  • Use Case: For a software development team using Beads to manage features, this Skill can automate the conversion of GitHub Issues into Beads, track progress, and ensure that all tasks are completed according to the defined workflow.

Quick Start

Run the beads-sdd-orchestrator skill to synchronize a GitHub Issue with a Beads bead.

Frequently Asked Questions about beads-sdd-orchestrator

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

FAQPage Schema
How do I manage Spec-Driven Development workflows with GitHub Issues?

You can orchestrate Spec-Driven Development workflows by synchronizing GitHub Issues with the Beads framework, ensuring the Beads bead maintains authoritative state while tracking visibility on GitHub.

What is the best way to integrate GitHub Issues into a Beads development cycle?

The best way to integrate GitHub Issues into a Beads development cycle is using an orchestrator that converts issues into beads, managing state and dependencies without compromising Beads' authoritative state.

Do I need the Beads framework to run SDD workflow orchestration?

Yes, you need the Beads framework installed because the orchestration relies on it to manage state, dependencies, gates, and work memory for development cycles.

Can I use multiple SDD frameworks like Spec Kit and BMad within the same project?

Yes, you can integrate multiple SDD frameworks such as Spec Kit, Superpowers, BMad, and GSD within the same project, streamlining the development process through centralized orchestration.

Why does Beads keep authoritative state instead of relying solely on GitHub Issues?

Beads keeps authoritative state to manage complex dependencies, gates, and work memory accurately, while GitHub Issues are synchronized strictly for external visibility and progress tracking.

How do I convert a GitHub Issue into a Beads bead?

To convert a GitHub Issue into a Beads bead, run the orchestrator skill to synchronize the issue, automatically pulling the task into the Beads framework for workflow execution.