Skip to content

feat: add cross-rig support to design-to-beads skill#2

Draft
sfncore wants to merge 2 commits intoXexr:mainfrom
sfncore:feat/cross-rig-design-to-beads
Draft

feat: add cross-rig support to design-to-beads skill#2
sfncore wants to merge 2 commits intoXexr:mainfrom
sfncore:feat/cross-rig-design-to-beads

Conversation

@sfncore
Copy link

@sfncore sfncore commented Mar 5, 2026

Summary

  • Auto-detects cross-rig mode from file paths in the plan's coverage matrix
  • Adds Target Rig field to issue draft template and coverage matrix
  • Phase 5 Execute: groups issues by rig, runs bd create from each rig's beads path
  • Cross-rig parent-child via bd dep add --type parent-child (--parent flag is same-DB only)
  • Cross-rig blocking deps use full prefixed bead IDs
  • Completeness review subagent validates rig assignments match file paths
  • Report includes per-rig bead ID mapping and distribution

Single-rig projects remain completely unchanged — cross-rig mode is auto-detected only when the coverage matrix shows multiple target rigs.

Companion PRs:

Test plan

  • Verify single-rig design-to-beads works unchanged
  • Test cross-rig detection from mixed file paths in plan
  • Verify Target Rig appears in draft template and coverage matrix
  • Test per-rig bd create execution (correct prefix per rig)
  • Test cross-rig parent-child wiring with bd dep add
  • Verify completeness review catches rig misassignments
  • Verify report includes per-rig breakdown

🤖 Generated with Claude Code

claude added 2 commits March 6, 2026 03:57
Multi-rig projects now handled natively. Auto-detects cross-rig mode from
file paths in the plan's coverage matrix. Issues are created from their
target rig's beads path (correct prefix + database). Cross-rig dependencies
use full prefixed bead IDs. Completeness review validates rig assignments.

Single-rig projects remain completely unchanged.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants