Sop Company Wiki

SOP & Company Wiki

What it is: Process documentation.

Overview

Works out the smallest useful SOP & Company Wiki setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on request, from one field list so they cannot drift apart.

Layer: Layer 1: Foundation. Fits: Growth stage. Table code: n/a.

When to Use This Skill

• sop template
• company wiki
• process documentation
• standard operating procedure tracker

Also use it when the user says "process documentation", or describes the same process happening in a spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
• "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
• "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
• "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: Which process hurts most to run?

Step 2 - Ask only what is missing

Skip anything the user already answered, in any earlier message. Ask the rest one at a time, and stop as soon as the remaining answers would not change the output.

• Processes - Which processes? / Written already? / How many?
• Ownership - Who owns each? / Who does the work? / Used by new hires?
• Detail - Step by step or checklist? / Tools involved? / Decision points?
• Current process - How is it done today? / In someone's head? / What breaks?
• Outcome - What do you need it for? / Onboarding, handover or audit?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless they ask, and it never carries a value the user did not give.

module: sop-company-wiki
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Processes": null
  "Ownership": null
  "Detail": null
  "Current process": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking

Step 4 - Recommend the smallest workflow

If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.

Recommended approach: Write one page per process with owner, trigger and steps. Publish them where the team already works.

Why this one: An SOP nobody opens is worse than none. Start from the process that causes the most rework, and keep it short enough to be read.

Workflow: Trigger → Steps → Owner → Checklist → Review after each run

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the requested artifacts. For machine-readable text, keep prose outside the data; for files, provide a usable link. Report material validation failures or limitations separately.

A selected Notion output is rendered by notion-manual-import, so route the Notion step there. When the user selects Notion, hand that step to @notion-manual-import: it holds the CSV, the property mapping, the import steps and the verification checklist, and it renders the Field Reference below instead of defining a table of its own. Do not restate the mapping here and do not improvise the import steps. Manual CSV and mapping outputs need no connection. For requested workspace changes, follow the shared contract: verify actual tool access and the target before writing. A user saying "connected" is not tool evidence. Never ask for a Notion password or token.

For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user requests a workbook. A CSV carries no types, so after it, name the columns that need a number, date or currency format applied.

SOP Title,Category,Department,Description,Last Reviewed,Next Review,Owner,Priority,SOP ID,Status,Tags,Version
Client Onboarding Runbook,Process,Delivery,"The written procedure for one recurring task, with the steps in the order they are done.",2026-01-15,2026-01-15,Sneha Iyer,Low,,Published,"process, finance",v1.0

CREATE TABLE sop_company_wiki (
  sop_title VARCHAR(255),
  category VARCHAR(100) NOT NULL,
  department VARCHAR(255),
  description TEXT,
  last_reviewed DATE NOT NULL,
  next_review DATE NOT NULL,
  owner VARCHAR(255),
  priority VARCHAR(100) NOT NULL,
  sop_id SERIAL PRIMARY KEY,
  status VARCHAR(100) NOT NULL,
  tags VARCHAR(255),
  version VARCHAR(255),
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_sop_company_wiki_status ON sop_company_wiki (status);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "SOP & Company Wiki",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "SOP Title": { "type": "string" },
      "Category": { "type": "string" },
      "Department": { "type": "string" },
      "Description": { "type": "string" },
      "Last Reviewed": { "type": "string", "format": "date" },
      "Next Review": { "type": "string", "format": "date" },
      "Owner": { "type": "string" },
      "Priority": { "type": "string" },
      "SOP ID": { "type": "integer" },
      "Status": { "type": "string" },
      "Tags": { "type": "string" },
      "Version": { "type": "string" }
  },
  "required": [
      "Category",
      "Last Reviewed",
      "Next Review",
      "Priority",
      "Status"
  ]
}

| CSV column | Notion property | Set after import |
|---|---|---|
| SOP Title | Title | Use as the database title |
| Category | Select (add options after import) | Convert to Select, add options: "Process", "How To", "Checklist", "Reference", "Template" |
| Department | Text | Leave as Text |
| Description | Text | Leave as Text |
| Last Reviewed | Date | Convert to Date |
| Next Review | Date | Convert to Date |
| Owner | Text | Leave as Text |
| Priority | Select (add options after import) | Convert to Select, add options: "Low", "Medium", "High", "Urgent" |
| SOP ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
| Status | Select (add options after import) | Convert to Select, add options: "Draft", "In Review", "Published", "Under Revision", "Retired" |
| Tags | Text | Leave as Text |
| Version | Text | Leave as Text |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date, and anything pointing at another table stays relation.

Field Reference