Quick Start
After installation, Hermes loads the plugin’s skills, commands, and hooks at startup. The default mode is fein.
Start a Session
Section titled “Start a Session”Launch Hermes in the project you want to work on.
Choose a Route
Section titled “Choose a Route”| Command | Route | Use it for |
|---|---|---|
| /fein | Full pipeline | Unfamiliar, multi-stage, or high-risk work |
| /sonar | Research only, then stop | Understanding a codebase or comparing approaches |
| /blitz | Direct read, research, and LLM work | Small work where direct execution is appropriate |
| /mode or /mode-clear | Show or clear the mode | Inspecting state or returning to neutral routing |
A mode command applies to all sessions that share the same HERMES_HOME; use /mode-clear to stop that persistence.
Try a Task
Section titled “Try a Task”For a full route, describe the outcome after activating fein:
/feinResearch the authentication patterns in this codebase, fix the empty-email failure, and review the fix.The orchestrator selects the needed specialists and passes evidence between stages. For a small explanation task, use blitz:
/blitzExplain what the add function in src/math.ts does.Understand the permission boundary
Section titled “Understand the permission boundary”maestria specialist names are routing roles, not permission identities. A trusted top-level session performs direct code changes; delegated children receive a fixed read, research, and read-only-inspection policy (no writes, code execution, shell, delegation, or OpenCode). Review and landing remain advisory because Hermes has no native review-state gate.
Long-Running Work
Section titled “Long-Running Work”Use Hermes’s /goal feature when the objective must survive session boundaries. maestria does not require a memory provider.