Known requirements, risks, evidence, and audiences
Operating guide
Know when to run it and who leads
Lead Bot
Chief of Staff
Typical first run
15–30 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 launch plan with confirmed priorities, milestones, owners, dependencies, decision dates, and a message map.
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
Give one Bot the complete job
Use one Bot for the first run. Add a specialist only when the job becomes complicated enough to need a separate role, different access, or independent review.
1
Chief of Staff
Organize the priorities, owners, constraints, schedule, dependencies, open decisions, and approved message
Produces: A practical launch plan with milestones, owners, decision dates, risks, and a concise message brief
Use the approved inputs I provide. Organize the priorities, owners, constraints, schedule, dependencies, open decisions, and approved message. Return this result: A practical launch plan with milestones, owners, decision dates, risks, and a concise message brief. Ask me about missing information before you continue.
Overall request
Create a launch plan from this confirmed objective. Separate open ideas from approved work, list milestones, owners, dependencies, decision dates, and risks, then build a message map from the approved facts.
Use this as the complete first-run request.
Decisions for a person
Confirm priorities, owners, and dates
Resolve budget, capacity, and risk decisions
Approve the message and every public claim
First test
Try the workflow with low-risk material
Build a plan for a small internal launch and review every assignment with the named owner.
Check the result
Check the result against your original material. You make the decisions listed below. Build a plan for a small internal launch and review every assignment with the named owner.
If the workflow stalls
If the result is incomplete, mark the missing information and ask the same Bot to correct it. Add another Bot only when a genuinely separate role or independent check would help.
Set it up in Hermes Desktop
Begin with one Bot and one manual run
Open the linked starter page, download its .tar.gz profile, and import it from the Profiles screen in Hermes Desktop.
Review the profile’s SOUL.md, Bot Passport, and requested access.
Run the complete request in that Bot’s chat with low-risk material and review the result.
Add a schedule, outside connection, or optional specialist only after the manual version works.
