Agent skill

Process Mapper

by alirezarezvani in alirezarezvani/claude-skills

A skill your agent uses when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff…

MITAuto-check passedBusiness, Finance & HR

Install Process Mapper

skills CLI
$ npx skills add alirezarezvani/claude-skills --skill process-mapper -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alirezarezvani/claude-skills process-mapper --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/business-operations/skills/process-mapper .claude/skills/process-mapper && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
process-mapper
GitHub stars
28k
Token cost
~2.2k tokens
SKILL.md length
993 words
Files
8 (incl. scripts, references, assets)
Skills in repo
342
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff…

  • Works in 3 steps: Implicit process — the steps exist only… → Invisible waiting — most of the elapsed… → Local optimization — Goldratt's Theory…
  • Process-improvement owner needs to document an end-to-end business process (procurement
  • SKILL.md covers Purpose, When to use, Workflow and Scripts, plus 6 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Process Mapper is an agent skill from alirezarezvani/claude-skills. 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…

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `assets/process_template.md`, `references/bottleneck_anti_patterns.md` and `references/bpmn_essentials.md`).

It sits in Business, Finance & HR, covering Operations and SOPs, Site reliability engineering and Customer success. It works with Python. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.

When your agent uses it

  • Process-improvement owner needs to document an end-to-end business process (procurement
  • Employee onboarding
  • Incident handoff
  • Customer-onboarding

Example prompts

  • “/process-mapper”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  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…
  3. Local optimization — Goldratt's Theory of Constraints is ignored; resources are added to non-constraint stages, gaining nothing.

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Process Mapper loads about 2.2k tokens when it runs, and up to ~7.5k if it reads all its reference files. Until then it costs about 206 tokens; SKILL.md has 993 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~206
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 993 words, ~2,235 tokens.

Download SKILL.mdSave it as .claude/skills/process-mapper/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
process-mapper
description
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 analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
version
2.8.0
author
claude-code-skills
license
MIT
tags
bizops, process, bpmn, bottleneck, cycle-time, lean, six-sigma, value-stream
compatible_tools
claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli

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:

  1. Intake. Capture the process as a JSON file with one entry per stage: name, owner, type (value-add | wait | rework), duration_minutes_p50, duration_minutes_p90. Use assets/process_template.md and its JSON skeleton.
  2. Map stages. Run process_documenter.py to produce an ASCII swim-lane diagram + a normalized JSON artifact. The swim-lane separates lanes by owner so cross-functional handoffs become visible.
  3. Measure cycle time. Run cycle_time_analyzer.py to compute total P50, total P90, value-add ratio (VA%), and a Little's-Law throughput estimate. Verdict: VA% > 25% = HEALTHY, 10–25% = TYPICAL, < 10% = WASTE-HEAVY.
  4. Detect bottlenecks. Run bottleneck_detector.py with the appropriate --profile (saas / services / manufacturing / healthcare). Output is a ranked list with severity (CRITICAL / HIGH / MEDIUM), root-cause hypothesis, and one recommended action per finding.
  5. Recommend. Pair the bottleneck list with the cycle-time verdict; recommend a single constraint-focused intervention per Goldratt's "subordinate everything to the constraint" rule. Don't recommend optimization of a non-constraint stage.

Scripts

scripts/process_documenter.py — Reads a process JSON, validates it, and emits a text-based BPMN-style swim-lane diagram in Markdown (lanes by owner, stages annotated with type + duration). Also outputs a normalized JSON artifact for downstream tools. Stdlib only. --sample prints a 6-stage procurement-intake example.

scripts/bottleneck_detector.py — Applies three deterministic detection rules: (a) stage P50 > 2× mean of value-add stages, (b) wait-state % > 40% of total cycle, (c) rework % > 15%. Thresholds adjust by --profile because SaaS, services, manufacturing, and healthcare have different "normal" wait ratios. Output is a ranked list with severity, hypothesis, action.

scripts/cycle_time_analyzer.py — Computes total P50 and P90 cycle time, value-add ratio (VA%), wait %, rework %, and a Little's-Law throughput estimate (WIP / cycle time). Per Lean canon: VA% > 25% = HEALTHY, 10–25% = TYPICAL (most non-manufacturing processes land here), < 10% = WASTE-HEAVY.

Quick example

bash
# 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

References

  • references/lean_six_sigma_canon.md — TIMWOOD wastes, value-stream mapping, Theory of Constraints, Kanban WIP, Little's Law. Cites Womack & Jones, Rother & Shook, Goldratt, Ohno, Liker, Pyzdek, Anderson.
  • references/bpmn_essentials.md — Pools, lanes, gateways, events, message flows, common notation mistakes. Cites the OMG BPMN 2.0 spec, Silver, Allweyer, Freund/Rücker, OASIS, ISO/IEC 19510:2013.
  • references/bottleneck_anti_patterns.md — Seven specific anti-patterns drawn from Goldratt, Kim et al., Spear, DORA, Deming, and process-mining research.

Assumptions

  1. The user can provide stage-level cycle-time data (even rough P50 / P90 estimates). If they cannot, the first step is to instrument the process — not to map it.
  2. "Process" here means a repeatable business workflow with discrete stages, not a one-off project.
  3. The user has authority to act on bottlenecks (or can route findings to someone who does). Without that, the output is academic.
  4. Stage type is honest: a "value-add" stage labeled as such by the user really does change the work product from the customer's perspective. Mis-labelling waiting as value-add is the most common data-quality failure.
Show full SKILL.md (386 more words)Show less

Anti-patterns

  • Mapping every process at once. Pick one. Goldratt: the constraint is a single point.
  • Optimizing the non-constraint. If stage 4 is the bottleneck, speeding up stage 2 just builds inventory in front of stage 4. Subordinate everything to the constraint.
  • Mistaking total cycle time for processing time. They are almost never the same; VA% reveals the gap.
  • Adding people to a wait-bound process. Wait time is not solved by more headcount; it's solved by removing the handoff or batch.
  • Treating rework as a separate problem. Rework loops belong in the process map. Hiding them understates true cycle time.

Distinct from

  • business-growth skills — external sales motion, lead-funnel conversion, customer-success retention. Process-mapper is internal operations.
  • engineering/slo-architect — system-reliability SLOs / error budgets / burn-rate alerts. Process-mapper is business-process cycle time, not system uptime.
  • c-level-advisor (COO / CEO) — strategic prioritization of which processes to fix. Process-mapper is the tactical instrument used after that prioritization decision.
  • project-management skills — Jira / Confluence ticket workflow tooling. Process-mapper is process design, not ticket tracking.

Forcing-question library (Matt Pocock grill discipline)

Before invoking the tools, the orchestrator (or /cs:grill-bizops) walks the user through these questions one at a time, with a recommended answer + canon citation. Never bundled.

  1. "Do you have measured cycle times for the top-3 longest stages, or only estimates?" Recommended: insist on measured data. Canon: Goldratt 1984 (The Goal) — optimizing estimated bottlenecks reliably attacks the wrong constraint.

  2. "Are you mapping the current process (as-is) or the intended process (to-be)?" Recommended: map as-is first. To-be after bottleneck is identified. Canon: Rother & Shook 1999 (Learning to See) — value-stream mapping starts with the current state, always.

  3. "Where do handoffs occur between teams, and how long does each handoff wait?" Recommended: log every handoff with median wait time. Canon: Reinertsen 2009 (Principles of Product Development Flow) — wait time at handoffs is the largest invisible cost.

  4. "What's your batch size at each stage?" Recommended: drive batch size toward 1 wherever possible. Canon: Anderson 2010 (Kanban) — batch size correlates 1:1 with cycle time variance.

  5. "What's the rework rate per stage?" Recommended: surface it explicitly; rework loops belong in the map. Canon: Pyzdek (Six Sigma Handbook) — hidden rework drives 30-50% of total cycle time in service processes.

Walk depth-first. Don't open question 4 before 1-3 are answered. After all 5 are locked, invoke process_documenter.py → bottleneck_detector.py → cycle_time_analyzer.py in sequence.

© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts, references, assets) in business-operations/skills/process-mapper of alirezarezvani/claude-skills.

  • SKILL.md
  • assets/process_template.md
  • references/bottleneck_anti_patterns.md
  • references/bpmn_essentials.md
  • references/lean_six_sigma_canon.md
  • scripts/bottleneck_detector.py
  • scripts/cycle_time_analyzer.py
  • scripts/process_documenter.py

