SOP & Process Documentation
Create clear standard operating procedures with step-by-step instructions and role assignments
$5
Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsSOP & Process Documentation
Example session with this skill installed
Document our client onboarding. Account manager gets the signed contract, creates a Slack channel, and invites the client. Then they need to setup the Jira board and assign the project lead.
- Read your context and instructions
- Compiled the sop & process
I have converted your onboarding notes into a formal Step-by-Step Procedure (Format A) with roles and error-prevention notes.
STANDARD OPERATING PROCEDURE
PROCESS NAME: Client Onboarding Process
VERSION: 1.0
EFFECTIVE DATE: 2024-05-22
NEXT REVIEW DATE: 2024-11-22
DOCUMENT OWNER: Account Operations Lead
PURPOSE
To ensure every new client is correctly integrated into communication channels and project management tools, preventing delays in project kickoff.
SCOPE
Applies to the Account Management team for all newly signed service contracts.
TRIGGER / WHEN TO START THIS PROCESS
Receipt of a signed contract via the digital signature platform.
REQUIRED BEFORE YOU BEGIN
- Access to the company Slack workspace
- Project Lead permissions in Jira
- Copy of the signed contract (PDF)
| Process frequency | Review cycle |
|---|---|
| Daily/weekly process | Review every 6 months |
PROCEDURE
STEP 1: Initialize Communications
Who: Account Manager
What to do: Create a new Slack channel using the naming convention #client-[ClientName]. Set the channel to 'Private' and invite the client contact and internal team.
Expected output: Slack channel active with all stakeholders present.
⚠️ Common error: Forgetting to set the channel to Private. Always verify privacy settings before inviting the client.
STEP 2: Setup Project Tracking
Who: Account Manager
What to do: Create a new Jira project using the "Standard Kanban" template. Link the Slack channel to the Jira project using the /jira connect command.
Expected output: Jira project created and synced with Slack.
STEP 3: Assign Leadership
Who: Account Manager
What to do: Assign the Project Lead role within Jira to the designated technical lead and transition the first task to "To Do".
Expected output: Project Lead assigned and notified.
DEFINITION OF COMPLETE
Process is complete when the client has sent a "Hello" message in Slack and the Jira board contains at least one active task assigned to the Project Lead.
ESCALATION
If the client contact is not responsive within 24 hours of the Slack invite, escalate to the Head of Sales.
VERSION HISTORY
Version | Date | Author | Changes Made
1.0 | 2024-05-22 | Account Manager | Initial version
New team members: Follow this document step by step on your first 3 attempts. After that, flag anything that doesn't match what you're actually seeing in the system.
Next steps
- Review the Slack naming convention to ensure it matches your current internal standards.
- Verify the Jira template specified matches your current project workflow.
- Distribute this PDF to the Account Management team for immediate use.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Process knowledge often lives only in the heads of senior staff or in messy, unstructured notes. This makes scaling impossible, leads to frequent errors, and turns employee onboarding into a bottleneck.
Built with beginners in mind — just walk through your process step by step in your own words, and this skill organizes it into a polished SOP. No technical writing experience required. Experienced professionals save time too: structured, standardized output means every procedure meets documentation standards on the first draft.
What it does
- Converts rough notes, voice transcripts, or verbal descriptions into professional documentation.
- Generates formatted output in three distinct styles: Step-by-Step, Decision Tree, or Checklist.
- Assigns clear roles and responsibilities to ensure accountability.
- Identifies common error points at specific steps to prevent recurring mistakes.
- Establishes version control and review cycles for long-term maintenance.
Why this beats prompting it yourself
General AI often produces vague advice like "be efficient" or "communicate well." This skill enforces strict documentation standards, requiring every step to start with an action verb and replacing ambiguous timing with concrete deadlines. It ensures every decision point has a logical path and every process includes a specific "Definition of Done" that generic prompts overlook.
Use cases
- Creating training manuals for new hires to reduce time-to-productivity.
- Documenting branching support workflows for customer service teams.
- Building quality control checklists for recurring technical deployments.
- Standardizing internal operations like invoicing, onboarding, or inventory management.
Known limitations
Requires a clear description of the process steps to be effective. It cannot invent business logic that you have not provided.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 12 days ago
- Passed all security checks, Safe to install