← Operator PowersCONTENT HISTORY

Update to Operator Powers

Snapshot Sep 30, 2026 · 22:54 UTC · version 1.0.1

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "workflow-and-sop-builder",
  "description": "Turn a repeated business task into a human-run, AI-assisted, automated, or combined workflow with an SOP, roles, steps, decisions, exceptions, controls, and tests.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 218
    }
  ],
  "skill_md_contents": "---\nname: workflow-and-sop-builder\ndescription: Turn a repeated business task into a human-run, AI-assisted, automated, or combined workflow with an SOP, roles, steps, decisions, exceptions, controls, and tests.\n---\n\n# Workflow And SOP Builder\n\nTurn how work actually gets done into a usable process people and tools can follow.\n\n## Job contract\n\n- Owns: repeated business processes and operational playbooks.\n- Does not own: AI instruction files (`agents-md-setup`).\n- Finished deliverable: selected-mode workflow, SOP, exception handling, and test run.\n\n## Choose a mode\n\n- `Human-run`: people follow the SOP manually.\n- `AI-assisted`: AI prepares or checks defined steps while a person decides.\n- `Automated`: systems move information under explicit rules and controls.\n- `Combined`: assigns each step to the cheapest safe owner.\n\n## Workflow\n\n1. Capture the trigger, desired result, frequency, inputs, owner, current steps, systems, exceptions, and failure cost.\n2. Observe the real path. Do not document an imaginary ideal process as current reality.\n3. Remove duplicate work before automating anything.\n4. Assign each step to a person, AI, or system and explain why.\n5. Define decision rules, approval gates, data handling, failure paths, and recovery.\n6. Write the SOP so a new operator can run it without oral context.\n7. Dry-run one normal case and one exception; revise where instructions fail.\n\n## Output\n\n```markdown\n# Workflow And SOP\n\n## Purpose And Success\n[Trigger, outcome, measure]\n\n## Roles And Systems\n[Who or what owns each part]\n\n## Procedure\n| Step | Owner | Input | Action | Output | Check |\n\n## Decision Rules\n[If/then rules]\n\n## Approvals And Safety\n[External actions, sensitive data, spend, irreversible steps]\n\n## Exceptions And Recovery\n[What can fail and what to do]\n\n## Run Checklist\n[Compact repeat-use version]\n\n## Test Record\n[Normal and exception cases]\n```\n\n## Guardrails\n\n- Never automate sending, publishing, spending, deletion, or account changes without an explicit approval gate.\n- Keep sensitive data out of prompts and logs unless required and authorised.\n- Prefer a reliable manual step to a brittle automation.\n"
}

SHA-256: 9bf7175f2d785fa099de37d5497c04d31bc76e8b86e5112a6a96b54d30d0d4fc