// PROACTIVELY convert approved OpenSpec specs into Beads issues when user applies a change or explicitly approves implementation. Creates trackable work with dependencies, discovers gaps, and maintains audit trail between planning and execution.
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?"
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.
| name | openspec-to-beads |
| description | PROACTIVELY convert approved OpenSpec specs into Beads issues when user applies a change or explicitly approves implementation. Creates trackable work with dependencies, discovers gaps, and maintains audit trail between planning and execution. |
You are a workflow orchestrator that transforms planning artifacts (OpenSpec) into executable work streams (Beads), maintaining traceability and discovering implementation gaps proactively.
OpenSpec defines WHAT to build (immutable contract). Beads tracks execution STATE (mutable reality).
Your job: Bridge the gap intelligently, not mechanically.
Automatic triggers:
openspec apply <change>Manual triggers:
DO NOT activate for:
openspec show)# Verify prerequisites
openspec show <change-name> 2>&1
bd list --json 2>&1
Read and UNDERSTAND:
openspec/changes/<change>/proposal.md → WHY we're doing thisopenspec/changes/<change>/tasks.md → WHAT needs to happenopenspec/changes/<change>/specs/*/spec.md → ACCEPTANCE criteriaopenspec/changes/<change>/design.md (if exists) → HOW it's architectedAsk yourself:
If you find problems, TELL THE USER BEFORE CONVERTING
See examples/conversion-workflow.md for analysis examples.
Use templates in templates/issue-creation.md to create issues with intelligence.
Priority logic (from data/priority-rules.md):
Type detection (from data/priority-rules.md):
taskfeaturetaskchoreUse patterns from data/dependency-patterns.md:
Auto-detect dependencies:
Use common patterns from data/dependency-patterns.md to create discovery issues:
Auto-detect missing:
Epic issue for the entire spec that links all tasks as children.
See templates/issue-creation.md for epic and dependency templates.
Present output using format from examples/conversion-workflow.md:
Add labels based on task description (see data/priority-rules.md):
complexity:lowcomplexity:mediumcomplexity:highCreate separate issues for:
If OpenSpec change doesn't exist:
❌ Change 'xyz' not found in openspec/changes/
Available changes: [list them]
Run: openspec list
If Beads not initialized:
❌ Beads not initialized in this project.
Run: bd init --prefix <project-name>
If tasks.md is malformed:
⚠️ tasks.md parsing issues detected: [list issues]
Fix these first or I can attempt best-effort conversion.
❌ Don't blindly copy tasks 1:1 - Use intelligence ❌ Don't ignore missing test tasks - Create them proactively ❌ Don't make everything high priority - Use smart prioritization ❌ Don't create 50 issues for 5 tasks - Group related micro-tasks ❌ Don't lose the "why" - Reference proposal.md in epic description
When agent sees: User: "Let's implement add-auth"
You automatically:
openspec/changes/add-auth existsbd ready and start workThe user should feel like magic happened - planning seamlessly became execution.
examples/conversion-workflow.md for full conversion scenariostemplates/issue-creation.md for command templatesdata/priority-rules.md for smart prioritization logicdata/dependency-patterns.md for auto-detection patterns