feat: add 27 new skills across 7 professions — 80 skills, 21 plugins (v5.0.0)
This commit is contained in:
@@ -0,0 +1,93 @@
|
||||
---
|
||||
name: sop-writer
|
||||
description: "Write a Standard Operating Procedure (SOP) for any operational task. Use when asked to write an SOP, standard operating procedure, work instruction, or operating manual. Produces a formal SOP with purpose, scope, procedure steps, quality checks, and version control."
|
||||
---
|
||||
|
||||
# SOP Writer Skill
|
||||
|
||||
Produces formal, audit-ready SOPs suitable for regulated industries, ISO certification, or operational scaling.
|
||||
|
||||
## Required Inputs
|
||||
- **SOP title** (e.g. "SOP-001: New Client Onboarding")
|
||||
- **Department / function**
|
||||
- **Process description**
|
||||
- **Regulatory or quality standard** (ISO 9001, GMP, CQC, FCA, etc.)
|
||||
- **Roles involved**
|
||||
- **Tools or equipment used**
|
||||
|
||||
## Output Structure
|
||||
|
||||
---
|
||||
|
||||
**[COMPANY NAME] — Standard Operating Procedure**
|
||||
|
||||
| Document ID | [SOP-XXX] |
|
||||
|---|---|
|
||||
| Title | [Title] |
|
||||
| Department | [Department] |
|
||||
| Version | 1.0 |
|
||||
| Effective date | [Date] |
|
||||
| Review date | [Date] |
|
||||
| Status | Draft / Under review / Approved |
|
||||
|
||||
---
|
||||
|
||||
### 1. Purpose
|
||||
[1-2 sentences. Why does this SOP exist?]
|
||||
|
||||
### 2. Scope
|
||||
**Applies to:** [Roles, departments, locations]
|
||||
**Does not apply to:** [Explicit exclusions]
|
||||
|
||||
### 3. Definitions
|
||||
| Term | Definition |
|
||||
|---|---|
|
||||
| [Term] | [Plain English definition] |
|
||||
|
||||
### 4. Responsibilities
|
||||
| Role | Responsibility |
|
||||
|---|---|
|
||||
| [Role] | [Specific responsibility] |
|
||||
|
||||
### 5. Required Materials / Tools / Access
|
||||
- [Item]
|
||||
|
||||
### 6. Procedure
|
||||
|
||||
| Step | Action | Responsible | Record/Output |
|
||||
|---|---|---|---|
|
||||
| 6.1.1 | [Imperative action: "Open [system] and navigate to [location]"] | [Role] | [What to record] |
|
||||
|
||||
NOTE: Steps must be written in imperative form. Each step must have one action only.
|
||||
|
||||
### 7. Quality Checks
|
||||
|
||||
| Check point | What to verify | Pass criteria | If fail |
|
||||
|---|---|---|---|
|
||||
| [After step X] | [What to check] | [What good looks like] | [What to do] |
|
||||
|
||||
### 8. Non-Conformance
|
||||
1. [Immediate action]
|
||||
2. [Who to notify]
|
||||
3. [How to document deviation]
|
||||
|
||||
### 9. References
|
||||
[Related SOPs, policies, standards]
|
||||
|
||||
### 10. Document History
|
||||
|
||||
| Version | Date | Author | Changes |
|
||||
|---|---|---|---|
|
||||
| 1.0 | [Date] | [Name] | Initial release |
|
||||
|
||||
## Quality Checks
|
||||
- All steps in imperative form
|
||||
- Each step has exactly one action
|
||||
- Roles specified for every step
|
||||
- Quality checkpoints at critical stages
|
||||
- Non-conformance process defined
|
||||
|
||||
## Example Trigger Phrases
|
||||
- "Write an SOP for [process]"
|
||||
- "Create a standard operating procedure for [task]"
|
||||
- "Write a work instruction for [process]"
|
||||
Reference in New Issue
Block a user