Skip to content

Scenarios

Turn a Prototype into a Product

Use this route when someone built a quick version to see whether an idea works, people liked it, and you now want to build it properly. The prototype answers questions; it is not the code you ship.

The example is the room booker. In an afternoon, someone prompted an agent into a floor-plan view: pick a floor, and see which rooms are free. People used it all week. It has no tests, knows only one floor, and reads the bookings table directly.

Turn a Prototype into a Product, step by step In Clarify, the prototype and your notes on what it taught; in Plan, Sofia writes the initiative and cuts epics, UX and architecture are adopted, and Sofia plans the first epic's stories; in Build and verify, bmad-build rebuilds it story by story. CLARIFY The prototype used for a week CLARIFY Your notes what it taught you PLAN Sofia the initiative and epics PLAN UX, architecture adopted by Sofia PLAN Sofia the first epic's stories BUILD bmad-build built again, properly

  1. Decide on purpose what happens to it: throw the code away and keep its lessons, keep the code, or drop the idea. If it came from John’s prototype plan, built by bmad-build-auto, John asks this when the build reports back. Here the code goes. See Clarify the Idea.

  2. Write down what it taught you in a short file beside the prototype, such as floor-plan-notes.md. A prototype planned with John records this in its plan’s Outcome instead.

    # Floor-plan prototype: what it taught us
    - Worked: people want free rooms at a glance, by floor.
    - Surprised us: people tapped a free room and expected to book it there.
    - Never handled: other floors, rooms that change size, tests.
    - Decision: throw the code away, keep these lessons.
  3. Have Sofia, the Product Owner, write the initiative, then cut it into epics. Her open questions collect what the prototype never had to answer. See Write and Slice the Initiative.

    /bmad-agent-po write the initiative from floor-plan-notes.md
    /bmad-agent-po split this initiative into epics
  4. Design what the prototype skipped, each skill in its own chat, then have Sofia adopt both. The spine settles what the prototype dodged, such as reading the bookings table directly. See Design UX and Architecture.

    /bmad-ux design the floor-plan view and its states
    /bmad-architecture settle the decisions the floor-plan epics share
    /bmad-agent-po adopt the design and the spine
  5. Plan the first epic’s stories, then build them one per chat. See Plan an Epic’s Stories and Build and Verify.

    /bmad-agent-po refine the first epic, then plan its stories
    /bmad-build 1.1
    /bmad-agent-po mark story 1.1 done

    Repeat for each story. Then run the retrospective on the epic, and have Sofia validate and close it, as in Finish an Epic. Then repeat this step for each remaining epic, naming that epic and its own story numbers.

An initiative whose requirements came from what people actually used, design files for the screen, the decisions the epics share, tested code built to them, and a retrospective per epic.

The prototype’s code is worth keeping. Record its rules with bmad-project-context, have Sofia write the initiative from the prototype, and run bmad-architecture to record the decisions the kept code already made, so Sofia adopts them before she slices the rest. See Change an Existing Codebase.

New to BMad? Start with Install BMad.