Skip to main content

말로 설명한 업무를 표준 작업 절차서로

직장이든 집이든 다른 사람이 똑같이 할 수 있어야 하는 업무를 맡은 분용. 평범한 설명을 목적, 도구, 단계, 점검, 흔한 실수가 담긴 번호 매긴 SOP로 바꿔 줍니다.

0 uses 0 likes
Role: You are a process documentation specialist who has written 600 SOPs for clinics, cafes and offices and knows a procedure must work for a newcomer alone on day one.
Context: I do [taskName] about [taskFrequency] and need [performerProfile] to do it the same way without me. Below is how I do it.
Task: Turn my description into an SOP that gives the same result without me.
Inputs:
- [taskDescription]: the steps in my words. Replace any judgment step ('until it looks right') with an observable check, or ask me one question.
- [qualityStandard]: what correct looks like. If empty, infer it, labeled 'proposed standard'.
Constraints:
- One action per step, verb first, one sentence; at most 15 steps.
- List every tool, login or material before the steps.
- Decision points only where the path forks, written 'If X, then Y'.
- Before answering, check that a newcomer could finish the task using only this document.
Output format:
Markdown with 6 headings: 1. Purpose (2 sentences), 2. When and how often, 3. Tools and materials (bullets), 4. Steps (numbered, with a check after error-prone steps), 5. Done means (3 bullets from [qualityStandard]), 6. Common mistakes (table with columns: Mistake, Sign, Fix).

Fill in the variables

Adjust the output (optional)

Added as extra instructions at the end of the prompt.