sop-creator

Generate runbooks, playbooks, and SOPs as publish-ready Markdown.

810|213|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/coleam00/second-brain-skills --skill sop-creator-coleam00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sop-creator
Source: https://github.com/coleam00/second-brain-skills/tree/main/.claude/skills/sop-creator
Command: npx skills add https://github.com/coleam00/second-brain-skills --skill sop-creator-coleam00

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creating consistent, thorough technical documentation is hard and error-prone. This Skill guides teams to rapidly produce runbooks, playbooks, and SOPs that are scannable, actionable, and maintainable.

Core Features & Use Cases

  • Structured Documentation: Generate runbooks, playbooks, ADRs, and SOPs with a universal structure and clearly defined "Definition of Done".
  • Templates & Guidance: Includes templates and examples for common documentation patterns, onboarding guides, and incident response docs.
  • Use Case Scenarios: Ideal for engineering incidents, onboarding new teammates, and standardizing repeatable procedures across teams.

Quick Start

Provide a user-friendly prompt that triggers the tool to create a runbook or SOP. For example: "Create a runbook for incident response in service X" or "Document this onboarding process for new engineers."

Frequently Asked Questions about sop-creator

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

FAQPage Schema
How do I create a runbook for incident response in a specific service?

You can generate a runbook for incident response by prompting the skill with your service details. It applies a universal structure including templates, clear responsibilities, and a Definition of Done to produce actionable, publish-ready Markdown documentation.

What is the best way to document onboarding processes for new engineers?

Documenting onboarding processes is best handled through structured SOPs. This skill helps you rapidly generate onboarding guides and playbooks that are scannable, actionable, and maintainable for standardizing new engineer procedures.

Does this tool work for standardizing repeatable engineering procedures?

Yes, it works for standardizing repeatable engineering procedures by enforcing a universal documentation structure. It formalizes technical procedures across teams, ensuring SOPs and runbooks include templates and a Definition of Done.

Can I generate ADRs and playbooks alongside standard SOPs?

Yes, you can generate ADRs and playbooks alongside standard SOPs. The skill supports a wide range of technical documentation patterns, producing structured playbooks, architectural decision records, and runbooks in Markdown.

Why do my operational docs lack clear responsibilities and scannability?

Operational docs often lack clear responsibilities and scannability without a universal structure. This skill solves this by applying templates, a Definition of Done, and specific responsibility assignments to produce publish-ready Markdown.