Description
The plugin published at tag v6.2.2.0 (2026-03-31) — the latest available on the claudev marketplace (urso/claudev) which sources this repo — appears to be missing the workflow.md file for nearly every skill.
Each skill's SKILL.md says:
Follow the instructions in ./workflow.md.
...but ./workflow.md does not exist in the skill's directory. This affects bmad-dev-story and, on inspection, the overwhelming majority of skills under plugins/bmad/skills/ (bmad-create-story, bmad-code-review, bmad-quick-dev, bmad-sprint-status, and ~55 others — both bmad-* and gds-* variants).
The published plugin is also stale relative to upstream
The README states this repo syncs from bmad-code-org/BMAD-METHOD weekly (every Wednesday), with version tracking via .upstream-versions/<id>.json. In practice, the most recent tag here is v6.2.2.0 from 2026-03-31, tracking upstream BMAD Method v6.2.2.
The official upstream repo (https://github.com/bmad-code-org/BMAD-METHOD/releases) has since moved on to v6.10.0, released 5 days before this report. So the automated sync appears to have stalled several months ago — this plugin has not picked up any of the upstream changes between v6.2.2 and v6.10.0, and the last version it did publish is also the one missing the workflow.md files described above.
Both issues likely need addressing together: resuming the upstream sync, and making sure the sync/packaging step actually copies each skill's workflow.md (or whatever the current upstream equivalent is) into the published plugin.
Steps to reproduce
- Install
bmad@claudev (or fetch v6.2.2.0 of this repo directly)
- Inspect e.g.
plugins/bmad/skills/bmad-dev-story/
- Only
SKILL.md and checklist.md are present — no workflow.md
$ ls plugins/bmad/skills/bmad-dev-story/
SKILL.md checklist.md
Expected behavior
- The plugin tracks current upstream BMAD-METHOD releases (or at least resumes the weekly sync it claims to run).
- Each skill directory contains the
workflow.md (or equivalent) file its SKILL.md references, so the skill is actually executable.
Additional context
Would appreciate either a patch release restoring the missing files and catching up the sync, or confirmation of what changed upstream (e.g. workflow format moved to XML — _shared/tasks/workflow.xml exists in the package) that would explain the omission.
Happy to help narrow this down further if useful.
Description
The plugin published at tag
v6.2.2.0(2026-03-31) — the latest available on theclaudevmarketplace (urso/claudev) which sources this repo — appears to be missing theworkflow.mdfile for nearly every skill.Each skill's
SKILL.mdsays:...but
./workflow.mddoes not exist in the skill's directory. This affectsbmad-dev-storyand, on inspection, the overwhelming majority of skills underplugins/bmad/skills/(bmad-create-story, bmad-code-review, bmad-quick-dev, bmad-sprint-status, and ~55 others — bothbmad-*andgds-*variants).The published plugin is also stale relative to upstream
The README states this repo syncs from
bmad-code-org/BMAD-METHODweekly (every Wednesday), with version tracking via.upstream-versions/<id>.json. In practice, the most recent tag here isv6.2.2.0from 2026-03-31, tracking upstream BMAD Methodv6.2.2.The official upstream repo (https://github.com/bmad-code-org/BMAD-METHOD/releases) has since moved on to
v6.10.0, released 5 days before this report. So the automated sync appears to have stalled several months ago — this plugin has not picked up any of the upstream changes betweenv6.2.2andv6.10.0, and the last version it did publish is also the one missing theworkflow.mdfiles described above.Both issues likely need addressing together: resuming the upstream sync, and making sure the sync/packaging step actually copies each skill's
workflow.md(or whatever the current upstream equivalent is) into the published plugin.Steps to reproduce
bmad@claudev(or fetchv6.2.2.0of this repo directly)plugins/bmad/skills/bmad-dev-story/SKILL.mdandchecklist.mdare present — noworkflow.mdExpected behavior
workflow.md(or equivalent) file itsSKILL.mdreferences, so the skill is actually executable.Additional context
Would appreciate either a patch release restoring the missing files and catching up the sync, or confirmation of what changed upstream (e.g. workflow format moved to XML —
_shared/tasks/workflow.xmlexists in the package) that would explain the omission.Happy to help narrow this down further if useful.