sop-creator

Convert user outlines into standardized SOP documents with YAML frontmatter and Markdown sections.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/ohnotnow/agentic-stuff --skill sop-creator-ohnotnow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sop-creator
Source: https://github.com/ohnotnow/agentic-stuff/tree/main/skills/sop-creator
Command: npx skills add https://github.com/ohnotnow/agentic-stuff --skill sop-creator-ohnotnow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes clear, repeatable Standard Operating Procedures from user outlines to standardize workflows.

Core Features & Use Cases

  • Structured SOP drafting: Converts outlines into well-organized SOP sections (Purpose, Prerequisites, Procedure, Verification, Troubleshooting, References).
  • Consistency enforcement: Applies a consistent style and structure across multiple SOPs.
  • Use Case: When teams need formal documentation for onboarding, incident response, or deployment checklists.

Quick Start

Draft a complete SOP from the user's outline using the provided template.

Frequently Asked Questions about sop-creator

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

FAQPage Schema
How do I convert an outline into a standard operating procedure document?

To convert an outline into a standard operating procedure, the Skill transforms your raw outline into a structured Markdown document with sections for Purpose, Prerequisites, Procedure, Verification, Troubleshooting, and References.

What sections should be included when writing an SOP for team onboarding or deployment?

An SOP for onboarding or deployment should include specific sections: Purpose, Prerequisites, Procedure, Verification, Troubleshooting, and References, along with YAML frontmatter for metadata.

Can I generate Markdown documentation with YAML frontmatter from a basic workflow outline?

Yes, you can generate Markdown documentation with YAML frontmatter directly from a basic workflow outline. The output includes YAML metadata for name and description, followed by the standardized Markdown body.

How do I standardize procedures for repeatable workflows across engineering and operations?

To standardize procedures for repeatable workflows, the Skill applies a consistent structure and style across multiple SOPs, ensuring engineering, QA, and operations teams follow identical documentation formats.

Does this SOP template work for incident response checklists and QA workflows?

Yes, this SOP template works for incident response checklists and QA workflows. It applies standardized formatting across any context requiring clear, repeatable procedures and formal documentation.