process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time
Profile →npx skills add alirezarezvani/claude-skills --skill process-mapper --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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-function
- Purpose
- When to use
- Workflow
- Scripts
- Quick example
- References
- Assumptions
- Anti-patterns
- Distinct from
- Forcing-question library (Matt Pocock grill discipline)
Renders a BPMN-style swim-lane diagram + normalized JSON for the built-in 6-stage procurement-intake example cd business-operations/skills/process-mapper && python3 scripts/process_documenter.py --sample
What does the process-mapper skill do?
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill process-mapper --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.