-
-
Notifications
You must be signed in to change notification settings - Fork 16
Description
Describe the bug
Version: 6.0.0-Beta.8
I've used the workflow builder quite a lot, and I decided to update bmad to the latest version yesterday.
The following message has never happened before pre Beta.1.
Steps to reproduce
Run @_bmad/bmb/agents/workflow-builder.md
EW _bmad/bmm/workflows/4-implementation/story-automator-go
⏺ Good, the story-automator-go workflow exists. Mode is Edit. Per the workflow architecture instructions, I'll now load and read the edit
step file completely before executing.
⏺ Read 1 file (ctrl+o to expand)
⏺ Now loading the orchestrator rules for context.
⏺ Searched for 2 patterns, read 4 files (ctrl+o to expand)
⏺ BMad, I've loaded the rules and checked for existing orchestration state documents. Here's what I found:
No orchestration state documents found for story-automator-go.
The output folder _bmad-output/story-automator/ doesn't exist yet, and the _bmad-output/orchestration/ folder only contains a
feedback-automator subfolder - no story-automator-go state files.
The Edit workflow requires an existing orchestration state document (orchestration-*.md) to modify. Since none exist, there's nothing to
edit yet.
What would you like to do?
- [C]reate - Switch to Create mode to initialize a new orchestration for story-automator-go
- [M]enu - Return to the main Wendy menu
- [CH]at - Discuss what you're trying to accomplish so I can route you correctly
✻ Cogitated for 55s
No it exists in _bmad/
⏺ You're right, my mistake. You want to edit the workflow itself, not an orchestration state. The target workflow is at
_bmad/bmm/workflows/4-implementation/story-automator-go/workflow.md. Let me load the correct edit step from the meta-workflow.
Expected behavior
BMB workflow to go straight to the edit step properly
Environment (if relevant)
- Model(s) used: Opus 4.6
- Agentic IDE used: Claude
- BMad version: 6.0.0-Beta.8
- Project language: Irrelevant
Screenshots or links
If applicable, add screenshots or links to help explain the problem.
PR
If you'd like to contribute a fix, please indicate you're working on it or link to your PR. See CONTRIBUTING.md — contributions are always welcome!
Additional context
Add any other context about the problem here. The more information you provide, the easier it is to help.