Sop Build

Builds standard operating procedures from a guided interview, screen-recording transcript, or existing draft. Use when the user says "write an SOP", "document this process", "make an SOP for X", "I keep redoing this", "delegate this to my VA", "onboarding doc for new hire", "write up how I do this", or asks to audit / clean up an existing SOP. Treats the user as the expert being interviewed and acts as a COO who pushes back on weak steps before they get written down.

62 stars 12 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add charlesdove977/procedure-ops --skill sop-build
Manual install
git clone --depth 1 https://github.com/charlesdove977/procedure-ops.git /tmp/procedure-ops
mkdir -p ~/.claude/skills
cp -r /tmp/procedure-ops/skill ~/.claude/skills/sop-build

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

<activation>
## What
Generates ironclad SOPs from a guided interview, a screen-recording transcript, or an existing draft. Pushes back on vague steps, suggests Loom videos when text falls short, flags automation candidates, and routes finished SOPs into the right business + department folder under `SOPs/`.

## When to Use
- Delegating a recurring task to a VA, contractor, or new hire
- Documenting a process you keep redoing from scratch
- Identifying which steps in a process can be automated (then feeding into n8n / Zapier / Make / managed agent)
- Onboarding documentation for a new role or seat
- Auditing or cleaning up an existing SOP

## Not For
- Building the automation itself — that is a separate job after the SOP flags it. Hand off to `/seed:tasks:ideate` to incubate, then `/paul:plan` to build.
- Project plans with milestones — use the `paul:*` workflow skills
- Ideating brand new processes that do not yet exist — use `seed:*` for incubation
- Client-facing deliverables, proposals, sales copy — use `ccpdf` or `copywriting`
</activation>

<persona>
## Role
COO-in-a-box who challenges the process while documenting it. Treats the user as the expert being interviewed, but pushes back on inefficient or under-specified steps before they get written down. The job is not just to capture what the user does — it is to make sure what gets captured is *worth* doing.

## Style
- Structured and opinionated. Challenges weak inputs.
Read the full skill on GitHub

Details

Skill name
sop-build
Path
skill/SKILL.md
License
MIT
Repo updated
23 October 2026

FAQ

What does the Sop Build skill do?

Builds standard operating procedures from a guided interview, screen-recording transcript, or existing draft. Use when the user says "write an SOP", "document this process", "make an SOP for X", "I keep redoing this", "delegate this to my VA", "onboarding doc for new hire", "write up how I do this", or asks to audit / clean up an existing SOP. Treats the user as the expert being interviewed and acts as a COO who pushes back on weak steps before they get written down.

How do I install the Sop Build skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add charlesdove977/procedure-ops --skill sop-build. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Sop Build popular?

It lives in charlesdove977/procedure-ops, which has 62 GitHub stars and 12 forks.

Related skills

Staff Level Elixir

228

pproenca/dot-skills

Use this skill when writing, reviewing, or refactoring Elixir, OTP, Ecto, or Phoenix/LiveView code. It corrects the staff-level judgment calls a capable model gets wrong by default — reaching for a GenServer as the universal tool, rescuing instead of letting processes crash, N+1 Ecto access, non-atomic writes, unbounded/linked Task fan-out, atom exhaustion from user input, eager Enum where Stream fits, and calling Repo from the web layer. Applies whenever the work touches process design, error handling, concurrency, data access, or LiveView, even if the user doesn't name them.

Writing & Content19

Sleep Story

191

jwynia/agent-skills

Write stories designed to help listeners fall asleep. Use for bedtime podcasts, meditation content, calming narratives, or any content where the goal is gentle cognitive engagement that fades naturally into rest.

Writing & Content24

Story Analysis

191

jwynia/agent-skills

Systematically evaluate completed short stories or novel chapters to identify strengths, weaknesses, and improvement opportunities. Use after drafting to assess whether the piece achieves its narrative goals.

Writing & Content24

Skyscraper Technique

150

guia-matthieu/clawfu-skills

Build high-quality backlinks systematically using Brian Dean's proven 3-step content marketing framework—find link-worthy content, make something 10x better, and reach out to the right people. Use when: **Build backlinks** to improve search rankings; **Create content** with pre-validated demand for links; **Outrank competitors** on specific topics; **Develop link-building campaigns** that actually work; **Promote new content** to relevant websites

Writing & ContentIn 1 list32

Story Coach

191

jwynia/agent-skills

Act as an assistive writing coach who guides but never writes for the user. Use when helping someone develop their own writing through questions, diagnosis, and frameworks. Critical constraint - never generate story prose, dialogue, or narrative content. Instead ask questions, identify issues, suggest approaches, and let the writer write.

Writing & Content24

Shared World

191

jwynia/agent-skills

Maintain a wiki-style world bible for collaborative fiction. Use for long-running story worlds, shared universes, membership sites, or any fiction requiring persistent canonical reference.

Writing & Content24

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.