skills.rest
poorvith-mp
poorvith-mpCOMMUNITY
Explore all skills by this author →
Website𝕏@poorvith_mpGitHub

sop-writing

Write Standard Operating Procedures with numbered steps, acceptance gates, and rollback runbooks.

2|Updated Jul 15, 2026
Search Tags:#documentation#checklist#operations#runbook#escalation#sop#standard operating procedure
One-click install
npx skills add https://github.com/poorvith-mp/skills-writing --skill sop-writing-poorvith-mp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sop-writing
Source: https://github.com/poorvith-mp/skills-writing/tree/main/skills/sop-writing
Command: npx skills add https://github.com/poorvith-mp/skills-writing --skill sop-writing-poorvith-mp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often rely on tribal knowledge or vague documentation, causing errors when operators execute critical procedures under pressure. This Skill turns unwritten or messy manual tasks into deterministic SOPs that any qualified operator can follow without ambiguity. ## Core Features & Use Cases - 4-Step SOP Architecture: Structures documents with scope and prerequisites, numbered imperative steps, observable verification gates, and rollback plus escalation paths. - Executable Templates: Produces a production-ready SOP template with metadata headers, copy-pasteable commands, and acceptance criteria for every critical step. - Use Case: Convert an informal database backup routine into a documented runbook with exact CLI commands, expected outputs, failure rollback steps, and an on-call escalation matrix. ## Quick Start Write a Standard Operating Procedure for our weekly database backup verification including prerequisites, numbered steps, and rollback instructions.

Frequently Asked Questions about sop-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Standard Operating Procedure that anyone can follow?▼

Structure the SOP with a metadata header, strict scope boundaries, and prerequisites first. Then write numbered steps starting with imperative verbs, include exact copy-pasteable commands, and specify the expected observable output for every critical step.

What should an operational runbook include?▼

A runbook should include purpose and scope, access prerequisites, a numbered step sequence with acceptance gates, decision branches for failures, a rollback plan, and an escalation contact matrix with named roles and paging channels.

How do I handle failures and rollbacks in an SOP?▼

Document exact rollback commands that restore the system to a safe baseline state if the procedure fails mid-stream. Also define an escalation SLA specifying who to page, on which channel, and after what time threshold.

When should I use an SOP instead of technical documentation?▼

Use an SOP for repeatable operational procedures executed by humans or agents, such as deployments or backups. Use technical documentation for API references, user guides, and architecture explanations aimed at developers.

What are common mistakes when writing runbooks?▼

Common anti-patterns include ambiguous instructions like 'configure the network properly', missing rollback procedures, and untested emergency runbooks that were never dry-run in a staging environment.

Related Skills

Explore More Content & Communication Skills→
RoxabiRoxabi
9

interview

Conduct structured interviews to generate MDX documents with YAML frontmatter.

Official
Advanced
ilove323ilove323

runbook

Create step-by-step operational runbooks with verification and rollback steps.

Community
Intermediate
afoxnyc3afoxnyc3

runbook-create

Create operational IT runbooks with prerequisites, steps, verification, and rollback.

Community
Advanced
nimadorostkarnimadorostkar
25

technical-documentation

Standardizes technical docs into tutorials, how-tos, references, and explanations.

Community
Intermediate