Open the folder on GitHubat commit 19392f7

Compare with similar skills

Process Mapper next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Process Mapper compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Process Mapper this skillalirezarezvani/claude-skills28k—~2.2kAutomated safety check: PassMIT
Security Commsbriiirussell/cybersecurity-skills412—~3.8kAutomated safety check: PassMIT
Performance Reportindranilbanerjee/digital-marketing-pro8541 repos~1.1kAutomated safety check: PassMIT
Client Reportindranilbanerjee/digital-marketing-pro8541 repos~2.4kAutomated safety check: PassMIT
Operationstravisjneuman/.claude101—~3.4kAutomated safety check: PassMIT
Gtm Board And Investor Communicationgithub/awesome-copilot40k1 repos~4.7kAutomated safety check: PassMIT

Similar skills

  • Security Comms

    briiirussell/cybersecurity-skills

    Translate technical security work into the language of non-security audiences — board, executives, engineering, customer success, customers, legal, procurement, sales.

    412 GitHub stars~3.8k tokensUpdated 4 mo ago
    Business, Finance & HRAuto-check passed
  • Performance Report

    indranilbanerjee/digital-marketing-pro

    Turn marketing data into a stakeholder-ready performance report: executive summary, channel-by-channel KPI dashboard, trend analysis, anomaly alerts with root-cause hypotheses, and recommendations…

    854 GitHub starsUsed in 1 repo~1.1k tokens
    Business, Finance & HRAuto-check passed
  • Client Report

    indranilbanerjee/digital-marketing-pro

    Generate a white-labeled client report in agency voice — weekly pulse, monthly review, or QBR — with a KPI scorecard vs targets and comparison period, channel breakdowns, top wins with attribution…

    854 GitHub starsUsed in 1 repo~2.4k tokens
    Sales & SupportAuto-check passed
  • Operations

    travisjneuman/.claude

    Operations excellence expertise for supply chain optimization, process improvement (Lean, Six Sigma), capacity planning, vendor management, quality assurance, and operational efficiency.

    101 GitHub stars~3.4k tokensUpdated today
    SecurityAuto-check passed
  • Official

    Board meeting preparation, investor updates, and executive communication.

    40k GitHub starsUsed in 1 repo~4.7k tokens
    Business, Finance & HRAuto-check passed
  • Aliyun Arms Query

    cinience/alicloud-skills

    A skill your agent uses when querying distributed traces or application metrics in Alibaba Cloud ARMS (Application Real-Time Monitoring Service).

    397 GitHub stars~1.6k tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed

