Receber por email
← Voltar para o catálogo

sop-writer

Cria um Procedimento Operacional Padrão (POP) para qualquer tarefa operacional. Gera um POP formal completo com propósito, escopo, etapas, verificações de qualidade e controle de versão, ideal para instruções de trabalho ou manuais.

991estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add mohitagw15856/pm-claude-skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/sop-writer/svg)](https://www.skillteca.com.br/skills/sop-writer)
#ai

Skills relacionadas

Ver todas de Produtividade →

Alerta por categoria

Receba novas skills de Produtividade toda segunda

1 email curto, só com as skills novas de Produtividade. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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 written in imperative form ("Open...", "Navigate...", "Confirm...")
  • [ ] Each step has exactly one action
  • [ ] Role specified for every step
  • [ ] Quality checkpoints at critical stages
  • [ ] Non-conformance process defines who to notify and how to document
  • [ ] Document history table and review date are included

Example Trigger Phrases

  • "Write an SOP for [process]"
  • "Create a standard operating procedure for [task]"
  • "Write a work instruction for [process]"
Compartilhar X LinkedIn