---
name: sop-guide-helper
description: "Produces a task-level SOP for a technical or departmental job, listing tools, an owner, numbered steps, and references so the task is done the same way every time. Use when you need a single-task procedure, like setting up a server or a department routine, with tools, owner, and references listed. Do not use for documenting a whole multi-team process or writing a full SOP with a review schedule. Related topics: productivity, work, sop."
---

# SOP Guide Helper

Produces a task-level SOP for a technical or departmental job, listing tools, an owner, numbered steps, and references so the task is done the same way every time.

## When to use

Use this skill when you need a single-task procedure, like setting up a server or a department routine, with tools, owner, and references listed. Do not use it for documenting a whole multi-team process or writing a full SOP with a review schedule.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. State the task scope as one outcome and name the condition the task starts from.
3. List the required tools and systems before any step is written.
4. Write the requested number of numbered steps, each one imperative action naming the exact command, menu, or form.
5. End with a verification step that proves the task succeeded.
6. Add the owner role and the reference documents.

## Inputs

- **Task title** (free text, e.g. "Initialize a new server")
- **Objective** (longer free text)
- **Department** (choose one: IT, Operations, HR, Finance, Marketing)
- **Required tools** (longer free text)
- **Number of steps** (number from 3 to 20)
- **Owner role** (free text, e.g. "System administrator")
- **Reference documents** (longer free text)

## Output

A markdown SOP with Title, Objective, Scope, Required Tools, numbered Procedure Steps matching the requested count, Owner, and References.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### SOP Guide Helper

Write a short SOP for one specific task.

- Task title: {{Task title}}
- Objective: {{Objective}}
- Department: {{Department}}
- Required tools: {{Required tools}}
- Number of steps: {{Number of steps}}
- Owner role: {{Owner role}}
- Reference documents: {{Reference documents}}

Use the task title and objective to set the scope: one task, one outcome, with the starting condition stated. List the required tools before the steps so nothing is discovered mid-task. Write exactly the requested number of numbered steps, each a single action in the imperative with the command, menu, or form named where one applies. Add a verification line to the last step that shows the task actually succeeded. Close with the owner and the reference documents.

## Pitfalls

- Writing steps like set it up properly without the exact command or setting, which forces the reader to guess.
- Letting the step count drift from the number requested.
- Omitting a verification step, so no one knows if the task really worked.
