Business Process Modeling

Skill Name: process-modeling

Background & Use Cases

Requirements documents are text, but the essence of business processes is "who does what, when, what happens next, and which branch to take under what conditions." When requirements involve multiple roles, multiple steps, and various exception paths, pure text descriptions struggle to reveal gaps and blind spots in the process. This skill transforms requirements and rules into visual flowcharts, allowing the team to see the complete business path at a glance.

Input & Output

You need to provide: Scenario descriptions from a confirmed requirements specification (who participates, basic flows, exception flows, key rules).

You will receive: Four diagrams/tables per scenario: swimlane diagram (how roles collaborate), state machine diagram (how object states transition), sequence diagram (the order of interactions between roles), and decision table (which branch under what conditions).

Process Overview

Using the scenario descriptions from the requirements specification, the Agent produces four diagrams for each scenario: first a swimlane diagram to clarify how roles collaborate, then a state machine diagram to depict object state changes, then a sequence diagram to show interaction order, and finally a decision table listing all branch conditions. Each diagram is confirmed by you before proceeding to the next scenario.

flowchart TD s0["Process Hierarchy & Overview"] s1["Single Scenario Swimlane"] s2["Single Scenario State Machine"] s3["Single Scenario Sequence"] s4["Single Scenario Decision Table"] s5["Single Scenario Consistency Check & Close-Out"] s6["scene"] s7["Exception Path Integration"] s8["Cross-Flow Chain Validation"] s9["Document Integration & Full Review"] s0 --> s1 s1 --> s2 s2 --> s3 s3 --> s4 s4 --> s5 s5 --> s6 s6 --> s7 s7 --> s8 s8 --> s9