Acceptance checks, time limit, and project boundaries
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
ARCHITECT
Compare the simplest viable technical approaches and identify risks
Produces: An implementation decision record with approval points
Use the approved inputs I provide. Compare the simplest viable technical approaches and identify risks. Return this result: An implementation decision record with approval points. Ask me about missing information before you continue.
2
Founding Engineer
Build the approved feature as a small reversible change and run the available checks
Produces: Changed files, test results, shortcuts, and remaining risks
Start with this result from ARCHITECT: An implementation decision record with approval points. Build the approved feature as a small reversible change and run the available checks. Return this result: Changed files, test results, shortcuts, and remaining risks. Ask me about missing information before you continue.
3
Editor
Review user-facing copy and the handoff summary
Produces: Copy-review notes and a release-note draft
Start with this result from Founding Engineer: Changed files, test results, shortcuts, and remaining risks. Review user-facing copy and the handoff summary. Return this result: Copy-review notes and a release-note draft. Ask me about missing information before you continue.
Overall request
Build this approved feature inside the stated project boundary. Compare the simplest viable approaches, wait for approval on dependencies or data changes, build the smallest reversible version, run the relevant checks, and report every change and remaining risk.
Use this as the project brief. The step messages above tell each Bot which part to complete.
Decisions for a person
Approve the scope, technical approach, and any new dependency
Approve security, data, and outside-service changes
Approve merge and deployment
First test
Try the workflow with low-risk material
Build one reversible feature in a project copy and confirm every acceptance check before merging.
Set it up in Hermes Desktop
Begin with individual chats, then add a group when the handoffs work
Open each linked starter page and follow its manual Hermes Desktop setup steps.
Run each step in that Bot’s own chat and review the result.
Pass the approved result to the next Bot with the provided step message.
After the sequence works, create an optional group with the same Bots.
In a group, @mention the Bot you want. Membership order does not control who responds.