Skip to main content
All Use Cases
Operations

SOP & Knowledge Curator

Recurring processes get captured as living SOPs, and stale ones get flagged before they bite.

Best forAgencyB2BSaaSServicesStartup
Agents8 required
Duration5-10 minutes

SOPs rot silently: the documented steps drift from reality while the team keeps re-answering the same questions in Slack. This recipe scans your Google Docs and Notion wiki plus optional Slack threads for repeated how-to questions and processes that keep coming up, compares what it finds against the existing SOP set, and drafts new SOPs or updates stale ones — each with concrete steps, a named owner, and a last-verified date. Gap detection catches questions with no documented answer and turns them into draft SOP stubs instead of letting them stay tribal knowledge. Publishing is staged to your docs tool behind one approval gate; gap tasks can be routed to the PM tool. Nothing publishes or creates tasks unreviewed. Idempotent per SOP + window: reruns update each SOP in place, never duplicate.

How it runs

Multi-agent orchestration — here's the flow, step by step.

01

Resolve the window and scope, load prior-run state from memory, and dedupe so an SOP already curated in the window is updated, not duplicated.

workflow orchestrator
01

Pull the existing SOP set and wiki pages from Google Docs or Notion with their owners and last-verified dates.

docs manager
01

Cluster repeated how-to questions from docs and optional Slack threads; rank clusters by frequency and business impact.

knowledge synthesizer
02

Run gap detection: map question clusters against the SOP set, flag stale SOPs where observed practice contradicts the documented steps, and list undocumented gaps.

process documentation agent
03

Draft new SOPs and updates — concrete steps, named owner, last-verified date — and write draft stubs for the detected gaps.

sop writer
03

Stage the publish: new and updated SOPs to Google Docs or Notion with a change note per page.

docs manager
03

Stage gap-filling tasks — stubs that need a subject-matter owner — into the PM tool when connected.

task router
04

Assemble the approval package — drafts, updates, stubs, gap tasks — and on approval execute the publish and task staging with receipts.

distributor
04

Assemble the summary: SOPs updated, stubs created, stale flags with the contradicting evidence, and the in-hub footer when connections are missing.

report formatter

Required Agents

8
  • workflow-orchestrator
  • knowledge-synthesizer
  • process-documentation-agent
  • sop-writer
  • docs-manager
  • task-router
  • distributor
  • report-formatter

Connections

Required

asanagoogledocsgoogledriveslack

Optional

slacklineargoogledrive

What it does

  • Scans docs, wiki pages, and repeated how-to questions for SOP candidates
  • Drafts and updates SOPs with concrete steps, named owner, and last-verified date
  • Gap detection: questions with no documented answer become draft SOP stubs
  • Stale SOPs flagged when a newer process contradicts the documented one
  • Publish staged to Google Docs or Notion behind the approval gate
  • Optional Slack scan finds the questions the team keeps re-answering
  • One approval gate — nothing publishes or creates tasks unreviewed
  • Idempotent per SOP + window — reruns update in place, never duplicate

Example prompt

Sweep our wiki and last month of Slack questions, update the stale SOPs, and draft stubs for anything undocumented.

Ready to deploy SOP & Knowledge Curator?

Start free. One click, full agent orchestration.

Get Started Free →