Sop Builder

View saved version →

---
name: process-documentation
description: Convert workflows into process maps, RACI tables, checklists, and improvement plans.
---

# Business Process Documentation

Document the current or proposed process faithfully and make its logic easy to inspect.

## Deliverables

Choose the smallest useful set based on the request:

- swimlane-style process map in text or Mermaid;
- RACI responsibility matrix;
- input/output and handoff table;
- decision tree and exception paths;
- control and risk register;
- checklist or runbook;
- current-state versus future-state comparison;
- prioritized improvement backlog.

Mark proposed steps and inferred ownership clearly. Preserve the user's terminology unless a glossary is requested. Do not claim that a process is compliant, approved, or validated without evidence.

View saved version →

---
name: sop-builder
description: Create clear, auditable standard operating procedures from business goals and process details.
---

# SOP Builder

Turn a user's process description into an implementation-ready SOP. Separate confirmed facts, assumptions, open questions, and recommendations.

## Workflow

1. Identify the process purpose, trigger, desired outcome, scope, exclusions, and audience.
2. Map roles, responsibilities, inputs, systems, handoffs, approvals, decision points, exceptions, controls, and outputs.
3. Write sequential steps with action owners, required inputs, expected outputs, and completion criteria.
4. Add safety, quality, privacy, escalation, and record-keeping controls only when supported by the user's context; label recommendations as recommendations.
5. Add a checklist, metrics, review cadence, version history, and training notes when useful.
6. Highlight missing information that could change the process materially.

## Default output

- SOP title and document control
- Purpose, scope, and definitions
- Roles and responsibilities
- Preconditions, inputs, tools, and records
- Numbered procedure with decision points and exceptions
- Quality and control checklist
- Escalation path and owner
- Metrics and review cadence
- Assumptions, open questions, and implementation notes

Never invent legal, regulatory, security, financial, or operational requirements. If the process touches a regulated or high-risk area, recommend professional review.

View saved version →

---
name: writing-quality
description: Make SOPs and process documents concise, consistent, actionable, and easy to maintain.
---

# Process Writing Quality

Use plain language, one action per step, consistent role names, measurable completion criteria, and explicit exception handling. Prefer active voice and precise verbs. Keep warnings near the step they affect. Define acronyms on first use. Flag ambiguity instead of hiding it. Preserve the distinction between required actions, optional guidance, assumptions, and recommendations.