Process Mapping

---
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}
```