Sop WriterSAFE

An agent skill published by revfactory.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: sop-writer
description: "standard operating procedure(SOP) agent team to processanalysis→procedure document→checklist→training materials→versionmanagementto Korean creation Full pipeline. 'SOP create it', 'standard operating procedurefrom writing', 'work procedurefrom', 'task ', 'operations procedure', 'procedure document writingplease do', 'checklist create it', 'work process document' etc. SOP writing before skill usage. existing process document procedure document·checklist·training materials writing degreeKRW. However, actual BPM whensystem building, workflow specialist development, ISO authentication company versus is outside this skill's scope."
---

# SOP Writer — standard operating procedure Full pipeline

standard operating procedure(SOP) processanalysis→procedure document→checklist→training materials→versionmanagement An agent team collaborates to generate all deliverables at once.

## execution mode

**agent team** — 5 agents communicate directly via SendMessage and cross-verify each other's work.

## agent composition

| agent | file | role | type |
|---------|------|------|------|
| process-analyst | `.claude/agents/process-analyst.md` | current work flow analysis, SIPOC, RACI | general-purpose |
| procedure-writer | `.claude/agents/procedure-writer.md` | stageby procedure document writing, decision-making minutebasis | general-purpose |
| checklist-designer | `.claude/agents/checklist-designer.md` | execution inspectiontable, quality design | general-purpose |
| training-developer | `.claude/agents/training-developer.md` | training guide, scenario annual, assessment document | general-purpose |
| version-controller | `.claude/agents/version-controller.md` | version management, cross-verification | general-purpose |

## workflow

### Phase 1: preparation (Orchestrator directly perform)

1. Extract from user input:
 - **target process**: work/procedure regarding SOPperson
 - **applied scope**: target departmentfrom/team/
 - ** requirement** (optional): related , authentication(ISO, HACCP etc.)
 - **existing document** (optional): current , work technicalfrom, 
2. `_workspace/` Create the directory at the project root
3. Organize input and save to `_workspace/00_input.md`
4. If existing files are provided, copy them to `_workspace/`and skip the corresponding Phase
5. Determine the **execution mode** based on the scope of the request

### Phase 2: team composition and execution

| order | task | responsible | dependency | deliverable |
|------|------|------|------|--------|
| 1 | process analysis | analyst | None | `_workspace/01_process_analysis.md` |
| 2 | procedure document writing | writer | task 1 | `_workspace/02_procedure_document.md` |
| 3a | checklist design | designer | task 2 | `_workspace/03_checklists.md` |
| 3b | training materials work | developer | task 2 | `_workspace/04_training_materials.md` |
| 4 | version management and verify | controller | task 3a, 3b | `_workspace/05_version_control.md` |

task 3a(checklist) and 3b(training materials) ** execution**. task 2(procedure document) only dependency.

**teamKRW between flow:**
- analyst complete → writerto process flow+RACI+example deliver, designerto quality degreepoint deliver
- writer complete → designerto verify standard deliver, developerto difficulty stage+actualnumber case deliver
- designer complete → developerto checklist usage deliver
- controller all deliverable cross-verification. 🔴 required revision findings when Request revision from the relevant agent -> rework -> re-verify (up to 2 rounds)

### Phase 3: integration and final deliverable

1. `_workspace/` Verify all files in the directory
2. verify reportConfirm that all critical revisions from the review report have been addressed
3. Report the final summary to the user:
 - process analysis — `01_process_analysis.md`
 - tablelevel procedure document — `02_procedure_document.md`
 - checklist tax — `03_checklists.md`
 - training materials — `04_training_materials.md`
 - version management and verify — `05_version_control.md`

## task scaleby mode

| user request pattern | execution mode | deploy agent |
|----------------|----------|-------------|
| "SOP create it", "procedure document overall" | **Full pipeline** | 5people beforeKRW |
| " process procedure document only " | **procedure document mode** | analyst + writer + controller |
| "checklist only create it" (procedure document provide) | **checklist mode** | designer + controller |
| "training materials create it" (procedure document provide) | **training mode** | developer + controller |
| " procedure document reviewplease do" | **review mode** | controller |

**existing file utilization**: user existing procedure document, etc. provide applicable stage case.

## data deliver protocol

| strategy | method | also |
|------|------|------|
| File-based | `_workspace/` | Store and share major deliverables |
| Message-based | SendMessage | Real-time key information transfer, revision requests |

File naming convention: `{}_{agent}_{deliverable}.{extensionspecialist}`

## error handling

| error type | strategy |
|----------|------|
| existing document None | user person based process re-composition, tablelevel reference |
| requirement people | applicable day framework web searchas research |
| agent failure | Retry once -> proceed without that deliverable, verify report specify |
| verifyfrom 🔴 findings | Request revision from the relevant agent -> rework -> re-verify (up to 2 rounds) |
| process | process minuteto eacheach SOP creation |

## test scenario

### flow
**Prompt**: " KRW joining processing process SOP create it. personcompanyteam target 50person scale company."
**expected result**:
- process analysis: hiring→joiningfrom→whensystemetc.record→equipmentdegreegrade→training→OJT flow
- procedure document: stageby detailed procedure + RACI + decision-making minutebasis
- checklist: joining before/day/1weekday/1months inspectiontable
- training materials: personcompanyperson res

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.