SOP Writer

The problem

Process knowledge often lives in messy chat logs, meeting transcripts, or scattered notes. When these are turned into SOPs manually, editors often invent missing steps or include vague instructions like "ensure it looks good" that provide no real accountability.

What it does

• Transforms a single raw data dump into a strictly numbered procedure with checkable completion criteria.
• Enforces a mandatory verification step with an observable pass/fail condition to ensure the process actually worked.
• Identifies and logs "gaps" such as contradictions in the source, unresolved roles, or missing exceptions.
• Strips out sensitive environment data like local file paths, vault IDs, and internal chat routing tokens.
• Prevents "hallucinated" safety steps by refusing to add rollbacks or notifications not present in the source.

Why this beats prompting it yourself

Generic prompts often hallucinate "best practices" or legalistic language that wasn't in your notes. This tool uses a rigid 8-step execution logic that prioritizes source fidelity over helpfulness, ensuring you only document what is actually known while highlighting exactly where your process is broken.

Use cases

• Converting a recorded screenshare transcript into a technical runbook.
• Formalizing "tribal knowledge" from a Slack thread into a version-controlled Markdown file.
• Auditing existing procedures by diffing them against fresh execution notes.
• Standardizing handoffs between roles by strictly mapping actors to imperative actions.

Known limitations

This skill handles exactly one procedure per run. It will not extract meeting minutes, write policy manuals, or generate weekly review templates.