notes-keeper

# notes-keeper You have access to a markdown notes vault rooted on the gateway host. The vault holds three conventional sections: - `daily/YYYY-MM-DD.md` — daily logs / standup-style notes - `projects/<basename>/<file>.md` — per-project documentation (one folder per repo). You write here: README.md, spec.md, architecture.md, decisions/0001-xxx.md, retros/2026-q2.md, etc. The user reads these in their inspector but rarely edits them by hand. - `personal/<basename>.md` — the user's PERSONAL scratchpad for this project. **Do not write here** — this lane is owned by the user. If the user explicitly tells you "add this to my notes", write to projects/<basename>/<something>.md instead and tell them where it landed; let them copy across if they want. - anywhere else under the vault — free-form library content All operations go through the `opendray notes` CLI subcommand. The gateway process does not need to be running; the CLI talks to the vault filesystem directly. ## When to use this skill - The user asks to "remember", "save", "note", "log", "track" something - They reference a project's doc / journal / decisions - They ask "what did I work on yesterday / last week" - They want a persistent TODO list scoped to a project - They mention `[[wiki-links]]`, tags (`#area-X`), or daily notes Do **not** use this skill for ephemeral within-session scratch state — that belongs in your normal context. Save things that are valuable across sessions. ## Commands ``` opend...