- Home
- Skills
- Business & Operations
- approval deadlock cycle time simulator
approval deadlock cycle time simulator
Simulates cycle-time risks and deadlock exposure in approval workflows using the Lübke pattern taxonomy.
$11
Works with the AI Agents you already use
approval deadlock cycle time simulator
Example session with this skill installed
Review this chain: 3-step sequential approval (Manager, VP, Finance) for capital expenditure over $50k. Requires unanimous consent. No timeouts or delegation rules. Stakes: High financial risk.
- Read your context and instructions
- Compiled the approval deadlock cycle
VERDICT (2-3 lines): CRITICAL EXPOSURE · Deadlock risk due to lack of non-performance handling · Add 'Silence as Rejection' or 'Replacement Approver' to prevent permanent process stalls.
A.C.E.S. EXPOSURE MATRIX
| Metric | Score | Finding |
|---|---|---|
| Availability Exposure | [■■■■□] HIGH | 3 distinct roles, no replacement/delegation rules stated. |
| Cycle-Time Exposure | [■■■■■] CRITICAL | Sequential + Unanimous = maximum cumulative delay. |
| Deadlock Exposure | [■■■■■] CRITICAL | No timeout or non-performance pattern; one absence kills the process. |
| Escalation Fit | [■■■□□] MODERATE | Sequential logic matches high-risk profile but lacks safety valves. |
FINDINGS
Sequential Delay (Force: Cycle-Time): Per Lübke (2023), sequential execution with unanimous aggregation creates the worst-case cycle time. The process is bound by the sum of all individual latencies.
Single Point of Failure (Force: Available Resources): Each step is a hard gate. Without a Replacement Approver or Silence as Rejection pattern, an approver's absence (vacation/illness) results in a permanent stall.
Resource Intensity: High-risk profiles justify the Unanimous Decision pattern, but the lack of Parallel Approval means resources are tied up longer than necessary for the quality gain.
RECOMMENDED MINIMAL CHANGE
Implement Silence as Rejection with a 48-hour timeout for the Manager and VP steps.
Trade-off: This caps the cycle time and prevents deadlocks, accepting a higher false-rejection rate which is consistent with your
High Financial Risk profile.
Next steps
- Define specific timeout durations for each of the three steps.
- Identify backup delegates for the 'Finance' role to ensure availability.
- Verify if your BPMN engine (e.g., Camunda) supports boundary timer events for these steps.
SOURCE: Forces and Consequences: Daniel Lübke, "Design Patterns for Approval Processes" (EuroPLoP 2023/2024).
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Process designers often build approval workflows that look sound on paper but fail in production due to hidden deadlocks, vacation bottlenecks, or sequential delays. Choosing the wrong aggregation rule or missing a non-performance pattern can stall critical business operations without warning.
What it does
- Evaluates approval chain configurations for Availability, Cycle-time, Escalation, and Stall (A.C.E.S.) risks.
- Identifies deadlock triggers, such as named individuals assigned without replacement rules or timeouts.
- Maps proposed logic against 25 academic approval patterns to find the safest trade-off between speed and risk.
- Flags mismatches between the stakes of the approval and the chosen escalation behavior (e.g., Silence-as-Approval).
Frameworks & tools
BPMN engines, Power Automate, ProcessMaker, Camunda, and Flowable.
Why this beats prompting it yourself
General-purpose LLMs lack the specific taxonomy of the Lübke approval patterns and often default to "safe" but slow sequential advice. This skill applies rigorous constraints from documented research to catch high-severity stall conditions that typical prompts overlook.
Use cases
- Reviewing procurement workflows for hidden bottlenecks before deployment.
- Validating financial approval chains against risk-based stakes profiles.
- Optimizing existing sequential processes for faster cycle times without increasing risk.
- Drafting deadlock-proof escalation policies for role-based approvals.
Known limitations
Requires specific configuration details (number of steps, aggregation rules) for accurate scoring. Does not model historical response times or actual load data.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.
Requires specific configuration details like step count and aggregation rules for scoring. Does not model historical data or engine-specific latency.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Permissions
No special permissions declared or detected