What problem does it solve? Writing Windmill Workflow-as-Code (WAC) scripts requires following strict checkpoint/replay rules, correct SDK naming, and the right CLI commands for previewing versus deploying, and mistakes cause broken suspension or non-deterministic replays. ## Core Features & Use Cases - WAC Authoring Rules: Enforces correct file shape, SDK imports, and naming for Bun TypeScript (windmill-client) and Python (wmill) workflow scripts. - Checkpoint/Replay Guidance: Ensures side effects, API calls, and non-deterministic values are wrapped in task() or step() so workflow replays stay deterministic. - CLI Workflow Discipline: Distinguishes wmill script preview for local iteration from wmill script run and wmill sync push for deployed versions. - Use Case: A developer asks to build a workflow that enriches customer data, waits for manager approval, then notifies a channel; the Skill produces a deterministic @workflow script with taskScript calls, getResumeUrls inside step(), and waitForApproval, then previews it locally. ## Quick Start Write a Windmill workflow-as-code script in Python that processes a list of items in parallel with a concurrency limit and then waits for an approval before finishing.