- Home
- Skills
- Business & Operations
- sop generators
Works with the AI Agents you already use
sop generators
Convert messy transcripts and notes into rigorous, verb-first SOPs with RACI tables and checklists.
Free
sop generators
Example session with this skill installed
Turn these notes into an SOP: When a new PR is opened, the dev runs npm test. If it fails, they fix it. If it passes, they tag @qa. QA checks visual regressions in Chromatic and approves in GitHub.
- Read your context and instructions
- Compiled the sop generators
I have processed the PR review notes into a structured SOP, including a RACI matrix and a one-page checklist for the engineering team.
Standard Operating Procedure: Pull Request Review & QA
Purpose & scope: To ensure code quality and visual consistency before merging to main. Applies to all frontend repository contributions.
Trigger: A developer opens a new Pull Request (PR) in the repository.
Roles & RACI
| Role | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Developer | X | |||
| QA Engineer | X | X | ||
| Tech Lead | X | X |
Procedure Steps
- Initiate testing — Run
npm testin the local environment.- Expected Result: All unit tests pass with 100% success rate.
- Evaluate test results — Check terminal output for errors.
- Stop Condition: If any test fails, developer must apply fixes and return to Step 1.
- Request QA review — Tag
@qain the GitHub PR comments and assign the user.- Expected Result: QA receives a notification and assigns themselves to the PR.
- Perform visual audit — Open the Chromatic build linked in the PR checks.
- Expected Result: Visual changes match design specifications exactly.
- Finalize approval — Click "Approve" in GitHub and add a summary comment.
- Expected Result: PR status changes to "Approved," allowing merge.
Exceptions & Escalation
- Chromatic build failure: Verify build logs → Retry build once → If still failing, escalate to DevOps.
- QA unavailability: If no response in 4 hours → Tag Tech Lead for emergency review.
One-Page Checklist
- Run
npm testlocally. - Verify 100% pass rate.
- Tag
@qaon GitHub PR. - Review Chromatic visual snapshots.
- Submit GitHub Approval.
Next steps
- Add the specific Chromatic project URL to the
[[PLACEHOLDER]]in the full doc. - Distribute the training script to the QA lead for the next sprint kickoff.
Connects securely to your tools. The creator never sees your data.
About this skill
Documenting internal processes usually results in tribal knowledge leaks or vague instructions that lead to errors. This skill forces technical precision into your documentation, ensuring a new hire can execute a procedure correctly on their first day without assistance. It transforms messy meeting transcripts, Slack threads, or rough bullet points into structured Standard Operating Procedures.
What it does
- Role mapping builds a RACI table to define responsibility and accountability for every task.
- Actionable sequencing creates verb-first numbered steps limited to 15 words for maximum clarity.
- Error handling defines explicit stop conditions and escalation paths for common process failures.
- Branch logic provides if/then tables for complex decision points within a workflow.
- Multi-format output generates a full technical SOP, a condensed printable checklist, and a brief training script.
How it works
- Intake the raw process data from transcripts, notes, or messages to extract triggers and tools.
- Clarify gaps by answering targeted questions about missing roles or undocumented steps.
- Structure the output using a fixed skeleton including scope, triggers, RACI, and version control.
- Audit the draft against a strict quality bar to ensure zero assumptions of prior experience.
Frameworks & tools
This skill produces Markdown-formatted documentation compatible with Notion, GitHub Wiki, Confluence, and Obsidian.
Why this beats prompting it yourself
Generic prompts often produce flowery, prose-heavy descriptions that are impossible to follow under pressure. This skill enforces a "one action per step" rule and mandates expected results for every instruction, eliminating the ambiguity that leads to operational downtime.
Use cases
- Drafting deployment runbooks from a developer's quick screenshare transcript.
- Converting a Slack thread about client onboarding into a repeatable team checklist.
- Building a disaster recovery plan with clear escalation paths and wait times.
- Standardizing monthly financial reporting tasks across a distributed ops team.
Known limitations
Large processes exceeding two pages are flagged for splitting into sub-processes. Requires placeholder confirmation for specific tool URLs or internal file paths.
Processes spanning more than two pages will be flagged for splitting. Internal URLs or specific file paths must be manually updated in the provided placeholders.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 23 days ago
- Free with an Agensi account
Permissions
No special permissions declared or detected