Process Memo as Transferable Workflow names the practice of writing a working AI workflow into a 📝memo that anyone can hand to their own 📝Claude, so the workflow travels between people instead of living as one user's tacit prompting knowledge.
The pattern starts after a workflow already works for one person. That person asks Claude to turn it into a process memo, and Claude summarizes the workflow, captures its context, structures its logic and writes reusable operating instructions. What makes it a process memo is that its intended reader is another person's AI.
The shift is in who has to carry prompting skill. The memo encapsulates the process logic, so the recipient does not need deep 📝prompt engineering expertise to run it: they paste it into their own Claude and it does the rest.
📝Building a Memo Drafting Loop in MythOS is a public example of the form: a guide whose setup is a single prompt pasted into a Claude session, which then builds the reader's own version of the loop. In 📝MythOS, connected to Claude through MCP, process memos sit alongside the templates and drafting loops the library uses to operationalize workflows. The idea complements 📝Update My Brain, which removes manual context management for the person doing the work.
After building a workflow for myself, I asked Claude to "build me a process memo that I can hand off to anyone else and have them hand it to their Claude." From there: "Now all you have to do is copy this and paste it into your Claude, and it does the rest."