The problem

Process knowledge often lives in the heads of a few team members, leading to inconsistent execution and bottlenecks during handoffs. Scaling a team without documented procedures causes errors, missed QA steps, and confusion over who owns specific tasks.

What it does

• Generates structured SOPs with mandatory sections for metadata, purpose, and scope.
• Maps out step-by-step instructions identifying the actor, action, and tool for every task.
• Defines clear role responsibilities, including executors, approvers, and escalation contacts.
• Builds integrated QA checklists and escalation workflows to handle process failures.
• Inserts screenshot placeholders for UI-based tasks to guide visual documentation.

Why this beats prompting it yourself

General prompts often miss critical operational guardrails like version control, escalation paths, and review cycles. This skill enforces a professional documentation standard, ensuring you never skip the "what happens if this fails" logic that makes an SOP actually useful for a team.

Use cases

• Standardizing new hire onboarding workflows for sales or engineering teams.
• Documenting monthly financial reconciliation tasks for an accounting department.
• Creating client campaign handoff procedures for agency account managers.
• Building support ticket triage and escalation paths for customer success teams.

Known limitations

It will not invent process steps you haven't described. If details are missing, it uses TODO placeholders for you to fill in manually.