The problem

Process knowledge often lives in the heads of a few team members, leading to inconsistent results, bottlenecks, and scaling friction. When documentation exists, it is usually vague, lacks quality checks, and fails to guide a new hire through a task without constant supervision.

What it does

• Converts rough notes, Loom transcripts, or task descriptions into structured SOPs with clear step-by-step instructions.
• Generates specific screenshot placeholders so team members know exactly what visual evidence to document.
• Builds comprehensive QA checklists and common error troubleshooting guides to ensure output consistency.
• Defines roles, responsibilities, and escalation paths to prevent project stalls.
• Audits existing process documents and assigns a readiness score based on clarity and completeness.

Why this beats prompting it yourself

General prompts often miss the "hidden" operational details like version control, handover notes, and specific screenshot locations. This skill enforces a 15-point structural framework that ensures every SOP is training-ready and compliant with operational best practices right out of the gate.

Use cases

• Documenting client onboarding sequences for agency account managers.
• Standardizing weekly newsletter publishing and email marketing workflows.
• Creating admin and finance routines for virtual assistants to follow.
• Auditing legacy process documents to identify missing quality controls.

Known limitations

Requires an initial rough process or task description to generate a draft. It cannot provide legally binding or regulatory advice for high-risk industries.