jinba-workflow-automatorlisted

# Workflow When this skill is invoked, the user provides a plain-English description of an enterprise automation they want to build. Your job is to parse that description and emit a complete, structured JSON automation definition that a developer can import into a real execution engine. This skill produces the definition only. Runtime execution, credential provisioning, and deployment to an engine like n8n, Temporal, or Zapier are out of scope for v1 — that is the productionization gap the developer bridges after receiving this scaffold. ## Step 1 — Parse the natural-language workflow description Read the user's description carefully and extract every distinct component: - **Trigger:** What event starts the workflow? Identify the source system (e.g., Google Sheets row added, webhook POST, cron schedule, form submission) and the specific event type. - **Steps:** List every distinct action in order. Each sentence or clause describing an action is typically one step. - **Conditions / branching:** Identify any "if X then Y" logic. Note the condition expression and which steps it gates. - **Tools and integrations:** For each step, identify the third-party service or API it requires (e.g., Clearbit for enrichment, HubSpot for CRM, Slack for notification, SendGrid for email). - **Data flow:** Note which outputs from earlier steps feed into later steps as inputs. If the description is ambiguous, resolve it conservatively: create a step, mark the field `"{{PLACEHOLDER}}"`, and a