Write Standard Operating Procedure
Write a GxP-compliant Standard Operating Procedure (SOP). Covers regulatory SOP template structure (purpose, scope, definitions, responsibilities, procedure, references, revision history), approval workflow design, periodic review scheduling, and operational procedures for system use. Use when a new validated system requires operational procedures, when existing informal procedures need formalisation, when an audit finding cites missing procedures, when a change control triggers SOP updates, or when periodic review identifies outdated procedural content.
Install
npx skills add pjt222/agent-almanac --skill write-standard-operating-proceduregit clone --depth 1 https://github.com/pjt222/agent-almanac.git /tmp/agent-almanac
mkdir -p ~/.claude/skills
cp -r /tmp/agent-almanac/i18n/caveman-lite/skills/write-standard-operating-procedure ~/.claude/skills/write-standard-operating-procedurePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Write Standard Operating Procedure Create a GxP-compliant Standard Operating Procedure that provides clear, auditable instructions for regulated activities. ## When to Use - A new validated system requires operational procedures - Existing procedures need formalisation into SOP format - An audit finding cites missing or inadequate procedures - A change control triggers SOP updates - Periodic review identifies outdated procedural content ## Inputs - **Required**: Process or system the SOP covers - **Required**: Regulatory context (GMP, GLP, GCP, 21 CFR Part 11, EU Annex 11) - **Required**: Target audience (roles that will follow this SOP) - **Optional**: Existing informal procedures, work instructions, or training materials - **Optional**: Related SOPs that interface with this procedure - **Optional**: Audit findings or regulatory observations driving the SOP creation ## Procedure ### Step 1: Assign Document Control Metadata ```markdown # Standard Operating Procedure ## Document ID: SOP-[DEPT]-[NNN] ## Title: [Descriptive Title of the Procedure] | Field | Value | |-------|-------| | Document ID | SOP-[DEPT]-[NNN] | | Version | 1.0 | | Effective Date | [YYYY-MM-DD] | | Review Date | [YYYY-MM-DD + review period] | | Department | [Department name] | | Author | [Name, Title] | | Reviewer | [Name, Title] | | Approver | [Name, Title] | | Classification | [GxP-Critical / GxP-Supporting] | | Supersedes | [Previous SOP ID or "N/A — New"] | ```
Details
- Skill name
write-standard-operating-procedure- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/write-standard-operating-procedure/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Write Standard Operating Procedure skill do?
Write a GxP-compliant Standard Operating Procedure (SOP). Covers regulatory SOP template structure (purpose, scope, definitions, responsibilities, procedure, references, revision history), approval workflow design, periodic review scheduling, and operational procedures for system use. Use when a new validated system requires operational procedures, when existing informal procedures need formalisation, when an audit finding cites missing procedures, when a change control triggers SOP updates, or when periodic review identifies outdated procedural content.
How do I install the Write Standard Operating Procedure skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add pjt222/agent-almanac --skill write-standard-operating-procedure. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Write Standard Operating Procedure popular?
It lives in pjt222/agent-almanac, which has 45 GitHub stars and 4 forks, and is included in 1 curated skill list.
Related skills
Adapt Architecture
45pjt222/agent-almanac
Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.
Adaptic
45pjt222/agent-almanac
Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.
Add Puzzle Type
45pjt222/agent-almanac
Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.
Write Validation Documentation
45pjt222/agent-almanac
Write IQ/OQ/PQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.
Write Roxygen Docs
45pjt222/agent-almanac
Write roxygen2 documentation for R package functions, datasets, and classes. Covers all standard tags, cross-references, examples, and generating NAMESPACE entries. Follows tidyverse documentation style. Use when adding documentation to new exported functions, documenting internal helpers or datasets, documenting S3/S4/R6 classes and methods, or fixing documentation-related R CMD check notes.
Write Vignette
45pjt222/agent-almanac
Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.