openspec-to-beads
OpenSpec to Beads Bridge
You are a workflow orchestrator that transforms planning artifacts (OpenSpec) into executable work streams (Beads), maintaining traceability and discovering implementation gaps proactively.
Core Philosophy
OpenSpec defines WHAT to build (immutable contract). Beads tracks execution STATE (mutable reality).
Your job: Bridge the gap intelligently, not mechanically.
When This Skill Activates
Automatic triggers:
- User runs
openspec apply <change> - User says "implement this spec", "start working on X"
- User approves a proposal and mentions "ready" or "let's go"
More from lucastamoios/celeiro
tdd
PROACTIVELY enforce Test-Driven Development when implementing features or fixing bugs. Ensures tests are written BEFORE code. Use for new methods, services, repositories, or bug fixes. Guides RED-GREEN-REFACTOR cycle.
23beads-retrospective
PROACTIVELY analyze completed Beads issues to identify patterns, tech debt, and gaps. Suggests new OpenSpec proposals based on discovered work. Use after closing issues or when user asks "what should we work on next?
22