Skip to content

Plan

Plan the Work

Use this page when the work is bigger than one build session. Plan answers three questions: what exactly, how, and in what order? It turns a clear intent into the initiative’s requirements, settles the decisions that separately built parts must share, and breaks each epic into stories an agent can build one session at a time.

Plan
You start withA clear intent from Clarify, or one you already have: an issue, notes, a brief, an existing PRD
You produceThe initiative and epic files with their requirements; a PRD, UX files, and an architecture spine when the work needs them; each epic’s stories in build order
It is done whenThe next epic’s stories are planned and you have approved them
Skip it whenThe work fits one session: go to Build a Change
What comes nextBuild and Verify: build the first story that is ready

You do not need to remember the order. The next step always follows from the state of the initiative file, then of each epic file. Ask Sofia, the Product Owner (bmad-agent-po), “what’s next?” at any point and she names it.

Sofia sizes new work first: one story or bug becomes a standalone ticket, several stories stay one epic, and more than one epic becomes an initiative. She proposes one epic unless a distinct outcome, or a part people can use early, splits it.

With no initiative yet:

/bmad-agent-po write the initiative from my-notes.md

With one:

/bmad-agent-po what's next?

The initiative's states, in order The initiative's states in order, each with its next step: no initiative yet, Sofia writes it; open questions, Sofia walks them with you; not sliced, Sofia cuts it into epics; shared design, optionally bmad-ux, adopted; shared decisions, optionally bmad-architecture, adopted; epic not refined, Sofia refines it; no stories yet, Sofia plans them; stories ready, bmad-build, one per chat. INITIATIVE No initiative yet Sofia writes it INITIATIVE Open questions Sofia walks them with you INITIATIVE Not sliced Sofia cuts it into epics INITIATIVE · optional Shared design? bmad-ux, adopted INITIATIVE · optional Shared decisions? bmad-architecture, adopted EPIC Epic not refined Sofia refines it EPIC No stories yet Sofia plans them STORY Stories ready bmad-build, one per chat

StateNext stepPage
No initiative yetSofia writes it from what you haveWrite and Slice the Initiative
No initiative yet, and people must agree on what the product isOptionally, John, the Product Manager, first writes a PRD or the planning document that fitsWrite a PRD
Open questions or assumptions in the initiativeSofia walks them with youWrite and Slice the Initiative
Not slicedSofia cuts it into epicsWrite and Slice the Initiative
The interface matters, or epics must share decisionsbmad-ux, bmad-architecture, then Sofia adopts their filesDesign UX and Architecture
An epic not yet refinedSofia works out what its stories must agree onPlan an Epic’s Stories
A refined epic with no storiesSofia plans its storiesPlan an Epic’s Stories
Stories readyBuild themBuild and Verify

An input added later, such as a UX design or an edited PRD, goes back to Sofia to update the initiative. She keeps every requirement id and tells you which stories no longer match.

Most work needs only the initiative and its epics. Add a document only when it answers a question the work has:

AddWhen
A PRDSeveral people must agree on what the product is, or several epics must not diverge; integrations or SLAs are involved
UX filesThe interface is a significant part of the outcome
An architecture spineTwo epics, or two agents, could otherwise make incompatible choices, or the stack is still open

UX goes before architecture, at the initiative and on each epic, so the design can inform the technical choices. UX can also come earlier and feed the PRD. The architecture spine comes after Sofia writes and slices the initiative, because it reads it. For kept code, such as a kept prototype, it runs before she slices, to record the decisions the code already made. Each can still run on one epic instead of the whole initiative. Plan Inside an Organization shows the order sign-offs set.

Tickets kept in the repository need no setup. For a tracker, or a store shared by several repos, see Set Up the Ticket Tree.