Independent guide to useful Bots · Across platforms
Bot Cabinet
Back to workflows
Multi-Bot workflow

Product and technology direction

A comparison of product and technology choices, plus a small prototype to test the chosen approach.

Designed for: Founders and small product teams choosing what to test and how to build it

Set up Nova Download the workflow guide
Full workflow and setup details
Before you begin

Gather the information the Bots need

  • The product goal, intended user, and current evidence
  • The current system and business constraints
  • Budget, time limit, risk limits, and acceptance checks
Operating guide

Know when to run it and who leads

Lead Bot
Nova
Typical first run
30–60 minutes for a first manual run
When to run it
When a person supplies the approved brief and starts the workflow

Use this workflow when you need a comparison of product and technology choices, plus a small prototype to test the chosen approach.

Access for the first run
  • The approved inputs listed on this page
  • Only the files, sources, and services required for this run
  • No sending, publishing, spending, or live-system changes without approval
Run the first version one step at a time

Send one clear message to each Bot

Start in individual Bot chats. After you approve a result, paste it into the next Bot’s chat with the message shown below. This gives you a clear handoff and keeps the order predictable.

1

Nova

Identify the product assumptions and the evidence needed for the next decision

Produces: A product hypothesis and evidence brief
Use the approved inputs I provide. Identify the product assumptions and the evidence needed for the next decision. Return this result: A product hypothesis and evidence brief. Ask me about missing information before you continue.
2

Architect

Compare practical technical directions for the approved product test

Produces: An architecture decision record with costs, risks, and approval points
Start with this result from Nova: A product hypothesis and evidence brief. Compare practical technical directions for the approved product test. Return this result: An architecture decision record with costs, risks, and approval points. Ask me about missing information before you continue.
3

Founding Engineer

Build the approved direction as the smallest reversible prototype

Produces: A working prototype, acceptance-check results, and a decision log
Start with this result from Architect: An architecture decision record with costs, risks, and approval points. Build the approved direction as the smallest reversible prototype. Return this result: A working prototype, acceptance-check results, and a decision log. Ask me about missing information before you continue.

Overall request

Help choose the next product and technology direction from the confirmed evidence and constraints. Compare practical options, mark every approval point, and build only the smallest prototype I approve in a disposable project copy.

Use this as the project brief. The step messages above tell each Bot which part to complete.

Decisions for a person

  • Confirm the user problem and product promise
  • Choose the technical direction and approve vendors, dependencies, budget, and risk
  • Approve repository access, real data use, and any merge or release
Handoff rules

Move only approved work to the next Bot

  1. 1

    Nova hands the approved output—a product hypothesis and evidence brief—to Architect.

  2. 2

    Architect hands the approved output—an architecture decision record with costs, risks, and approval points—to Founding Engineer.

First test

Try the workflow with low-risk material

Build one small prototype with sample data in a separate project copy. Check its test results before choosing how to build the real product.

Check the result

Check the result against your original material. You make the decisions listed below. Build one small prototype with sample data in a separate project copy. Check its test results before choosing how to build the real product.

If the workflow stalls

If a handoff is incomplete, return it to the Bot that produced it with the missing information marked. Do not move to the next Bot until a person approves the corrected result.

Set it up in Hermes Desktop

Begin with individual chats, then add a group when the handoffs work

  1. Open each linked starter page, download its .tar.gz profile, and import it from the Profiles screen in Hermes Desktop.
  2. Review each imported profile’s SOUL.md, Bot Passport, and requested access.
  3. Run each step in that Bot’s own chat and review the result.
  4. Pass the approved result to the next Bot with the provided step message.
  5. After the sequence works, create an optional group with the same Bots. In a group, @mention the Bot you want.
Read the official Bot Mode guide