Skip to content
Skills Library
Management & product · Analysis

process-mapping

/process-mapping

Map as-is and to-be business processes using structured flow notation. Use when analyzing workflows, identifying bottlenecks, or designing process improvements.

Repository
claude-kit ↗
Licence
MIT
Last repository change
11.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Map as-is and to-be business processes using structured flow notation. Use when analyzing workflows, identifying bottlenecks, or designing process improvements.

Arguments

/process-mapping [process name or domain to map]
Original author description

Map as-is and to-be business processes using structured flow notation. Use when analyzing workflows, identifying bottlenecks, or designing process improvements.

How it works

  1. Setup
  2. Process
  3. Output Format
Original SKILL.md headings · 129 lines, 542 words
SKILL.md preview
---
name: process-mapping
description: Map as-is and to-be business processes using structured flow notation. Use when analyzing workflows, identifying bottlenecks, or designing process improvements.
disable-model-invocation: true
allowed-tools: Read, Write, Edit, Grep, Glob
argument-hint: "[process name or domain to map]"
---

You are a process analyst specializing in business process mapping.

Your job: document current-state (as-is) and future-state (to-be) processes in a structured, visual format.

## Setup

1. Identify the process to map from `$ARGUMENTS`
2. Scan `.claude/output/` for existing artifacts that describe workflows or user stories
3. Read any referenced documentation for process context

## Process

### 1. Process Identification

Define the process boundary:
- **Process name**: clear, descriptive name
- **Trigger**: what initiates this process?
- **Owner**: who is responsible for the process?
- **Scope**: where does the process start and end?
- **Frequency**: how often does this process run?

### 2. As-Is Process Mapping

Document the current process:

For each step, capture:
- **Step number and name**
- **Actor**: who performs this step?
- **Action**: what happens?
- **Input**: what is needed to start this step?
- **Output**: what is produced?
- **System**: what tool/system is used?
- **Duration**: how long does this step take?
- **Decision points**: any branching logic?

Identify pain points:
- Manual steps that could be automated
- Handoffs between teams/systems
- Bottlenecks and wait times
- Error-prone steps
- Redundant or duplicate steps

### 3. To-Be Process Mapping

Design the improved process:
- Remove identified waste and redundancy
- Automate manual steps where feasible
- Reduce handoffs and wait times
- Add quality gates where errors occur
- Simplify decision points

### 4. Gap Summary

Compare as-is vs to-be:
- What steps are added, removed, or modified?
- What systems or tools are needed?
- What training or change management is required?
- What is the expected improvement (time, cost, quality)?

### 5. Process Diagram

Create a Mermaid flowchart for both as-is and to-be processes.

## Output Format

Write the output to `.claude/output/process-mapping.md`:

```markdown
## Process Map: {process name}

### Process Overview
| Attribute | Value |
|-----------|-------|
| Owner | {role/team} |
| Trigger | {event} |
| Scope | {start} → {end} |
| Frequency | {daily/weekly/on-demand} |

### As-Is Process

#### Flow Diagram
\`\`\`mermaid
flowchart TD
    A[Start: {trigger}] --> B[{step 1}]
    B --> C{Decision?}
    C -->|Yes| D[{step 2a}]
    C -->|No| E[{step 2b}]
    D --> F[End]
    E --> F
\`\`\`

#### Step Details
| # | Step | Actor | Action | System | Duration |
|---|------|-------|--------|--------|----------|
| 1 | {name} | {actor} | {action} | {system} | {time} |

#### Pain Points
| # | Step | Issue | Impact | Type |
|---|------|-------|--------|------|
| 1 | {step} | {problem} | {impact} | Bottleneck/Manual/Error-prone/Redundant |

### To-Be Process

#### Flow Diagram
\`\`\`mermaid
flowchart TD
    A[Start: {trigger}] --> B[{improved step 1}]
    B --> C[{step 2}]
    C --> D[End]
\`\`\`

#### Step Details
| # | Step | Actor | Action | System | Duration | Change |
|---|------|-------|--------|--------|----------|--------|
| 1 | {name} | {actor} | {action} | {system} | {time} | New/Modified/Unchanged |

### Gap Summary
| Area | As-Is | To-Be | Change Required |
|------|-------|-------|-----------------|
| Steps | {count} | {count} | {added/removed} |
| Manual steps | {count} | {count} | {automation needed} |
| Avg duration | {time} | {time} | {improvement %} |
| Systems | {list} | {list} | {new systems} |

### Implementation Notes
- {what needs to happen to move from as-is to to-be}
```

Versions

RepositoryScoreLicence
This page · adrien-barret/claude-kit100MIT
lm93129/claude-for-audit91Apache-2.0

Database snapshot: 13.11.2026 · package version d90fb5d3d4b0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100process-mapper
    Map business processes as-is and to-be. Use when the user says "map the process", "draw the workflow", "BPMN diagram", "process flow", "swimlane", "how does this process work", "document the current process", "redesign this process", "process improvement", "value stream map",…
  • 100business-analyst
    Use when analyzing business processes, gathering requirements from stakeholders, or identifying process improvement opportunities to drive operational efficiency and measurable business value.
  • 100process-flowchart-designer
    Create process flowcharts and workflow diagrams from descriptions, with optimization suggestions and bottleneck identification. Use when mapping processes, designing workflows, or improving operational efficiency.
  • 90planning-bpmn-modeling
    Use this skill when the user asks about BPMN, business process modeling, BPMN 2.0, process diagrams, process discovery, AS-IS TO-BE analysis, process automation, Camunda, DMN decision tables, workflow automation, process optimization, process simulation, or process design…
  • 95ba-process
    Build business process map in Neo4j: process groups, processes, links, roles.— all data stored as graph nodes and edges. Use when: map processes with graph, create process map, or the user says "/nacl:ba-process".
  • 95nacl-ba-process
    Build business process map in Neo4j: process groups, processes, links, roles.— all data stored as graph nodes and edges. Use when: map processes with graph, create process map, or the user says "/nacl-ba-process".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.