sop-creator
by ognjengtsop-creator turns rough process notes into clear Standard Operating Procedures for repeatable business work. Use it for process documentation, workflow guides, onboarding, and step-by-step instructions when you need practical output, not polished corporate prose. It also works well as a sop-creator for Technical Writing and for teams that need consistent handoff-ready docs.
This skill scores 74/100, which means it is list-worthy for directory users but not especially polished. It has a clear trigger, a defined execution mode, and a substantial workflow for turning process notes into SOPs, so an agent can use it with less guesswork than a generic prompt. Users should still expect some adoption friction because the repository provides only the SKILL.md workflow and no supporting references, scripts, or install command.
- Clear triggerability: the frontmatter says to use it for SOPs, process documentation, operational guides, and repeatable business workflows.
- Operational workflow is concrete: it specifies empty-vs-populated $ARGUMENTS behavior, checks for FOUNDER_CONTEXT.md, and outlines analysis/clarification steps.
- Strong directory value for process documentation tasks: it aims to transform unstructured descriptions into a 5th-grade-reading-level SOP.
- No support files or install command are provided, so users only get the SKILL.md behavior with limited onboarding help.
- The visible excerpt is truncated mid-flow, so some execution details and edge-case handling are not verifiable from the repository evidence provided.
Overview of sop-creator skill
The sop-creator skill turns a rough process description into a clear Standard Operating Procedure, written for reuse and easy handoff. It is best for people who need SOPs, process documentation, workflow guides, or step-by-step operational instructions and want the result to be practical rather than polished corporate prose. If you use sop-creator for Technical Writing, the main value is structuring messy process knowledge into a readable, action-first format.
What sop-creator is good at
This skill is built to document repeatable business processes: who does what, in what order, with what tools, and what “done” looks like. The strongest use case is when you already know the process exists, but it lives in someone’s head, a loose chat thread, or a half-written note.
When sop-creator is the right fit
Use sop-creator when you need an SOP that another person can follow without improvising. It is a good fit for onboarding, internal ops, admin workflows, support procedures, recurring reviews, and compliance-adjacent tasks where consistency matters more than creative wording.
Main limitation to know
sop-creator is not a strategy planner or process re-engineering tool. It documents a process you can describe; it does not replace subject-matter review, policy approval, or a real operational audit. If the process is undefined, highly variable, or politically sensitive, expect to provide more context before the output becomes usable.
How to Use sop-creator skill
Install sop-creator
Install the sop-creator skill with:
npx skills add ognjengt/founder-skills --skill sop-creator
After install, start by opening skills/sop-creator/SKILL.md. This repository has a single core skill file, so there are no companion rules/, resources/, or scripts/ folders to consult for hidden behavior.
What input the skill needs
The sop-creator usage pattern is simple: give it a process description, not a blank prompt. Strong input usually includes the process name, the role doing it, the tools used, the desired end state, and any constraints.
Good starting input:
- “Document our monthly invoice approval workflow for finance coordinators in QuickBooks and Slack.”
- “Create an SOP for publishing blog posts in our CMS, including QA and final approval.”
- “Write an SOP for onboarding a new customer support agent using Zendesk and Notion.”
Weak input:
- “Make an SOP.”
- “Write a process doc for our team.”
How the execution flow works
The sop-creator guide follows a simple branch:
- If you provide no arguments, it responds with a prompt asking you to describe the process.
- If you provide process details up front, it begins working immediately.
- It also checks for
FOUNDER_CONTEXT.mdin the project root and uses it when present to tailor the SOP to your company, brand, tools, and audience.
That means the best results come when you supply enough context for the skill to skip guesswork on terminology, ownership, and operational boundaries.
Best workflow for better output
Start with a rough but specific brief, then revise the first draft for missing roles, exceptions, and quality checks. If you are using sop-creator for Technical Writing, feed it source material like an outline, a checklist, or a recorded process description, then ask it to convert that into a formal SOP with steps, prerequisites, and acceptance criteria.
sop-creator skill FAQ
Is sop-creator only for technical writing?
No. sop-creator for Technical Writing is one useful application, but the skill is broader. It is meant for any repeatable business process that needs clear execution instructions, especially when the audience needs consistency more than narrative explanation.
How is this different from a normal prompt?
A normal prompt can draft a process document, but sop-creator gives you a more repeatable workflow: it expects process input, looks for project context, and behaves like an SOP drafting assistant rather than a general chatbot. That reduces prompt drift when you need a standardized format.
Do I need a full process description first?
You do not need a perfect one, but you do need enough to identify the task, the owner, and the outcome. If your input is vague, the skill will likely need follow-up clarification before it can produce a useful SOP.
When should I not use sop-creator?
Do not use it when you need a decision tree, a policy rewrite, a troubleshooting guide, or a process redesign from scratch. It is strongest when the process already exists and your job is to document it clearly.
How to Improve sop-creator skill
Give more operational context
The fastest way to improve sop-creator results is to name the actual environment: team, role, tools, handoffs, and approval points. “Customer support refund workflow in Zendesk and Stripe for Tier 1 agents” is far better than “refund process,” because it lets the skill produce steps that match real work.
Include edge cases and boundaries
If there are exceptions, mention them early: approval thresholds, compliance checks, escalations, outage behavior, or “do not do” cases. These details prevent the SOP from reading like a generic checklist that fails at the first real-world exception.
Review for missing step ownership
A common failure mode is a clean-looking SOP with unclear responsibility. After the first draft, check whether every step has an owner, trigger, and output. If not, revise your source input and rerun sop-creator with those gaps called out explicitly.
Iterate with one process at a time
The skill works best when you document one workflow per run. If you ask for too many procedures at once, the result tends to flatten important differences. Split large operations into smaller SOPs, then combine them later if needed.