Getting a solution built
Build it ▾ hands a solution to your AI builder or your developers; the builder reports it live, or you ship it.
Build it ▾ sits in the header of every solution that isn't delivered or abandoned. It hands the solution to the people, or the AI builder, who will build it. When the page is in one column (a side panel or a phone), the same action is a full-width green bar at the top of Overview, above About.
AI-builder products
The main button reads Build it with <your builder> (Lovable, Cursor, Claude Code, Replit…, or "your AI builder" when Bonzaii doesn't know which one). It opens the prompt window:
- While the AI writes the prompt, the window counts the seconds.
- When it's ready, the prompt sits in a box you can edit before copying. Copy prompt copies it and shows Copied ✓. Regenerate writes a new one.
- The prompt always says what to build; why (the problem, plus one line of evidence with its code); where it goes (the area or parent feature, and the screen from Product structure when there is one); the acceptance criteria as Given / When / Then; what's out of scope, including "don't change other features"; and the exact feature name to use, so Bonzaii can match the feature later. AI-powered solutions also get their AI usage rules.
- The prompt ends by asking your builder to report back when it's published: "When this is published, report it to Bonzaii: deliver solution O-0xx (mark_solution_delivered) and attach the changed or new feature."
- The last prompt is saved on the solution. Reopening the window shows it at once ("Generated 17 Nov · Regenerate") without using AI again.
The ▾ menu has Copy prompt (the same prompt; the window shows a paste hint for your builder), Copy as Markdown brief (a plain brief from the solution's fields, no AI), Generate PRD and Dev tickets.
Traditional products
The main button is Dev tickets. The ▾ menu has Generate PRD, Copy as Markdown brief and Copy prompt for an AI builder.
Dev tickets
Dev tickets splits the work by layer: Database, Backend, Design, Frontend and QA, one ticket per layer the solution really touches (Frontend and Backend work are never in the same ticket). Each ticket has:
- a title starting with the solution code and layer, for example "O-005 · BE · Weekly digest job";
- a description, and the solution's acceptance criteria (Given / When / Then) on the ticket that delivers them;
- Blocked by: Database and Backend come before the Frontend that uses them;
- a size, S, M or L, and labels (the product, the release code, the area).
The window groups the tickets by type, with a filter for All, Frontend or Backend. Copy on a ticket, Copy group, Copy all (Markdown) and Copy as CSV for a Jira or Linear import (columns Summary, Description, Issue type, Labels, Story points with S = 1, M = 3, L = 5, Blocked by). The CSV goes to your clipboard: paste it into a .csv file to import it. Add as task (or Add all as tasks) creates a Bonzaii task for the ticket that blocks the solution, so its readiness counts it; the task's type follows the layer and its description says what it is blocked by. Tickets are saved on the solution, so reopening the window never writes them again (Regenerate does, with AI).
Building a whole release
A planned release has its own Build it ▾ in the release header (feature green). In one column (a side panel, a phone) it's the green bar at the top of the release's Overview. It isn't shown on builder releases or cancelled ones, and it's greyed out with a tip while the release has no solutions.
AI-builder products: Build it with Lovable (5) opens one window with one prompt per solution, not one giant prompt: AI builders do better with one change at a time.
- The order: solutions others depend on first (an open task that blocks one solution and is about another), then new features before improvements, then by Impact. Drag a row (or use the arrow keys on its handle) to change it; the order is kept.
- Each row shows its number, code and name, New or Improvement, and its state (Not sent, In build, Live). Copy prompt is green on the next row to copy. Open a row to read or edit its prompt.
- Prompts already written for a solution are reused; only the missing ones are written, one after another, and each appears as soon as it's ready. The window says so: "5 prompts · 3 already written · 2 to write". The AI allowance is checked once for the whole set.
- Every prompt ends with its own report-back line ("deliver solution O-0xx") and "This is part of release R-0xx; don't change the other items in it."
- Copy all as one copies every prompt in order, with "--- Prompt 2 of 5 ---" separators, for builders that take a long task (Claude Code, Cursor).
- Copying a prompt moves that solution to In build. The release header shows the progress, for example "Build: 2 of 5 sent · 1 live", and History says "Release sent to build".
When your connected builder publishes, each publish reports its solutions: they are delivered one by one into the release (the Shipped list shows each publish as "part of R-0xx"), and when the last one is live the release ships by itself, with one celebration and See it in your product (the Feature Tree in focus on all its features). Without a connection, each row gets Mark as live (15 seconds to Undo); once all are live the release ships the same way. If every solution is live but the release is still open, the green action is Ship release.
The release's next step follows its state: Build it with Lovable (5) → 2 of 5 live · Copy next prompt → Ship release → See it in your product.
Traditional products: the button is Dev tickets ▾, one window with a section per solution (the layered tickets above, Copy each, Copy all, CSV). Shipping stays the normal Ship release.
The ▾ menu has Copy as Markdown brief (the whole release, no AI) and Generate PRD (one document with a section per solution; a solution's saved PRD is reused, new ones are saved on their solution).
In build
The first time you copy a prompt or a brief, the solution becomes In build: the header pill reads "In build · Lovable" and History says "Sent to Lovable" with your name. Copying again changes nothing else. AI actions use your AI allowance as usual; the brief and a saved prompt don't. The pill goes away once the solution is delivered.
On AI-builder products the header (or the bar) then follows the solution:
- Connected builder: "Waiting for Lovable to publish" (grey), with Copy prompt again and Mark as live manually. When your builder publishes and reports it, the solution is delivered by itself, in a builder release, and the ship celebration plays.
- No connection: Mark as live (green), with Copy prompt again.
- Delivered: See it in your product.
Mark as live (AI-builder products)
Mark as live is the fallback when the product isn't connected or the builder didn't report the publish (for people with Builder access). Pick the release: the one the solution is already planned in is preselected; otherwise a new release dated today (a builder release), or another open release. The window shows the feature it creates or improves. Mark as live ships it 15 seconds later: Undo in the message keeps it In build. It's the same delivery as your AI builder's publish, so it works on AI-builder products whose structure is locked. Criteria copied from the solution are marked "Not confirmed — from the plan". The release is published and the ship celebration plays; see Ship a release.
Shipping on traditional products
Traditional products have no Mark as live: the team ships the solution's release (Ship release, see Ship a release), or sets the solution to Delivered in its state menu. Delivered always runs the full delivery: the feature is created or improved and the criteria are copied, never just a state change.
Changing a live feature
In Bonzaii a change to a live feature is an improvement: a solution that improves that feature, so the request keeps its trail (evidence, plan, release, shipped). Change it ▾ sits in the header of every live or paused feature, in the same place and the same green as Build it ▾ on solutions.
- AI-builder products: the main button reads Change it with <your builder>.
- Traditional products: the main button reads Request a change, and the ▾ menu also has Dev tickets.
- The ▾ menu has Quick change (the main button), Plan an improvement (full form…) (the Add Improvement window, already pointing at this feature), Copy prompt and Generate PRD.
- In one column (side panel, phone) the same action is a full-width green bar at the top of Overview. While a change from it is In build, the bar shows that improvement's state (for example "Weekly tidy-up: waiting for Lovable to publish", with Copy prompt again and Mark as live manually), then returns to Change it once it's delivered.
Quick change asks one thing, What should change? (for example "Let people pin tags to the top"). You can also link evidence (an insight or a problem) and pick Fix or Improvement. Create & write the prompt then:
- creates an improvement (O-0xx) for this feature, named from your request, with the request as its "what it does";
- writes a change prompt in the same prompt window as Build it (editable, Copy prompt, saved on the improvement). The prompt starts with the feature as it is today (what it does, its live criteria, where it lives), asks only for the change (new or changed criteria as Given / When / Then), and says "Don't rebuild the feature; keep everything else as it is", plus what's out of scope.
The improvement shows in the feature's Improvements module straight away. Copying moves it to In build; your builder's publish report (or Mark as live on AI-builder products, the release or Delivered on traditional ones) ships it like any solution. On traditional products, Request a change creates the improvement and opens it, and its Build it ▾ writes the Dev tickets.
On AI-builder products the window first asks what's wrong: Change the product (the steps above) or The map is wrong (a missing feature, wrong parent, wrong name, should be removed, other). The map choice works as before: your AI builder gets a task at its next sync, and you get a prompt to paste now. Report a mapping issue on Feature Tree and map cards opens this same window with "The map is wrong" already picked.