From bmad-extensions
Clean up legacy BMAD artifact outputs into the zero-padded epic/sprint folder layout, then review epic/sprint state consistency.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bmad-extensions:bmad-cleanup-artifactsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Clean up legacy flat files in implementation and planning artifacts into the current folder structure:
Clean up legacy flat files in implementation and planning artifacts into the current folder structure:
epic-{EE}/sprint-{SS}/stories/{story-key}.mdepic-{EE}/sprint-{SS}/closure/...epic-{EE}/sprint-{SS}/tests/...epic-{EE}/epic-closure/...epic-{EE}/tests/...planning_artifacts/epic-{EE}/...EE and SS must be zero-padded two-digit values (01, 02, etc.).
Load config from {project-root}/_bmad/bmm/config.yaml and resolve:
implementation_artifactsplanning_artifactsoutput_folderIf implementation_artifacts is unavailable, default to:
{output_folder}/implementation-artifacts
Story files in flat root:
{implementation_artifacts}/{story-key}.md^([0-9]+)-[0-9]+.*\.md$01 unless user provides a mapping{implementation_artifacts}/epic-{EE}/sprint-{SS}/stories/{story-key}.mdSprint closure files in flat root:
epic-*-sprint-*-retro-*.md, sprint-adversarial-*.md, sprint-redteam-*.md){implementation_artifacts}/epic-{EE}/sprint-{SS}/closure/{filename}01 unless user mapping providedEpic closure files in flat root:
epic-*-arch-drift-*.md, epic-*-functional-completeness-*.md, epic retros explicitly marked epic-level{implementation_artifacts}/epic-{EE}/epic-closure/{filename}Test evidence files in flat root:
*qa*.md, *test*.md, *verification*.md{implementation_artifacts}/epic-{EE}/sprint-{SS}/tests/{filename}{implementation_artifacts}/epic-{EE}/tests/{filename}Planning artifacts:
{planning_artifacts}/epic-{EE}/{filename}{planning_artifacts}/epic-{EE}/sprint-{SS}/{filename}Unknown files:
epic-XX, sprint-YY)stories/, closure outputs under closure/, and tests under tests/sprint-status.yaml), flag story states that reference missing story filesDONE - Moved: N, Conflicts: N, Unclassified: N, Refs Updated: N, Ref Conflicts: N, State Issues: N, Root: [implementation_artifacts]
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub ravensorb/bmad-extensions --plugin l3io-sec