borghei/Claude-Skills / business-operations/process-mapper
process-mapper
VerifiedMap, measure and improve business processes — SIPOC and swimlane capture, cycle-time and bottleneck analysis, handoff diagnosis, and a payback-ranked improvement backlog. Use when a process is slow, error-prone, or crosses too many teams.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.0 KB |
| assets/process-map-template.md | markdown | 3.4 KB |
| assets/sample_opportunities.json | config | 3.5 KB |
| assets/sample_process.json | config | 3.5 KB |
| references/lean-process-analysis.md | markdown | 11.3 KB |
| references/process-capture-methods.md | markdown | 9.5 KB |
| scripts/handoff_analyzer.py | script | 11.3 KB |
| scripts/improvement_scorer.py | script | 11.2 KB |
| scripts/process_analyzer.py | script | 12.1 KB |
assets/process-map-template.md
View on GitHub# Process Map — [Process Name]
**Owner:** [name] · **Mapped:** [date] · **Variant:** [e.g. standard terms, existing customer]
**Volume:** [X] units/month · **Coverage:** this variant is [X]% of total volume
> Steps marked (est) were estimated, not measured. Assumptions listed in section 7.
---
## 1. SIPOC
| Suppliers | Inputs | Process | Outputs | Customers |
|-----------|--------|---------|---------|-----------|
| | | 1. | | |
| | | 2. | | |
| | | 3. | | |
| | | 4. | | |
| | | 5. | | |
**Trigger:** [event that starts the process]
**Terminal:** [state that ends it]
**Out of scope:** [explicitly excluded, so it stays excluded]
---
## 2. Swimlane
```
Owner A | [s1]───┐ ┌──[s6]
| │ │
Owner B | └──[s2]──[s3]────────────┘
| ╎ 22% rework
Owner C | └╌╌╌╌╌╌> back to s1
```
Draw one lane per owner, left to right in time order. Annotate each box with
`touch / wait` minutes. Dashed arrows are rework loops labelled with their rate.
Keep it to one page.
---
## 3. Step detail
| # | Step | Owner | Type | Touch (min) | Wait (min) | Rework | Returns to | System |
|---|------|-------|------|-------------|-----------|--------|-----------|--------|
| s1 | | | V/B/N | | | | | |
| s2 | | | | | | | | |
| s3 | | | | | | | | |
Type: **V** value-added · **B** business-value-added · **N** non-value-added
---
## 4. Flow metrics
Generated by `process_analyzer.py`.
| Metric | Value | Benchmark |
|--------|-------|-----------|
| Lead time | | |
| Touch time | | |
| Wait time | | |
| Process cycle efficiency | | 5-15% typical, 15-25% good for cross-team |
| Value-added ratio | | |
| First-pass yield | | Below 85% means fix quality first |
| Expected rework per unit | | |
**Constraint:** [step] — [X]% of lead time, of which [X] min is wait.
---
## 5. Handoffs
Generated by `handoff_analyzer.py`.
| From -> To | Wait (min) | System switch | Risk | Why |
|-----------|-----------|---------------|------|-----|
| | | | HIGH/MED/LOW | |
**Handoff density:** [X] per step (above 0.5 = fragmented)
**Share of wait at handoffs:** [X]% (above 60% = fix between teams, not inside them)
**Rework loops:**
| Detected at | Returns to | Rate | Steps replayed | Crosses teams | Cost/unit |
|------------|-----------|------|----------------|---------------|-----------|
| | | | | | |
---
## 6. Improvement backlog
Generated by `improvement_scorer.py`.
| Tier | Opportunity | Verb | Annual saving | Lead-time saved | Effort | Payback | Owner |
|------|------------|------|---------------|-----------------|--------|---------|-------|
| NOW | | eliminate | | | | | |
| NEXT | | | | | | | |
| LATER | | | | | | | |
**Labour saving (costed):** [X]/year
**Lead-time reduction (not costed):** [X] min per unit — value per [business owner]: [their figure, or "not quantified"]
---
## 7. Assumptions and gaps
1. [Steps estimated rather than measured, and why]
2. [Exception paths excluded, with frequency]
3. [Data period used]
4. [What would change the conclusion if wrong]
---
## 8. Validation
- [ ] Map read back to the people who do the work
- [ ] Modelled lead time within 20% of measured end-to-end lead time
- [ ] Exception paths captured with frequencies
- [ ] Invisible steps checked (chase emails, status meetings, reconciliation)
- [ ] Batching checked at every step ("as it arrives, or on a schedule?")
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |