process-doc

Capture how work actually gets done and formalize it as a complete standard operating procedure. Reach for it when a process lives only in someone's head, when a RACI is needed to clarify who owns what, when an SOP is required for a handoff or audit, or when the exceptions and edge cases of a workflow need documenting. The interaction is conversational, so you can describe the process, paste existing docs, or just give its name and let the skill ask the right questions, and messy starting material is expected and welcome.

The output is a structured SOP with a header carrying owner, last-updated date, and review cadence, followed by purpose, scope, a RACI matrix mapping each step to who is Responsible, Accountable, Consulted, and Informed, a process flow, detailed per-step breakdowns covering who, when, how, and output, exceptions and edge cases, metrics with targets and measurement methods, and related documents. The guidance highlights that the exceptions, the "usually we do X, but sometimes Y" cases, are the most valuable part to capture, and it encourages naming the people who do the work today even if roles later change.

Connectors extend the workflow. With a knowledge base connected the skill searches for existing process documentation so it updates rather than duplicates, and it can publish the finished SOP to a wiki. With a project tracker connected it links the process to related projects and workflows and can create tasks for process-improvement action items. The result is a durable, shareable reference that turns tribal knowledge into something a team can follow and audit.