The naumu skill
The daily read+write loop - your agent retrieves the team's prior decisions before a task and files a short work-log entry with a commit trailer after.
Not installed yet? One command adds both skills to your repo: npx skills add naumu-ai/skills. Full instructions under Agent skills → Install.
The naumu skill is the behavior behind the .naumu file in your repo. Once installed, it activates in any repo that has a .naumu file at its root - you do not invoke it day to day, it changes how your agent works on every substantive task.
The read: retrieval before the task
Before starting a build, fix, or refactor, the agent runs one fast scoped lookup against your space - a naumu_search built from the task's feature names, files, and symbols. If a result points at a conversation worth the context, it reads that one thread. Anything relevant (a prior decision, a gotcha, a linked ticket) gets folded into how it approaches the work, and mentioned to you in one line.
This is a reflex, not a research project: it has a hard budget of a few seconds, and if the space is slow or errors, the agent drops the lookup and starts the work. It never stalls your task on retrieval.
The write: a work-log entry on completion
When a unit of work is done, the agent posts a short bulleted work-log entry into your space, filed under the topic your .naumu file names in its tracking block. If the tracking block is absent, the team has opted out and no work-log is written.
Each commit for a tracked task also carries the thread as a trailer:
fix(scope): short description
Body text.
Naumu-Thread: https://naumu.ai/spaces/<slug>/chat/<threadId>That trailer is the trail a future teammate follows: git blame leads to the commit, the commit links the thread, and the thread holds the original reasoning. Reviewers see the link in the PR even if their own agent never connected. Set tracking.commitTrailer: false in .naumu to turn the trailer off.
Cold clones
In a fresh clone that has a .naumu file but no Naumu MCP server connected yet, the skill offers once to connect - and never sets anything up without a yes. If you decline, it stays quiet for that clone.
Triggering it explicitly
The loop runs on its own, but you can also invoke it directly with /naumu - for example to run the retrieval reflex on demand, or to re-trigger the connect offer you declined earlier.