The BMB workflow edit mode creates validation reports in the target workflow folder ({targetWorkflowPath}/validation-report-{workflow_name}.md) instead of in the BMB output folder
({bmb_creations_output_folder}). This causes validation reports (which are session artifacts) to be mixed in with workflow source files, potentially leading to accidental commits of
ephemeral files into the workflow source.
Steps to reproduce
- Run /bmad:bmb:workflows:workflow and select Edit mode
- Select a workflow to edit
- Choose to validate the workflow (either before or after edits)
- Observe that validation reports are created in the workflow's own folder (e.g., bmad-custom-modules-src/.../my-workflow/validation-report-*.md)
Expected behavior
Validation reports should be created in {bmb_creations_output_folder} (typically _bmad-output/bmb-creations/) alongside the edit plan and other session artifacts. This keeps
session-specific files separate from the workflow source being edited.
Environment (if relevant)
- Model(s) used: Claude Opus 4.5
- Agentic IDE used: Claude Code
- BMad version: v6.0.0-alpha.23
Screenshots or links
The issue is in the BMB workflow edit validation step. From step-e-06-validate-after.md:
validationReport: '{targetWorkflowPath}/validation-report-{workflow_name}.md'
This should likely be:
validationReport: '{bmb_creations_output_folder}/validation-report-{workflow_name}-{date}.md'
PR
Not currently working on a fix, but happy to contribute if desired. The fix would involve updating the validationReport path in:
- steps-e/step-e-06-validate-after.md
- Possibly steps-v/step-01-validate.md and related validation steps
Additional context
This was discovered during an edit session on a custom workflow. Three validation reports were created in the workflow folder and had to be manually moved to _bmad-output/bmb-creations/ before committing to avoid polluting the workflow source with session artifacts. The edit plan is already correctly placed in {bmb_creations_output_folder}, so validation reports should follow the same pattern for consistency.
The BMB workflow edit mode creates validation reports in the target workflow folder ({targetWorkflowPath}/validation-report-{workflow_name}.md) instead of in the BMB output folder
({bmb_creations_output_folder}). This causes validation reports (which are session artifacts) to be mixed in with workflow source files, potentially leading to accidental commits of
ephemeral files into the workflow source.
Steps to reproduce
Expected behavior
Validation reports should be created in {bmb_creations_output_folder} (typically _bmad-output/bmb-creations/) alongside the edit plan and other session artifacts. This keeps
session-specific files separate from the workflow source being edited.
Environment (if relevant)
Screenshots or links
The issue is in the BMB workflow edit validation step. From step-e-06-validate-after.md:
validationReport: '{targetWorkflowPath}/validation-report-{workflow_name}.md'
This should likely be:
validationReport: '{bmb_creations_output_folder}/validation-report-{workflow_name}-{date}.md'
PR
Not currently working on a fix, but happy to contribute if desired. The fix would involve updating the validationReport path in:
Additional context
This was discovered during an edit session on a custom workflow. Three validation reports were created in the workflow folder and had to be manually moved to _bmad-output/bmb-creations/ before committing to avoid polluting the workflow source with session artifacts. The edit plan is already correctly placed in {bmb_creations_output_folder}, so validation reports should follow the same pattern for consistency.