What problem does it solve? Deciding whether business logic belongs in a durable workflow or plain typed code is hard, and authoring NocoBase 3 workflow DSL packages without knowing the exact contracts leads to invalid definitions, failed builds, and misdiagnosed runs. This Skill guides the full lifecycle of source-managed workflows so definitions, invocations, and diagnostics follow the actual plugin contracts. ## Core Features & Use Cases - Architecture decisions: Decide whether a business behavior belongs in Workflow, ordinary typed code, or a combination, based on durability, branching, and observability needs. - DSL authoring and validation: Author workflow.ts packages with Condition, Run, and Terminate instructions, input schemas, administrator parameters, and result contracts, then run the five-phase checker and Artifact build. - Invocation and management: Trigger workflows through workflowServiceToken, handle accepted/skipped receipts and event-key deduplication, and use the authenticated management API for enablement, parameters, and manual runs. - Execution diagnostics: Diagnose runs by status model, node attempts, payloads, and logs, and distinguish root causes such as module errors, input validation, or timeout aborts. - Use Case: A developer needs a quotation approval process that branches on a risk score and retains execution history. The Skill helps decide the Workflow/code boundary, author the quotation-decision package with run scripts, validate and build the Artifact, trigger it with an idempotent event key, and diagnose a failed node attempt. ## Quick Start Use the nocobase-app-plugin-workflow skill to decide whether my business process needs a NocoBase workflow and then author and validate the workflow package.