More from alirezarezvani/claude-skills

All 342 skills in this repo
  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed
  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed
  • App Store Optimization

    alirezarezvani/claude-skills

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.

    28k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed
  • AWS Solution Architect

    alirezarezvani/claude-skills

    Design AWS architectures for startups using serverless patterns and IaC templates.

    28k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Campaign Analytics

    alirezarezvani/claude-skills

    Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • Code to PRD

    alirezarezvani/claude-skills

    Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.

    28k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

Works with

Questions about Process Mapper

What does Process Mapper do?

A skill your agent uses when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff…. Process Mapper is an agent skill from alirezarezvani/claude-skills. 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.

When should I use Process Mapper?

Process Mapper fits situations like: process-improvement owner needs to document an end-to-end business process (procurement; employee onboarding; incident handoff; customer-onboarding.

How do I install Process Mapper in Claude Code?

Run `npx skills add alirezarezvani/claude-skills --skill process-mapper -a claude-code`. Or copy the skill folder (business-operations/skills/process-mapper in alirezarezvani/claude-skills) into .claude/skills/process-mapper in your project. Claude Code loads it when a task matches its description.

How do I install Process Mapper in Codex?

Run `npx skills add alirezarezvani/claude-skills --skill process-mapper -a codex`. Or copy the skill folder (business-operations/skills/process-mapper in alirezarezvani/claude-skills) into .agents/skills/process-mapper in your project. Codex loads it when a task matches its description.

Can I use Process Mapper in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill process-mapper -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/process-mapper, .gemini/skills/process-mapper, .github/skills/process-mapper and .opencode/skills/process-mapper in your project.

What does Process Mapper need to run?

Going by SKILL.md and its folder, Process Mapper needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Process Mapper access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Process Mapper safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Process Mapper use?

Process Mapper is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Process Mapper use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.2k tokens, read only when the agent opens those files.

What are the alternatives to Process Mapper?

Skills that share tags, products or a category with Process Mapper: Security Comms (briiirussell/cybersecurity-skills, 412 stars), Performance Report (indranilbanerjee/digital-marketing-pro, 854 stars), Client Report (indranilbanerjee/digital-marketing-pro, 854 stars) and Operations (travisjneuman/.claude, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Process Mapper?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,788 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.

Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.