If you have to explain the same job again every time you open Hermes, put the job in a small folder first. You do not need a huge system. Start with one repeating review that is safe to prepare as a draft and still needs your approval before anything happens. The goal is simple: when you open a new chat, the work, the boundary, and the latest decision are already findable. ## Pick a review that is safe to draft Choose something you already do more than once. Good first examples include: - reviewing a few support requests and preparing reply drafts - checking a weekly project list and flagging what needs attention - gathering a small set of updates into a decision brief Do not begin with payments, account changes, sending messages, deleting files, or anything where a bad first draft could hurt someone. Your first workflow should prepare information, not take action. ## Make one folder with three files Create a folder named for the job. Inside it, make these three plain-text files: ```text weekly-project-review/ ├── PURPOSE.md ├── CONTEXT.md └── decisions.md ``` ### 1. `PURPOSE.md` Write what the review is for, what comes in, and what should come out. ```markdown # Weekly Project Review ## Purpose Prepare a short draft of this week's priorities for my review. ## Inputs - Current project notes - Last review's decisions ## Output - A draft priority list with open questions ## Human check I review the draft before any task, message, calendar, or file change happens. ``` ### 2. `CONTEXT.md` Write the facts Hermes needs every time. Keep it short and current. ```markdown # Context - We work on three active client projects. - Jordan makes final priority decisions. - Do not contact clients or change project records. - Flag missing information instead of guessing. ``` ### 3. `decisions.md` Add the latest choices and unresolved questions. Date each entry.