Operations · documentation

SOP Builder

Documents a procedure from the steps you listed, with owners left blank where you named none.

Purpose

Write a standard operating procedure for one process.

Deliverable: Purpose, steps, roles, exceptions, and a checklist.

Inputs

Required

  • Process name
  • Steps

Optional

  • Owner
  • Exceptions
  • Definition of done

Method

  1. 01Number the steps you wrote.
  2. 02Attach an owner only if you named one for that step or for the whole process.
  3. 03Record exceptions only where you wrote unless, except, or if.
  4. 04The checklist is those steps, not a new control set.

Evidence

A run uses the text you submit. It does not browse, and it does not open links you paste.

  • Do not: Add compliance controls you did not mention.
  • Do not: Imply the SOP is already in force.

Quality checks

  • Step text matches what you submitted.

SKILL.md

Install at ~/.grok/skills/sop-builder/SKILL.md and start a new session.

Download
---
name: sop-builder
description: Documents a procedure from the steps you listed, with owners left blank where you named none.
---

# SOP Builder

## Purpose
Write a standard operating procedure for one process.

Outcome: Purpose, steps, roles, exceptions, and a checklist.

## When to activate
Use this when the user needs to write a standard operating procedure for one process.

## When not to activate
- Add compliance controls you did not mention.
- Imply the SOP is already in force.

## Required inputs
- Process name
- Steps

## Optional inputs
- Owner
- Exceptions
- Definition of done

## Workflow
1. Number the steps you wrote.
2. Attach an owner only if you named one for that step or for the whole process.
3. Record exceptions only where you wrote unless, except, or if.
4. The checklist is those steps, not a new control set.

## Evidence
- Verified facts are only pages retrieved in the run, or figures and sentences the user typed.
- Label user-provided claims, assumptions, and unknowns separately.
- Do not invent sources, statistics, quotations, contacts, credentials, or tool use.
- Do not say a page, file, or account was opened if it was not.
- Do not present the output as regulated professional advice.

## Output
Purpose, steps, roles, exceptions, and a checklist.

## Quality checks
- [ ] Step text matches what you submitted.

## Failure handling
If a required input is missing, return the sections that can be completed and name the gap. Do not fill it.

## Safety
Refuse deception, impersonation, and requests for wrongdoing. Do not collect credentials.

## Install
Save as ~/.grok/skills/sop-builder/SKILL.md and start a new session.

Related

Research skills show only pages retrieved on that run. Every other skill uses what you type and labels the gaps. Finance outputs are planning support, not regulated advice. Nothing here is an identity, credit, legal, medical, or compliance decision.