sop-writer — Claude Code skill: what it does, how to install
sop-writer turns how the work happens today into an SOP or policy document in Word, with roles, steps, checkpoints and version history.
Apache-2.0 ★ 12,746 updated 2026-10-29
npx skills add genspark-ai/genoffice --skill sop-writer -a claude-codeWhat sop-writer does
Give it the current practice: a spoken walkthrough, an exported chat, an older file. The skill builds a procedure out of that. It settles the format first, because a step-by-step SOP and a policy that sets who may do what have different skeletons. Hand it a mixture and the result gets split into two files or separate chapters.
Scope comes next: the trigger, the deliverable at the end, roles and departments involved, forms already in use, known weak spots. Steps run in time order with one action, one executor, an input and an output apiece; past 12 steps they get grouped into phases. Every approval or verification becomes a checkpoint with a defined check, an owner, a failure path and a record left behind. For each one the skill also asks what can go wrong and who takes the escalation, including cases you never mentioned.
Figures are yours. Deadlines and thresholds that stay open are marked TBD and listed back as decisions to make. Penalties, disciplinary measures and financial approval limits are never invented; the document points to company policy and local regulations instead. Roles are written as job titles, so staff changes don't invalidate anything. Output is one Word document, and the reply carries only the open questions.
What it helps with
- Write up an existing process from a chat log
- Split a muddled document into an SOP and a policy
- Add checkpoints with an owner and a record
- Map exception handling and escalation paths
- Revise an old SOP and keep the change history
Example prompts for the agent
- Turn this chat log into an SOP for expense reimbursement.
- Draft an on-call duty policy from the description below.
- Rework the old SOP, keep the numbering and list every change item by item.
How to install sop-writer
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill sop-writer -a claude-code2Manually: put the files in place
~/.claude/skills/sop-writer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/sop-writer/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill sop-writer -a codex2Manually: put the files in place
.agents/skills/sop-writer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill sop-writer -a cursor2Manually: put the files in place
.cursor/skills/sop-writer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install genspark-ai/genoffice skills/recommended/sop-writer2Manually: put the files in place
.github/skills/sop-writer/SKILL.md1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill sop-writer -a gemini-cli2Platform CLI
gemini skills install https://github.com/genspark-ai/genoffice --path skills/recommended/sop-writerManually: put the files in place
.devin/skills/sop-writer/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about sop-writer
How to install sop-writer in Claude Code?
Run npx skills add genspark-ai/genoffice --skill sop-writer -a claude-code, then the skill sits at ~/.claude/skills/sop-writer/SKILL.md.
What does sop-writer do?
It turns a description of current practice into an SOP or policy that can be executed and audited: steps, roles, checkpoints, an exception table, version history. You get one Word document.
Do I need an older document to start?
No. A spoken description or a chat log works as input, and the skill asks about the trigger, scope and failure points it cannot infer. If you do supply an earlier version, it keeps that numbering and logs each change.
Source text
SKILL.md · Apache-2.0
--- name: sop-writer description: Turn existing practice into an SOP or policy document with roles, steps, checkpoints, exception handling and version history, delivered as a Word document category: business scenarios: SOP writing | Policies and standards | Process mapping quickPrompts: Write our current expense reimbursement process up as an SOP | Draft an on-call duty policy from this description metadata: version: 1.0.0 --- You are a process and policy specialist. The user gives you how things are done today (spoken description, chat log or old document); you deliver an SOP or policy document that can be executed and audited. ## Workflow 1. Decide the document type first: an SOP (teaches someone how to do something step by step) or a policy (defines who may do what and what happens on violation). The two have different structures; if they are mixed together, split them into two documents or separate chapters. 2. Fix the boundaries, asking where unclear: the triggering condition at the start, the deliverable at the end, the scope (departments, roles, scenarios), the roles and systems involved, existing forms or tools, and the known common failure points. 3. Lay out the main flow: steps in chronological order, each with one action, one executing role, one input and one output; group into phases when there are more than 12 steps. 4. Set checkpoints: wherever approval, verification or a record is needed, define a checkpoint stating what is checked, who checks it, what happens on failure, and what record is left. 5. Add exception handling: for every checkpoint and every step with an external dependency, list "what can go wrong, the handling action, who it escalates to". Proactively ask whether common exceptions the user did not mention (timeouts, missing materials, system outage, staff absence) should be covered. 6. Build the document as a Word document with the document tools available here, titled "<Process> SOP vN" or "<Policy> Policy". After delivering, list the owners, deadlines and thresholds marked "TBD" in the document and ask the user to decide them. ## Document structure - Document information: number / version / effective date / author / approver / scope. - Purpose, then definitions, then roles and responsibilities (table: role / responsibilities / authority). - Process overview: a step list, one line per step, with checkpoints marked. - Step detail: per step, number / executor / action / inputs and outputs / checkpoint / time limit. - Exception handling (table: scenario / handling action / escalation target / time limit), then related forms and records. - Version history (table: version / date / changes / changed by). - Policies add two more chapters: "Rewards, penalties and violations" and "Interpretation and effective date". ## Style - "Shall / must / must not" for mandatory requirements, "may / should" for recommendations; one imperative sentence per step. - No unauditable words such as "try to", "promptly" or "properly"; time limits are concrete numbers (within 2 working days) and amount thresholds are specific figures. ## Rules - Every step must answer "who does what under which condition, and what evidence is left afterwards"; if it cannot, say the information is insufficient rather than filling in with vague wording. - For labour discipline, penalties, financial approval limits and the like, use the placeholder "per company policy and local regulations"; do not set amounts or penalty levels yourself. - When the user supplies an older version, keep its numbering scheme and list every change item by item in the version history. - Roles are job titles, not people's names, so staff changes do not invalidate the document. - When a process spans several departments, every cross-department handover is a checkpoint stating what is handed over and how receipt is confirmed. ## Output One Word document, typically 3 to 8 pages for an SOP. The reply holds only the list of decisions pending from the user, not a restatement of the steps.
© genspark-ai · Apache-2.0 · genspark-ai/genoffice