The argument in one line.
Most creators use /goal at its default single-mission level, but upgrading it with custom presets like /goal overnight, /goal night-queue, and /goal batch—wired into Slack with approval gates—lets you run autonomous revenue loops while you sleep.
Read if. Skip if.
- A founder or operator running a business who's using /goal at default settings and wants to unlock parallel agent execution and overnight task completion without manual oversight.
- A technical operator managing Slack-resident AI agents (Hermes, Claude Code, or similar) who needs approval gates and risk-stratified autonomy to scale task delegation safely.
- An agency or product team running multiple concurrent experiments (landing pages, ad variations, design iterations) and looking to batch and queue /goal operations instead of executing them serially.
- You're not using Claude Code, Hermes, or similar Slack-integrated agent frameworks — this breakdown assumes that specific technical stack and won't translate to other LLM interfaces.
- You're still in the single-agent, single-task phase of AI adoption — the revenue unlock here depends on already running multiple parallel missions and needing orchestration, not foundational /goal usage.
The full version, fast.
The default /goal slash command in Claude Code and similar agent stacks is underused, and treating it as a single-shot task runner leaves most of its revenue leverage on the table. The upgrade is to wrap /goal in custom presets � overnight for unattended long builds with a morning executive packet, night-queue for ranking and launching the safest high-leverage work autonomously, batch for splitting open Slack threads into parallel lanes, plus continue, pause, and status for state control � all routed through a Slack-resident control tower. The non-negotiable is a definition of done on every mission and approval gates around anything that touches money, customers, or production, so agents move fast internally while risky actions stay packaged for your review.
Chat with this breakdown.
Modern Creator members can chat with any breakdown — ask for the hook, quote a framework, find the exact transcript moment. Unlocks at T2: refer 3 friends + add your own API key.
Create a free account →Where the time goes.

01 · Cold open + revenue framing
/goal has shipped in Claude Code, Codex, Hermes, Open Claw — Eric reframes it as a revenue tool, not just a dev convenience, and previews that most people are using it at the base level.

02 · Live example — /goal'ing open Slack threads
Walks through using /goal inside Slack with his Hermes agent (Codex as the frontier model). Asks 'what are the open threads, can we /goal them?' to drain a queue of half-spec'd work without re-checking each one.

03 · Defining 'done' for a /goal
Core principle: every /goal needs an explicit definition-of-done outcome. Examples given: 'design 50 ads in this style, this copy' or 'three landing page variants pulled from Mobbin MCP'.

04 · Upgrading /goal — the custom preset registry
Shows his Hermes /goal registry: /goal overnight, /goal status, /goal pause, /goal resume, /goal remove, /goal business-operator, /goal big-op, /goal batch open-threads, /goal continue, /goal open-thread scope. Calls out the historical Ralph (Wiggum) loop as the predecessor, now baked in.

05 · Batch and continue — multiple goals at once
Default is one goal at a time, but /goal batch lets you fan out across Slack threads, and /goal continue lets a paused goal resume from a clarifying question without manual reprompting. Argues the Kanban board most teams use is too messy.

06 · Single Brain sponsor break
Mid-roll for singlebrainwithab.com / singlebrain.com — unified intelligence layer in Slack/Teams, ad-creative agents, data pulls from Meta/Google/SEO, team-visible execution.

07 · Diagram 02 — /goal overnight + 04 — AI Optimization Lab
Walks through two operating diagrams: 'Agents work the night shift with proof and approval gates' (Eric → Sleep → Morning approval; Tracks: Builder/Reviewer/Operator/Escalator; Proof: deliverable monitors / risk filter / executive packet), and the AI Optimization Lab compounding revenue loop (metrics → diagnose → hypotheses → eval scoring → approval → test → readback).

08 · Diagram 03 — Night Queue + 07 — Hermes Control Tower
Night Queue reads the business surface, dedupes work, ranks by impact, auto-launches safe jobs, packages risky ones for approval. Hermes Control Tower model: goals launch runners → runners create artifacts and evals → approvals touch outside world → metrics+memory improve the next goal. Mantra: 'move the ball forward'.

