Workflow and sop builder

Skill nahiddotai/operator-powers/plugins/operator-powers/skills/workflow-and-sop-builder

AI skills to operate and grow. Twenty-eight practical powers for non-technical operators.

Install

npx -y skills add nahiddotai/operator-powers --skill workflow-and-sop-builder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.1 KB, 421 tokens by cl100k_base, as published. Nobody here has run it

Workflow And SOP Builder

Turn how work actually gets done into a usable process people and tools can follow.

Job contract

Owns: repeated business processes and operational playbooks.
Does not own: AI instruction files (agents-md-setup).
Finished deliverable: selected-mode workflow, SOP, exception handling, and test run.

Choose a mode

Human-run: people follow the SOP manually.
AI-assisted: AI prepares or checks defined steps while a person decides.
Automated: systems move information under explicit rules and controls.
Combined: assigns each step to the cheapest safe owner.

Workflow

Capture the trigger, desired result, frequency, inputs, owner, current steps, systems, exceptions, and failure cost.
Observe the real path. Do not document an imaginary ideal process as current reality.
Remove duplicate work before automating anything.
Assign each step to a person, AI, or system and explain why.
Define decision rules, approval gates, data handling, failure paths, and recovery.
Write the SOP so a new operator can run it without oral context.
Dry-run one normal case and one exception; revise where instructions fail.

Output

# Workflow And SOP

## Purpose And Success
[Trigger, outcome, measure]

## Roles And Systems
[Who or what owns each part]

## Procedure
| Step | Owner | Input | Action | Output | Check |

## Decision Rules
[If/then rules]

## Approvals And Safety
[External actions, sensitive data, spend, irreversible steps]

## Exceptions And Recovery
[What can fail and what to do]

## Run Checklist
[Compact repeat-use version]

## Test Record
[Normal and exception cases]

Guardrails

Never automate sending, publishing, spending, deletion, or account changes without an explicit approval gate.
Keep sensitive data out of prompts and logs unless required and authorised.
Prefer a reliable manual step to a brittle automation.