Sop Builder

sop-builder

A Claude Code plugin that turns a rough description of an IT process into a polished, client-ready Standard Operating Procedure as a formatted .docx (and optionally .pdf).

Built for MSPs, IT consultants, and internal IT teams who need to ship consistent, non-technical-friendly SOPs fast — without wrestling with Word templates.

Install from the marketplace (recommended)

Inside Claude Code, run:

/plugin marketplace add Yxdav/sop-builder-skill
/plugin install sop-builder@sop-builder-marketplace

That's it. Node dependencies install automatically on first use via a SessionStart hook.

Requirements:

• Node.js 18+ on your PATH
• (Optional, for PDF export) Windows with Microsoft Word installed

What it does

Given any input — a pasted outline, a loose description, or nothing at all — the plugin:

1. Maps your input to a fixed five-section SOP structure (Title, Purpose, Procedure, Outputs, FAQs).
2. Asks only for what's missing, one gap at a time, in plain language.
3. Confirms the structure with a short summary before generating anything.
4. Generates a formatted .docx via a Node script that uses the docx library.
5. Optionally converts to PDF using Word's COM automation (Windows + Word required).
6. Opens the file automatically when done.

Design principles baked in

• One SOP, one process. Adjacent steps that belong to a different SOP go in Outputs as a → See [related SOP] reference, not as steps.
• Written for non-technical readers. Headlines speak to the reader ("You are logged in"), UI elements are described by what the reader sees ("three-line menu icon"), jargon avoided.
• Lean writing. No filler phrases, no restating headlines in bodies, no over-explaining obvious clicks.
• Per-step screenshots are optional — drop a file path and it's embedded, auto-scaled to page width.

Usage

Just ask naturally in Claude Code. Any of these will trigger it:

• "Create an SOP for resetting a user's MFA device"
• "Write a standard operating procedure for onboarding a new client mailbox"
• "Make an IT SOP"

Even a vague prompt works — the plugin will ask targeted questions to fill in gaps.

Example flow

You: Make me an SOP for resetting a user's Microsoft 365 password.

Claude: What's step 1, and what's the visible result when it's done?

You: Log into the admin portal and find the user.

Claude: Do you have a screenshot for this step? If so, drop the file path.

(...continues through remaining steps, outputs, FAQs...)

Claude: Ready to generate the .docx? (confirms structure)

You: Yes.

Claude: (generates file, asks .docx / PDF / both, opens it)

SOP structure

Every generated SOP has exactly these sections:

Section	Content
Title	The process name
Purpose	1–5 sentences: why this matters, what breaks if skipped
Procedure — Inputs	Prerequisites (access, tools, info)
Procedure — Steps	1–8 steps, each with a mini-result headline and body and/or screenshot
Outputs	Observable signals that the procedure is complete
FAQs	Common questions, edge cases

Manual install (without the marketplace)

If you'd rather manage the skill yourself:

# Windows
git clone https://github.com/Yxdav/sop-builder-skill.git "%USERPROFILE%\.claude\skills\sop-builder-manual"

# macOS / Linux
git clone https://github.com/Yxdav/sop-builder-skill.git ~/.claude/skills/sop-builder-manual

Then cd into plugins/sop-builder and run npm install. Note that paths in SKILL.md reference ${CLAUDE_PLUGIN_ROOT} — for a non-plugin install you'll need to adjust those to absolute paths.

Repository layout

sop-builder-skill/
├── .claude-plugin/
│   └── marketplace.json            # Marketplace manifest (lists plugins)
├── plugins/
│   └── sop-builder/
│       ├── .claude-plugin/
│       │   └── plugin.json         # Plugin manifest + SessionStart hook
│       ├── skills/
│       │   └── sop-builder/
│       │       └── SKILL.md        # Skill definition Claude reads
│       ├── scripts/
│       │   └── generate_sop.js     # Node generator (uses `docx` + `image-size`)
│       └── package.json
├── .gitignore
└── README.md

License

MIT