Process Doc

What This Skill Does

• This skill documents a business process as a complete standard operating procedure (SOP).
• It's designed for operations managers, team leads, and anyone responsible for creating and maintaining process documentation.
• The skill guides users through defining the process, identifying roles and responsibilities, and documenting each step in detail.

When to Use

• Document a new onboarding process.
• Create an SOP for customer support inquiries.
• Standardize a sales process.
• Document a software deployment process.
• Update an existing process documentation.

Key Features

• Creates a structured SOP document.
• Defines the purpose and scope of the process.
• Generates a RACI matrix.
• Creates a process flow diagram.
• Provides detailed step-by-step instructions.
• Includes exceptions and edge cases.

Manual Installation

/process-doc

• If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.

• md.

Document a business process as a complete standard operating procedure (SOP).

Usage

/process-doc $ARGUMENTS

How It Works

• Walk me through the process — describe it, paste existing docs, or just tell me the name and I'll ask the right questions.
• I'll produce a complete SOP.

Output

Process Document: [Process Name]

Owner: [Person/Team] | Last Updated: [Date] | Review Cadence: [Quarterly/Annually]

Purpose

[Why this process exists and what it accomplishes]

Scope

[What's included and excluded]

RACI Matrix

Process Flow

[ASCII flowchart or step-by-step description]

Detailed Steps

Step 1: [Name]

Who: [Role] When: [Trigger or timing] How: [Detailed instructions] Output: [What this step produces]

Step 2: [Name]

[Same format]

Exceptions and Edge Cases

Metrics

Related Documents

[Link to related process or policy]

If Connectors Available

If ~~knowledge base is connected: Search for existing process documentation to update rather than duplicate Publish the completed SOP to your wiki

If ~~project tracker is connected: Link the process to related projects and workflows Create tasks for process improvement action items

Tips

• Start messy — You don't need a perfect description.

• Tell me how it works today and I'll structure it. Include the exceptions — "Usually we do X, but sometimes Y" is the most valuable part to document. Name the people — Even if roles change, knowing who does what today helps get the process right./process-doc

• Start messy — You don't need a perfect description.

• Tell me how it works today and I'll structure it. Include the exceptions — "Usually we do X, but sometimes Y" is the most valuable part to document. Name the people — Even if roles change, knowing who does what today helps get the process right.