sop-writer

Convert undocumented business processes into structured Standard Operating Procedures with checkpoints and metrics.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/fritzgeraldz/Vibe-Managing --skill sop-writer-fritzgeraldz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sop-writer
Source: https://github.com/fritzgeraldz/Vibe-Managing/tree/main/skills/operations/sop-writer
Command: npx skills add https://github.com/fritzgeraldz/Vibe-Managing --skill sop-writer-fritzgeraldz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Critical business processes often live only in one person's head, making them impossible to delegate, scale, or measure. This Skill converts that tribal knowledge into a documented Standard Operating Procedure with explicit steps, quality standards, recovery steps, and metrics. ## Core Features & Use Cases - Structured SOP Generation: Produces a complete SOP document with numbered steps, quality checkpoints, fail-safes, escalation paths, and target metrics. - Tribal Knowledge Capture: Interviews for tacit details like standards, exceptions, and recovery steps, inserting [TO CONFIRM] placeholders instead of fabricating unknowns. - Use Case: A marketing agency founder wants to hand monthly client reporting to a new account coordinator. The Skill turns a walkthrough into a 6-step SOP with a mandatory review checkpoint, fail-safes against wrong date ranges, and on-time delivery metrics. ## Quick Start Document our monthly client reporting process as an SOP so I can delegate it to a new account coordinator.

Frequently Asked Questions about sop-writer

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

FAQPage Schema
How do I document a business process as an SOP?▼

Provide a process map or a start-to-finish walkthrough of the process, including its purpose, required output, and quality standards. The Skill structures this into numbered steps with checkpoints, recovery procedures, and metrics written to the owning role.

What should a standard operating procedure include?▼

A complete SOP includes purpose, scope, trigger, definition of done, prerequisites, numbered steps with standards, quality checkpoints, exceptions and recovery steps, fail-safes, escalation paths, metrics with targets, training notes, and a review cadence.

When should I not write an SOP for a process?▼

Do not codify a process that is not yet understood or stable; run process mapping or optimization first. Also avoid SOPs when the real goal is automation or a customer-facing contract rather than internal operating documentation.

How do I handle unknown quality standards in an SOP?▼

Insert a [TO CONFIRM] placeholder and list it as an open question rather than guessing. Standards, thresholds, scripts, and compliance requirements are never fabricated; the founder or operator must confirm them before go-live.

Can an SOP help delegate an owner-dependent process?▼

Yes. The SOP is written to a role rather than a person, with explicit ownership, success metrics, and an escalation path so responsibility genuinely transfers. Assigning it to a specific employee still requires founder approval.