How do I install the Process Documentation skill?

Run npx skillmds@latest add majiayu000/process-documentation-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Process Documentation safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Process Documentation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Process Documentation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Process Documentation?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Process Documentation by majiayu000

Name: Process Documentation
Rating: 4.5 (4 reviews)
Author: majiayu000

Process Documentation

Document any business process in a clear, structured format. Use when asked to document a process, write a process guide, create a workflow document, or map out how something works. Produces a complete process document with steps, roles, inputs, outputs, and edge cases.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Process Documentation Skill

Produces clear, structured process documentation that someone new to a role can follow without needing to ask questions.

Required Inputs

Process name
Process description (rough notes are fine)
Who does this process (roles involved)
How often it runs (daily / weekly / monthly / event-triggered)
Tools involved
Known edge cases

Output Structure

Process: [Process Name]

Owner: [Role] | Frequency: [How often] | Estimated time: [Duration]

Purpose

[1-2 sentences. Why does this process exist? What breaks if it is not done?]

Scope

In scope: [What this covers] Out of scope: [What it does not cover]

Prerequisites

[Required access or information]
[Any dependency that must be completed first]

Roles and Responsibilities

Role	Responsibility
[Role 1]	[What they do]

Process Steps

Step 1: [Step name]

Who: [Role]
When: [Trigger or timing]
How: [Substeps numbered]
Output: [What exists at end of this step]
Tool: [System used]

[Continue for all steps]

Edge Cases and Exceptions

Situation	What to do	Who to contact
[Edge case]	[Action]	[Name/role]

Common Mistakes

[2-4 things people get wrong the first time]

Escalation Path

[Name/role] → [Next level] → [Final escalation]

Review

Next review due: [Date]

Quality Checks

Every step has a named role (not "someone" or "the team")
Edge cases and exceptions table is complete
Prerequisites are listed so someone new can prepare before starting
Escalation path is named (specific people or roles, not just "your manager")
Review date is set

Example Trigger Phrases

"Document this process: [description]"
"Write a process guide for [workflow]"
"Map out how [process] works"

---name: process-documentation-2description: Document any business process in a clear, structured format. Use when asked to document a process, write a process guide, create a workflow document, or map out how something works. Produces a complete process document with steps, roles, inputs, outputs, and edge cases.--- # Process Documentation Skill Produces clear, structured process documentation that someone new to a role can follow without needing to ask questions. ## Required Inputs - **Process name** - **Process description** (rough notes are fine) - **Who does this process** (roles involved) - **How often it runs** (daily / weekly / monthly / event-triggered) - **Tools involved** - **Known edge cases** ## Output Structure --- # Process: [Process Name] **Owner:** [Role] | **Frequency:** [How often] | **Estimated time:** [Duration] --- ### Purpose [1-2 sentences. Why does this process exist? What breaks if it is not done?] ### Scope **In scope:** [What this covers] **Out of scope:** [What it does not cover] ### Prerequisites - [ ] [Required access or information] - [ ] [Any dependency that must be completed first] --- ### Roles and Responsibilities | Role | Responsibility | |---|---| | [Role 1] | [What they do] | --- ### Process Steps **Step 1: [Step name]** - **Who:** [Role] - **When:** [Trigger or timing] - **How:** [Substeps numbered] - **Output:** [What exists at end of this step] - **Tool:** [System used] [Continue for all steps] --- ### Edge Cases and Exceptions | Situation | What to do | Who to contact | |---|---|---| | [Edge case] | [Action] | [Name/role] | --- ### Common Mistakes [2-4 things people get wrong the first time] ### Escalation Path [Name/role] → [Next level] → [Final escalation] ### Review Next review due: [Date] ## Quality Checks - [ ] Every step has a named role (not "someone" or "the team") - [ ] Edge cases and exceptions table is complete - [ ] Prerequisites are listed so someone new can prepare before starting - [ ] Escalation path is named (specific people or roles, not just "your manager") - [ ] Review date is set ## Example Trigger Phrases - "Document this process: [description]" - "Write a process guide for [workflow]" - "Map out how [process] works"

Frequently asked questions