bpa-map

Documents As-Is business processes using swimlane diagrams and BPMN notation.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/NestorMonroy/thyrox --skill bpa-map-nestormonroy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bpa-map
Source: https://github.com/NestorMonroy/thyrox/tree/main/.claude/skills/bpa-map
Command: npx skills add https://github.com/NestorMonroy/thyrox --skill bpa-map-nestormonroy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Teams often hold conflicting mental models of how a process actually works, and redesigning without a validated current-state map makes improvement impossible to measure. This Skill guides the Map phase of Business Process Analysis (BPA), producing a validated As-Is Process Map with actors, steps, decisions, times, and handoffs. ## Core Features & Use Cases - Structured mapping sessions: Provides a timeboxed agenda, participant roles (Process Owner, executors, facilitator), and swimlane rules (maximum 6-7 lanes) for documenting the real process flow. - BPMN notation guidance: Includes a reference guide covering events, tasks, gateways, pools/lanes, and sequence flows, plus common patterns and errors to avoid. - Ready-to-use template: Ships an As-Is Process Map template capturing steps, inputs, outputs, times, variants, workarounds, and validation sign-off. - Use Case: A credit approval team disagrees on how applications flow between sales, analysts, and the committee. Run this Skill to facilitate a mapping session, document the happy path plus exceptions with time data, and get the map validated by the Process Owner before analysis. ## Quick Start Ask the assistant to run the bpa-map step to document the As-Is map of your selected process with swimlanes, times, and exceptions.

Frequently Asked Questions about bpa-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an As-Is process map with swimlanes?▼

Run a 2-3 hour mapping session with the Process Owner and 2-4 executors. Define one swimlane per actor (maximum 6-7), map the happy path left to right using verb-plus-object task names, then add variants, exceptions, and time data per step.

What BPMN elements are needed for process mapping?▼

A descriptive map needs start and end events (circles), tasks (rectangles named with verb plus object), exclusive gateways (diamonds with labeled Yes/No exits), and lanes per actor. Every gateway must have all outgoing flows labeled with their condition.

When should I not create an As-Is process map?▼

Skip mapping if a validated map less than 6 months old already exists, if the process is entirely new (go straight to To-Be design), or if the scope exceeds 40 steps, in which case split it into subprocesses first.

Why must a process map include time data?▼

Without task time, wait time, and total cycle time per step, the later analysis phase cannot calculate how much of the cycle is value-added versus non-value-added work. Ranges like 2-8 hours are acceptable when exact figures are unavailable.

How do I validate a process map with stakeholders?▼

Share the draft with process executors and ask what they do that is missing and what appears but is not done that way. Correct inconsistencies, then obtain written confirmation from the Process Owner before moving to analysis.

What are common mistakes in BPMN process diagrams?▼

Frequent errors include gateways with unlabeled exits, tasks without verbs, unnamed lanes, multiple start events, missing end events, and undocumented workarounds. Each decision diamond needs at least two labeled outgoing paths.