Keep project notes current

What this does. After you’ve done a substantive piece of work — a meeting, a decision, a draft, an analysis — run /update. Claude scans the related project notes, instruction files, and process docs in your vault, and proposes specific updates to each so they reflect what just happened. You approve or decline per file. No silent edits.

Why this matters

The slow rot of project notes is one of the most expensive things in a knowledge-work setup. Status notes go silently stale; the “what’s happening on project X” lives in your head and dies when you’re not in the room. People (including future-you) ask, and you don’t have a clean answer — so you spend an hour reconstructing it from your daily notes and your memory.

/update is the fix. After a substantive session, your notes catch up automatically.

When to use it

• After meetings — typically paired with the transcribe flow. Transcript lands, project files get swept.
• After a substantive piece of writing or analysis — the project’s state has moved, so the project file should too.
• After editing a skill, process doc, or instruction file — /update can sweep related docs (cross-references, examples, summaries) so they don’t drift.
• When /document surfaces decisions that should land in project files specifically, not just the session log.

How to use it

Just type:

/update

Claude lists which documents it thinks should be updated, with a short note about what it proposes to change in each. Review the list:

• Approve a proposed change → Claude applies it.
• Decline anything that looks off → Claude skips it.
• Edit a proposed change first → tell Claude what to change before approving.

You stay in control of every edit.

What this prevents

The drift between what’s true about a project today and what’s written in the project notes. Without /update, that gap grows steadily and you only notice it when someone asks an inconvenient question. With /update, the gap closes at the end of each working session.

What’s next

You’ve got the core daily-and-after-meetings rhythm now: install → connect → teach Claude about you → transcribe → daily-rhythm → keep notes current. That’s enough to actually use this system productively.

Ready for a real project? Turn reports into a paper draft (a worked example) walks through using everything from Lessons 1–7 to take an existing body of work — reports, data, drafts — and shape it into a paper. The example is concrete; the workflow generalises to any project where you’ve got materials and want a structured output.

From there, the full course at github.com/marinemegafauna/mmf-claude-code covers more specialised workflows — deep research, citation verification, adversarial review — and the deeper customisation layers. Ping Simon when there’s a specific area you want made into a page on this site and he’ll prioritise it next.