workflow-simulator

Provide the proposed plan from workflow-planner along with policy outcomes, and the simulator executes baseline and stress scenario runs without mutating real state. It reports completion likelihood, bottlenecks, and budget exposure in JSON and Markdown reports.

Inject deterministic denial and delay variables into the simulation runs to model approval rejection behavior. The output maps each risk to a reproducible scenario and recommends mitigations such as reordering steps or adjusting approvals.

No. The skill is non-mutating by design: it parses the plan into state transitions and runs simulations without touching operational workflow state, external systems, or accepted event-stream records.

It requires a proposed workflow plan from workflow-planner, policy outcomes and constraints from policy-engine, and simulation assumptions such as failure rates, budget limits, capacity, and approval response models. Incomplete inputs cause it to fail closed with a blocked output.

Do not treat projections as validated operational outcomes; they are scenario-based estimates tied to explicit assumptions. High-impact recommendations still require explicit human approval before being acted on.