Scenarios
Build from a Conversation
Use this route when the decision was made in a conversation or a brainstorm and nobody needs a PRD to agree on it. The transcript, or the brainstorm’s summary, is the input, and the initiative Sofia writes from it is the spec.
The example is the room booker. On a call, the office manager and the facilities lead talked about rooms that are booked and never used. The office manager decides, and you have the transcript.
-
Turn the call into a note. Each point cites its timestamp, and both numbers appear where the two disagreed. See Clarify the Idea.
/bmad-ingest ~/Downloads/rooms-call.txtIf you start from a brainstorm, the summary
bmad-brainstormingwrote, or the report of an ideabmad-forge-ideahardened, is your note. Go to step 2. -
Have Sofia, the Product Owner, write the initiative from the note.
/bmad-agent-po write the initiative from the rooms call noteFrom a brainstorm, name its summary instead:
/bmad-agent-po write the initiative from the brainstorm summary -
Settle her open questions with the office manager, then answer Sofia in the same chat.
The office manager says a room counts as unused 15 minutes after its start, and the server frees it. -
Cut it into epics: door check-in first, then freeing no-show rooms. See Write and Slice the Initiative.
/bmad-agent-po split this initiative into epicsStep 3 settled that the server frees the room, so she has no shared decision to send to
bmad-architecture. -
Plan the first epic’s stories, and approve them. Story 1.1, showing each room on its door tablet, is marked
hitlbecause facilities mounts and pairs the tablets. See Plan an Epic’s Stories./bmad-agent-po refine the door check-in epic, then plan its stories -
Build story by story, each in a fresh chat, and mark each one done after you check it. See Build and Verify.
Story 1.1 has a person’s step. Build it with
bmad-build, have facilities mount and pair the tablets, check that a tablet shows its room, then mark it done./bmad-build 1.1/bmad-agent-po mark story 1.1 done/bmad-build 1.2Build and mark each remaining story the same way, then finish the epic in step 7. Repeat steps 5 to 7 for the second epic.
-
Run the retrospective, then close the epic. The retrospective judges the finished epic. Then Sofia validates it against its Requirements and Done when, you confirm, and she closes it. See Finish an Epic.
/bmad-retrospective 1/bmad-agent-po close the door check-in epic
What You Have at the End
Section titled “What You Have at the End”The note, the initiative and its epic files, each epic’s stories in
tickets.toml, the code, one plan per story recording its build, and a
retrospective per epic. There is no PRD, UX file, or architecture spine,
because no one needed them.
Shorter and Longer Routes
Section titled “Shorter and Longer Routes”- If the note describes one session’s work, hand it to
bmad-build, as in Make a Small Change. - If it is a few stories, ask Sofia to slice the initiative into stories directly, with no epics.
- If the decision is already written down, skip step 1 and hand the issue or paragraph to Sofia.
- If several people must agree first, take the route in Plan a Feature as a Team.
New to BMad? Start with Install BMad.