From relay
Import BMAD story and epic artifacts into Beads as trackable issues with dependencies. Use when the user says 'import stories', 'sync BMAD into Beads', 'import epics', or when Beads has no issues but sprint-status.yaml has backlog stories. Shows a dry-run plan before applying. Can filter by specific epic.
How this skill is triggered — by the user, by Claude, or both
Slash command
/relay:bmad-importThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
BMAD produces planning artifacts (epics, stories in sprint-status.yaml) but those aren't tracked as issues. This skill bridges the gap — it reads the BMAD plan and creates corresponding Beads issues with proper dependencies, so work can be picked up, assigned, and tracked.
BMAD produces planning artifacts (epics, stories in sprint-status.yaml) but those aren't tracked as issues. This skill bridges the gap — it reads the BMAD plan and creates corresponding Beads issues with proper dependencies, so work can be picked up, assigned, and tracked.
python -c "
from famdeck.bmad_import.importer import import_stories
result = import_stories('$PWD', dry_run=True)
print(result.summary())
"
Show the plan to the user — which stories will be created, under which epics, with what dependencies. Wait for confirmation before applying.
python -c "
from famdeck.bmad_import.importer import import_stories
result = import_stories('$PWD')
print(result.summary())
"
To import only stories from one epic (e.g., epic 1):
python -c "
from famdeck.bmad_import.importer import import_stories
result = import_stories('$PWD', epic_filter=1)
print(result.summary())
"
bd list shows no issues but sprint-status.yaml has backlog stories/autopilot pre-flight detects missing Beads issuesnpx claudepluginhub ivintik/private-claude-marketplace --plugin famdeck-relayDecomposes GitHub issues into structured Beads epics, tasks, and sub-tasks with objectively verifiable acceptance criteria and dependencies. Useful for planning actionable work in Beads projects.
Converts design documents, PRDs, or task lists into structured beads issues with epic hierarchy, validated dependencies for maximum parallelization, and three independent subagent reviews.
Emits and maintains sprint-status.yaml as a sequencing system-of-record. Orders stories by epic and dependency, assigns parallel-set waves, and drives status lifecycle.