Question
Is validate-workflow.xml coming back, or has its functionality been intentionally absorbed elsewhere?
If coming back: I'll submit a PR restoring an improved version based on the last known content (from 7bf05c9d~1). The 89-line task file is straightforward — load checklist, validate each item against a document, generate a report.
If intentionally removed: I'll submit a PR removing the dangling references in checklist.md (lines 36 and 66) so the validator runs clean and new users don't hit the same wall that #1324, #1351, and #1455 reported.
Summary
src/core/tasks/validate-workflow.xml is still missing from the repository. Three prior issues reported this (#1324, #1351, #1455), all closed on Jan 31 with "Resolved during beta. Closing as completed." — but the file was never restored and the broken references remain.
The file reference validator flags two broken references in src/bmm/workflows/4-implementation/create-story/checklist.md:
src/bmm/workflows/4-implementation/create-story/checklist.md
[BROKEN] core/tasks/validate-workflow.xml (line 36)
[BROKEN] core/tasks/validate-workflow.xml (line 66)
Why this matters: two different files
There's a risk of confusion between two files that sound similar but serve completely different purposes:
|
validate-workflow.xml (deleted) |
workflow.xml (still exists) |
| Task name |
"Validate Workflow Output" |
"Execute Workflow" |
| Purpose |
Run a checklist against a document, produce a PASS/FAIL validation report |
General workflow execution engine — load config, resolve variables, process steps |
| Inputs |
checklist + document to validate |
workflow.yaml path |
| Output |
validation-report-{timestamp}.md with per-item evidence |
Executes workflow steps, produces workflow output |
| Lines |
89 lines |
196 lines |
The checklist.md is explicitly about validation review — loading a checklist and running it against a story document. That's what validate-workflow.xml did. workflow.xml is the generic workflow runner and would not be a correct replacement.
Community members encountering the missing file may assume workflow.xml covers the same functionality, but it doesn't — the dedicated checklist-runner/validation-reporter was a distinct tool.
History
| Date |
Event |
| Oct 2025 |
validate-workflow.xml first created (ab05cdcd) |
| Jan 1 |
checklist.md content authored referencing validate-workflow.xml (4142972b PR #1217) |
| Jan 7 |
validate-workflow.xml deleted in cleanup commit 7bf05c9d ("fix missing scripts from installation, and add ability to exclude workflows from being added as commands in tools") — appears to be collateral deletion alongside the create-module/ directory removal |
| Jan 15 |
#1324 acknowledged: "thank you! Will resolve with update asap" |
| Jan 18 |
#1351 closed as duplicate: "already noted and responded to the other ones that its coming back before beta release" |
| Jan 19 |
checklist.md moved to current path in 6f8f0871 — broken references carried forward |
| Jan 31 |
#1324 and #1455 closed: "Resolved during beta. Closing as completed." |
| Feb 4 |
File still absent. File reference validator (PR #1494) detects both broken references. |
Prior issues
Question
Is
validate-workflow.xmlcoming back, or has its functionality been intentionally absorbed elsewhere?If coming back: I'll submit a PR restoring an improved version based on the last known content (from
7bf05c9d~1). The 89-line task file is straightforward — load checklist, validate each item against a document, generate a report.If intentionally removed: I'll submit a PR removing the dangling references in
checklist.md(lines 36 and 66) so the validator runs clean and new users don't hit the same wall that #1324, #1351, and #1455 reported.Summary
src/core/tasks/validate-workflow.xmlis still missing from the repository. Three prior issues reported this (#1324, #1351, #1455), all closed on Jan 31 with "Resolved during beta. Closing as completed." — but the file was never restored and the broken references remain.The file reference validator flags two broken references in
src/bmm/workflows/4-implementation/create-story/checklist.md:Why this matters: two different files
There's a risk of confusion between two files that sound similar but serve completely different purposes:
validate-workflow.xml(deleted)workflow.xml(still exists)validation-report-{timestamp}.mdwith per-item evidenceThe checklist.md is explicitly about validation review — loading a checklist and running it against a story document. That's what
validate-workflow.xmldid.workflow.xmlis the generic workflow runner and would not be a correct replacement.Community members encountering the missing file may assume
workflow.xmlcovers the same functionality, but it doesn't — the dedicated checklist-runner/validation-reporter was a distinct tool.History
validate-workflow.xmlfirst created (ab05cdcd)checklist.mdcontent authored referencingvalidate-workflow.xml(4142972bPR #1217)validate-workflow.xmldeleted in cleanup commit7bf05c9d("fix missing scripts from installation, and add ability to exclude workflows from being added as commands in tools") — appears to be collateral deletion alongside thecreate-module/directory removalchecklist.mdmoved to current path in6f8f0871— broken references carried forwardPrior issues
_bmad/core/tasks/validate-workflow.xmlbreaks create-story validation"7bf05c9das accidental deletion, noted the asymmetry between BMM and BMGD Scrum Master agents