09 · Diagram 06 — Safe command surface + outro
Safe vs risky autonomy: internal docs / dry runs / evals & QA are safe to auto-run; email, CRM, social, CMS, ad-spend, deploys require Gate 4 human approval. Mantra: 'autonomy without letting the robot touch the money printer'. Outro pitches the next video on Hermes revenue growth.
Lines worth screenshotting.
- Most people are using /goal at its default single-mission level — the real revenue unlock is custom presets that let it work overnight, run in queues, and process batches.
- Defining the definition of done before running /goal is the difference between an agent that finishes a task and one that spins indefinitely on ambiguous completion criteria.
- A /goal overnight preset lets your AI agent execute one high-priority mission uninterrupted while you sleep — without any manual check-ins.
- Wiring a Hermes control tower into Slack creates an approval gate where risky actions pause for human sign-off while safe actions execute autonomously.
- The /goal batch command runs multiple independent missions in parallel — compressing what would take days of sequential work into a single overnight session.
- A /goal night-queue preset staggers multiple tasks across off-hours in sequence, so the agent is productive during the hours you're not watching.
- The more tools and MCPs you connect to your agent, the more interesting experiments you can run — the bottleneck is tool connectivity, not model capability.
- Running Hermes inside Slack rather than a terminal interface makes it accessible from your phone, enabling on-the-go oversight of autonomous overnight work.
Steal the format.
Don't ship a slash command. Ship a registry of branded presets that each carry their own safety rails and output format — every preset becomes both a feature and a pricing anchor.
- Pick one base verb (/flow, /goal, /run) and wrap it in 6-10 named presets, each with a clear definition-of-done — overnight, batch, continue, status, pause, resume.
- Frame the upgrade narrative the same way Eric did: 'You're using X wrong, here's how the pros stack it.' The promise sells the upgrade.
- Bake a two-lane safety model in from day one — green path runs without confirmation, red path produces an approval packet a human signs off in Slack/email.
- Tutorials that show a real Slack thread / real Hermes registry crush abstract slide decks. Eric switches between his actual Slack window and his actual preset definitions — that's the proof.
- Slot the sponsor / upsell at the 65-70% mark (~7:40 of 11:19) right before the highest-density payoff section, not at the end where viewers have already bounced.
- Close every framework with a one-line memorable mantra ('move the ball forward', 'don't let the robot touch the money printer'). Mantras are the only thing viewers can quote in the comments.
- Visual recipe: bookshelf talking head for emotional beats, full-screen Slack for proof, orange-on-black operating-diagram slides with PiP host in the corner for the framework block. Three modes, no slop.
Terms worth knowing.
- /goal command
- A slash command in Claude Code and similar AI coding environments that lets a user specify a high-level objective and have the agent autonomously plan and execute a multi-step path to achieve it.
- Hermes (agent)
- An open-source AI agent framework that can be configured to run autonomously on a schedule, receive instructions via messaging platforms like Slack, and orchestrate other AI agents or tools.
- Codex (agent)
- OpenAI's autonomous coding agent capable of independently writing, testing, and refining code toward a stated goal without step-by-step human guidance.
- OpenClaw
- A community-built AI coding agent environment that supports slash commands and autonomous task execution, compatible with multiple language model backends.
- Night queue
- A scheduled batch of AI agent tasks configured to run overnight while the operator is offline, maximizing compute time without requiring human oversight during execution.
- Approval gate
- A checkpoint in an autonomous AI workflow that requires a human to review and confirm before the agent proceeds with a high-risk or irreversible action.
- Slash command
- A shortcut typed as /<keyword> in a chat or terminal interface that triggers a specific preconfigured action or workflow, such as starting a task or switching an agent's mode.
Things they pointed at.
Lines you could clip.
“When you're running slash goal, you need to make sure that you're defining an outcome.”
“Move the ball forward — that's ultimately gonna build the most leverage for you.”
“Autonomy without letting the robot touch the money printer.”
“I could've been continued to work in those eight hours where you're sleeping.”
“It's no different than when you hire someone that's really amazing that's able to kinda figure things out on their own.”
Word for word.
The bait, then the rug-pull.
Eric Siu opens not by introducing /goal but by accusing you of running it at default. The promise is bigger than a tutorial — the title insists you are leaving money on the table, and the cold open immediately reframes /goal from a coder's convenience into a revenue lever you can stack overnight presets on top of.
Named ideas worth stealing.
/goal preset registry
- /goal overnight — one high-priority mission as an overnight operator loop with safe internal execution, verification, and a morning packet
- /goal status — how active goals are progressing
- /goal pause — freeze active goal without deleting
- /goal resume — restart a paused goal from its saved state
- /goal remove — drop current goal so the session stops chasing it
- /goal continue — pick back up after a clarifying question
- /goal batch open-threads — split open Slack threads into separate work lanes, track independently, produce a consolidated executive summary
- /goal night-queue — read business surface, dedupe, rank by impact, auto-launch safe jobs, package risky work for approval
- /goal business-operator — operator framing for business tasks
A registry of custom /goal subcommands layered on top of the base slash command — each one a named preset that bakes in safety rails, verification, and output format.
Safe vs Risky command surface (Gate 4)
- Safe to run: internal docs, briefs, research, plans, notes, summaries
- Safe to run: dry runs — preview commands, simulated sends, draft publishes
- Safe to run: evals and QA — tests, screenshots, scoring, linting, checklists
- Gate 4 approval required: email, CRM, social, CMS — anything that writes to customers or public channels
- Gate 4 approval required: ad spend and deploys — money movement and production changes
Two-lane autonomy model. One lane runs without permission; the other requires explicit human gate before it touches money, reputation, or production.
AI Optimization Lab loop
- Metric inputs (Instantly, Gong, ads, SEO)
- Diagnose bottleneck
- Hypotheses & variants
- Eval scoring
- Approval-then-test
- Metric readback into learning store
Closed-loop experimentation framework — metrics in, hypothesis out, test, score, approve, ship, read back into a learning store that improves the next cycle.
Hermes Control Tower
- Eric sets mission, constraints, approval posture, business priorities
- Hermes Control Tower routes work, gates risk, prepares review packets
- Runners: /goal runners, Codex, Cron, Subagents → produce artifacts and evals
- Approvals + metrics + learning store close the loop
Reframes the agent stack as a control tower, not a pile of prompts — single dispatch point, accountable runners, approval gates, observability.
How they asked for the click.
“Hope you enjoyed this one and you can check out this next video over here on how we are using Hermes to grow our revenue faster.”
Soft end-card CTA — no subscribe ask, no email capture. The real conversion ask is the embedded Single Brain mid-roll at 7:40, which is harder to skip than an outro.







































































