bmad-os-audit-file-refs

You can audit markdown and YAML files for broken file references by scanning BMAD workflow and task documents to detect forbidden relative paths, bare filenames, and absolute system paths, reporting exact line-level violations.

BMAD workflow files require canonical {project-root}/_bmad paths or {installed_path}/ paths. The audit skips runtime variables and fenced code examples, flagging documents that violate these file-reference conventions.

Yes, you can batch review large sets of source files for path violations. The process breaks large file sets into batches, allowing multiple subagents to check markdown and YAML documents consistently in parallel.

File reference auditing skips runtime variables and fenced code examples entirely. It focuses solely on identifying nonconforming path conventions in active workflow and task markdown or YAML documents.

The best way to catch nonconforming file paths before a release is to run a convention audit on BMAD source files under src/bmm, src/core, and src/utility, validating file coverage and summarizing violations with file and line detail.