# Process Mapper

Use when documenting an end-to-end business process (procurement, onboarding, handoffs)...

- Repository: https://github.com/alirezarezvani/claude-skills (29114 stars)
- Category: Business
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add alirezarezvani/claude-skills --skill process-mapper -g -a claude-code -y`
Codex: `npx skills add alirezarezvani/claude-skills --skill process-mapper -g -a codex -y`
Cursor: `npx skills add alirezarezvani/claude-skills --skill process-mapper -g -a cursor -y`
Gemini CLI: `npx skills add alirezarezvani/claude-skills --skill process-mapper -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add alirezarezvani/claude-skills`

## Description

Use when documenting an end-to-end business process (procurement, onboarding, handoffs) and finding where work waits. Maps it with process_documenter.py, measures stages with cycle_time_analyzer.py and finds bottlenecks with bottleneck_detector.py.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# process-mapper

BPMN-style business process documentation, bottleneck detection, and cycle-time analysis for internal-operations leaders.

## Purpose

Internal-operations work suffers from three recurring failure modes:

1. **Implicit process**, the steps exist only in tribal knowledge, so handoffs drop and onboarding takes weeks.
2. **Invisible waiting**, most of the elapsed time on any business process is queue / wait / approval time, not actual work; teams optimize the wrong stage.
3. **Local optimization**, Goldratt's Theory of Constraints is ignored; resources are added to non-constraint stages, gaining nothing.

This skill produces a documented process map, identifies where work waits, and points the constraint out by name with deterministic logic, not LLM intuition.

## When to use

- Documenting a new business process (procurement intake, vendor onboarding, employee onboarding, incident handoff, expense reimbursement, customer onboarding, claims adjudication).
- An existing process is "too slow" but nobody can name the bottleneck.
- Cycle time is being measured but value-add ratio is not, so the team can't tell whether the process is healthy or waste-heavy.
- Cross-functional handoffs are dropping work and root cause is unclear.

## Workflow

Five-step deterministic flow:

The rest: https://github.com/alirezarezvani/claude-skills/blob/HEAD/business-operations/skills/process-mapper/SKILL.md