Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, building a RACI to clarify who owns what, writing an SOP for a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done.

/process doc If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Document a business process as a complete standard operating procedure (SOP). Usage How It Works Walk me through the process — describe it, paste existing docs, or just tell me the name and I'll ask the right questions. I'll produce a complete SOP. Output If Connectors Available If ~~knowledge base is connected: Search for existing process documentation to update rather than duplicate Publish the completed SOP to your wiki If ~~project tracker is connected: Link the process to related projects and workflows Create tasks for process improvement action items Tips 1. Start messy — You don't need a perfect description. Tell me how it works today and I'll structure it. 2. Include the exceptions — "Usually we do X, but sometimes Y" is the most valuable part to document. 3. Name the people — Even if roles change, knowing who does what today helps get the process right.

process-doc