workflow bottleneck finder

    1

    Diagnose operational constraints, map lead times, and prioritize workflow interventions using constraints-based logic.

    $5

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    workflow bottleneck finder

    Example session with this skill installed

    Map the 'Software Bug Fix' workflow. Symptoms: developers say they're waiting on specs, but QA is backed up. Steps: Triage, Dev, PR Review, QA, Deploy. PRs take 2 days, QA takes 3 days.

    • Read your context and instructions
    • Compiled the workflow bottleneck finder
    • Generated the document

    I have analyzed the 'Software Bug Fix' workflow. While QA has the longest active time, the primary controlling bottleneck is the PR Review step due to a high queue-to-active ratio and downstream impact on QA readiness.

    Workflow Bottleneck Analysis

    Step IDNameOwnerInput RequiredQueue WaitActive TimeLead TimeRework %
    S1TriagePMBug Report4h30m4.5h5%
    S2DevEngineerSpecs2h6h8h15%
    S3PR ReviewSenior EngPR Link48h [EST]1h49h20%
    S4QATesterBuild12h24h36h10%
    S5DeployDevOpsApproved Build1h30m1.5h2%

    Bottleneck Identification

    Primary Constraint: S3 (PR Review). Lead time is 49 hours. The queue-to-active ratio is 48:1. This is a scheduling bottleneck where work sits idle, causing "starvation" for the QA team who then receive items in large, unmanageable batches.
    2.

    Secondary Constraint: S4 (QA). Lead time is 36 hours. While the active time is high, the delay is exacerbated by S3's batching behavior.
    3.

    Hidden Rework: S2 (Dev). The 20% rework rate coming out of S3 suggests that 'waiting on specs' (S1 output) is causing poor initial code quality.

    Intervention Priority List

    InterventionImpactEffortRiskTotal ScorePriority
    Implement 'Review Buddies' (S3)5524.6High
    Standardize Spec Template (S1)4414.1High
    Automated Regression Suite (S4)5233.4Medium

    Action Plan: S3 Lead Time Reduction

    • Owner: Engineering Manager
    • Measure: PR Cycle Time (Lagging), Daily Review Count (Leading)
    • Baseline: 49 hours
    • Target: 12 hours (within 4 weeks)

    Validation Test: Compare S4 queue stability. If S3 lead time drops but S4 queue spikes, the bottleneck has successfully shifted to capacity.

    Next steps

    1. Validate the 48-hour PR wait time with actual GitHub metadata.
    2. Assign 'Review Buddies' to distribute the PR load away from Senior Engineers.
    3. Review the Triage spec template to reduce S2 rework.

    workflow-bottleneck-finder.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Pinpoint the specific step controlling total process lead time.Calculate queue-to-active work ratios to identify idle time.Rank process improvements by weighted impact and implementation effort.Design validation tests to confirm if a bottleneck has actually moved.

    About this skill

    The problem

    Operational delays and high rework rates are often treated by fixing symptoms rather than the actual constraint. Developers and managers frequently optimize individual steps without realizing they are just moving the bottleneck elsewhere in the system.

    What it does

    • Maps end-to-end workflows including queues, active work time, handoffs, and approval gates.
    • Identifies the controlling constraint by calculating lead times and queue-to-active work ratios.
    • Distinguishes between superficial symptoms and root causes, tracing issues upstream to missing inputs.
    • Scores interventions using a weighted priority matrix based on impact, effort, and implementation risk.
    • Generates actionable improvement plans with owners, KPIs, and validation tests to ensure the bottleneck actually shifts.

    Why this beats prompting it yourself

    Generic prompts often miss the nuances of queue theory and rework loops, leading to shallow "work harder" advice. This skill applies specific constraints-based logic to differentiate between scheduling issues and capacity limits, ensuring you don't waste resources optimizing the wrong step.

    Use cases

    • Diagnosing delays in software release cycles or CI/CD pipelines.
    • Identifying friction points in client onboarding or support ticketing flows.
    • Optimizing manufacturing or order fulfillment processes with high rework rates.
    • Audit-ready mapping of complex approval workflows and cross-departmental handoffs.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 10 days ago

    • Passed all security checks, Safe to install

    Listed10 days ago

    What's inside

    Frequently Asked Questions