process-documentation

Document a repeatable process, SOP, run sequence, ownership model, or handoff with inputs, steps, decisions, exceptions, and verification. Use for SOP, process document, workflow documentation, operat

SKILL.md

GitHub

Process Documentation

Document what people actually do, not an idealized version.

  1. Define trigger, outcome, scope, owner, users, inputs, tools, and constraints.
  2. Capture normal path, decisions, exception paths, escalation, handoffs, and completion evidence.
  3. Use numbered executable steps and name the decision owner at every ambiguity point.
  4. Add a short review cadence and change owner so the document does not silently stale.

Keep overhead proportional. Do not write a policy for a one-off task, and do not invent controls or approvals.