Repository navigation
Is the ticket tree only for code work? #3147
BenNewman100
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
So I have just started using BMAD (I’m on the v7 beta from the main branch). This is one of the first things I noticed when I started working with tickets.
Some of my tickets aren’t code. They’re planning sessions I do with the agent: reviewing an architecture doc a batch at a time, brainstorming how the roadmap gets planned, and moving my old planning over from OpenSpec. I put them in the tree because it gave me an order and a “what’s next”. But every one of them gets offered bmad-build as the way to start it, which feels a bit off.
I know I can just run the right skill myself. What I’m getting at is that a ticket has no way to say it isn’t a build. So anything that starts work from the tree, whether that’s Sofia, a loop or a board, falls back to build.
The docs describe the tree as “tickets a coding agent can build from”, so maybe that’s intended and planning like this just doesn’t belong there. If so, where does planning that spans several sessions live, and how do you keep track of what’s next? If it does belong there, should a ticket be able to say what kind of work it is?
All reactions