notelisted

# /note — leave a note for another environment > **Only the user runs this.** It happens when they type `/note`, and at no > other time. If you are reading this file because *you* decided to — to see what > it does, or to carry out its steps yourself — then stop and do neither. > Following these instructions **is** running the skill, whichever route you took > to them, and a checkpoint the user did not ask for is one they will believe > happened when it did not. Say the skill exists and let them invoke it. When invoked, leave a note addressed to **another** aello environment. The argument is that environment's name (e.g. `/note frontend`). Invoking this skill is your authorization to write the note. This is **not** a handoff. `/handoff` is a note to *yourself* for your next session; `/note` is a message to a *different* environment — you touched something it owns, or hit a problem on its side, and it needs to act. You are the **`TechnicalDirector`** environment. The note goes to `<target>.NOTE.md` at the **target's** project root. That file is the target env's inbox — its SessionStart hook reads the note on boot, delivers it, and deletes the file. Steps: 1. Take the target env name from the argument; if none was given, ask which environment the note is for and stop. Use the blueprint's **canonical casing** (`RevoicedMainDev`, not `revoicedmaindev`) — the hook looks for exactly `<Name>.NOTE.md`, so wrong casing is a silent dead letter on a case-sensitive files