Process Doc

1---2name: process-doc3description: Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, building a RACI to clarify who owns what, writing an SOP for a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done.4argument-hint: "<process name or description>"5---6 7# /process-doc8 9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).10 11Document a business process as a complete standard operating procedure (SOP).12 13## Usage14 15```16/process-doc $ARGUMENTS17```18 19## How It Works20 21Walk 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.22 23## Output24 25```markdown26## Process Document: [Process Name]27**Owner:** [Person/Team] | **Last Updated:** [Date] | **Review Cadence:** [Quarterly/Annually]28 29### Purpose30[Why this process exists and what it accomplishes]31 32### Scope33[What's included and excluded]34 35### RACI Matrix36| Step | Responsible | Accountable | Consulted | Informed |37|------|------------|-------------|-----------|----------|38| [Step] | [Who does it] | [Who owns it] | [Who to ask] | [Who to tell] |39 40### Process Flow41[ASCII flowchart or step-by-step description]42 43### Detailed Steps44 45#### Step 1: [Name]46- **Who**: [Role]47- **When**: [Trigger or timing]48- **How**: [Detailed instructions]49- **Output**: [What this step produces]50 51#### Step 2: [Name]52[Same format]53 54### Exceptions and Edge Cases55| Scenario | What to Do |56|----------|-----------|57| [Exception] | [How to handle it] |58 59### Metrics60| Metric | Target | How to Measure |61|--------|--------|----------------|62| [Metric] | [Target] | [Method] |63 64### Related Documents65- [Link to related process or policy]66```67 68## If Connectors Available69 70If **~~knowledge base** is connected:71- Search for existing process documentation to update rather than duplicate72- Publish the completed SOP to your wiki73 74If **~~project tracker** is connected:75- Link the process to related projects and workflows76- Create tasks for process improvement action items77 78## Tips79 801. **Start messy** — You don't need a perfect description. Tell me how it works today and I'll structure it.812. **Include the exceptions** — "Usually we do X, but sometimes Y" is the most valuable part to document.823. **Name the people** — Even if roles change, knowing who does what today helps get the process right.