sop-builder

Convert rough process notes and operator knowledge into structured standard operating procedures.

2|1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/dkyazzentwatwa/skill_starter_pack --skill sop-builder-dkyazzentwatwa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sop-builder
Source: https://github.com/dkyazzentwatwa/skill_starter_pack/tree/main/sop-builder
Command: npx skills add https://github.com/dkyazzentwatwa/skill_starter_pack --skill sop-builder-dkyazzentwatwa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Teams often keep critical workflows as scattered notes, chat messages, or tribal knowledge that new members cannot follow. This Skill normalizes that messy material into explicit, runnable SOPs with clear steps, quality checks, and escalation paths. ## Core Features & Use Cases - Process Normalization: Converts rough notes, Loom summaries, and chat instructions into atomic operating facts covering triggers, inputs, steps, outputs, and exceptions. - Multiple Output Formats: Produces Standard, Lightweight, and Formal SOP variants plus a live execution checklist companion. - Assumption Surfacing: Labels details as Confirmed, Assumed, or Unknown/Open so hidden gaps stay visible instead of becoming silent errors. - Use Case: A team lead pastes a messy Slack thread describing the weekly client-reporting process and receives a complete SOP with procedure, QA checks, failure modes, and an escalation path that a new hire can follow. ## Quick Start Use the sop-builder skill to turn these process notes into a standard operating procedure with a checklist companion.

Frequently Asked Questions about sop-builder

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

FAQPage Schema
How do I turn messy process notes into an SOP?

Provide the raw material such as notes, chat threads, or call summaries, and the skill normalizes it into atomic operating facts like triggers, steps, and outputs. It then drafts a structured SOP with procedure, quality checks, and escalation path.

What should a standard operating procedure include?

A complete SOP includes title, purpose, scope, audience, owner, trigger, required inputs and tools, step-by-step procedure, outputs, quality checks, failure modes, exceptions, escalation path, and revision notes. The skill uses this structure by default.

Can I get a short checklist instead of a full SOP document?

Yes, the skill produces a lightweight SOP and a checklist companion with short action lines for live execution. You can request only one variant instead of the default full set of outputs.

What happens when process details are missing or conflicting?

Missing details are labeled as Assumed or Unknown/Open rather than invented, and conflicting source material is preserved in a visible resolution note. The SOP is still produced with the gaps explicitly flagged.

When should an existing SOP be updated?

Update an SOP when tools, ownership, triggers, QA checks, output formats, or escalation routing change, or when operators repeatedly improvise around missing instructions. The update guidance reference lists which sections drift fastest and how to record revision notes.