---
name: sop-guide-manager
description: "Builds a full SOP document with purpose, scope, procedure, roles, tools, and a review schedule, ready to file in a department handbook. Use when you want a complete handbook-ready SOP with roles, tools, and a review schedule for a departmental process like onboarding. Do not use for polishing an existing draft or writing a one-task technical runbook. Related topics: productivity, work, sop."
---

# SOP Guide Manager

Builds a full SOP document with purpose, scope, procedure, roles, tools, and a review schedule, ready to file in a department handbook.

## When to use

Use this skill when you want a complete handbook-ready SOP with roles, tools, and a review schedule for a departmental process like onboarding. Do not use it for polishing an existing draft or writing a one-task technical runbook.

## 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. Title the document and write the purpose from the stated goal plus a scope suited to the department.
3. Write numbered steps up to the step count and tag each with the responsible role.
4. Write a roles section with one line per selected role stating what that role owns.
5. Map each tool to the step that uses it in a tools section.
6. Define the review schedule with frequency, reviewer, and the events that force an early review.

## Inputs

- **Process name** (free text, e.g. "Onboarding new employees")
- **Primary goal** (longer free text)
- **Department** (choose one: HR, IT, Finance, Operations, Marketing, Sales)
- **Number of steps** (number from 3 to 20)
- **Responsible roles** (choose any: Manager, Supervisor, Analyst, Technician, Coordinator)
- **Required tools** (longer free text)
- **Review frequency** (choose one: Monthly, Quarterly, Annually, Never)

## Output

A markdown file titled with the process name containing Purpose, Scope, Procedure, Roles, Tools, and Review Schedule sections.

## Prompt template

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

### SOP Guide Manager

Produce a complete SOP document that I can file in our handbook and keep current.

- Process name: {{Process name}}
- Primary goal: {{Primary goal}}
- Department: {{Department}}
- Number of steps: {{Number of steps}}
- Responsible roles: {{Responsible roles}}
- Required tools: {{Required tools}}
- Review frequency: {{Review frequency}}

Title the document with the process name. Write the purpose from the goal, then a scope that fits the department. Give the procedure as numbered steps up to the step count, and tag each step with the role from the list that performs it. Add a roles section with one line per selected role describing what they own. Add a tools section that says which step uses which tool. Finish with a review schedule: the chosen frequency, who reviews, and what triggers an early review such as a tool change. If the frequency is Never, say so and name the event that would force a revision anyway.

## Pitfalls

- Assigning every step to the same role, which hides who is truly accountable.
- Listing tools without saying where they are used, so the tools section becomes decoration.
- Setting a review schedule with no owner, which means it never happens.
