SOP Documentation

Capture how the process actually runs before writing it up.

Record:

• The process name and its purpose — what outcome it produces
• Who runs it and when it is triggered
• The steps in order, as they really happen — including the small
  ones people do from memory
• Tools, systems, or access needed at each step
• Common pitfalls or edge cases and how they are handled

Probe for the tribal knowledge — the "oh, and you also have to" steps
that never make it into documentation. If a step is unclear, ask the
operator rather than guessing.

Save the captured process as a task note with task_notes_add. The next
step — Draft SOP — reads this note.

Read the task notes with task_notes_list — the note from the Capture
Process step contains the steps and the tribal knowledge. Work from it.

Write the SOP. What good looks like:

• A title, purpose, and the trigger that starts the process
• Prerequisites — access, tools, inputs needed before starting
• Numbered steps in order, each one concrete action a person can do
  without guessing
• Edge cases and what to do when they occur
• The definition of done — how to know the process completed correctly

Write for someone doing this for the first time. No assumed knowledge.

Save the full SOP draft as a task note with task_notes_add. If it
exceeds 10,000 characters, split across notes or store where the
operator keeps documents and record the location. The Walkthrough step
reads this note.

Read the task notes with task_notes_list — the Draft SOP note holds
the procedure and the Capture Process note holds the original steps to
check against. Work from them.

Walk the SOP step by step as if running the process for the first time:

• Every step is actionable with no missing prerequisite
• The order is correct and nothing is skipped
• Edge cases are covered
• A new person could follow it without asking for help

Note any gap and fix the draft before sign-off.

Ask the operator to approve the SOP for publishing. This is a checkpoint
— once published the team relies on it, so the AI cannot advance until
you approve. If you reject, the workflow returns to Draft SOP.

Read the task notes with task_notes_list — the Walkthrough note holds
the approved procedure. Work from it.

Publish the SOP where the team keeps its documentation — the wiki, doc,
or shared space they actually use. Save the published SOP as a task note
with task_notes_add so the record stays on file, then close out the task.