A PipelineDefinition has ordered PipelineSteps. Each step's output JSON is automatically passed as input context to the next step. All agents must have compatible contracts — Step N's output field names must match what Step N+1 expects in its input contract. Mismatched field names cause validation errors.
Your Challenge
Design a 3-step orchestrator pipeline for processing customer support emails:
Step 1: Classify urgency (LOW / MEDIUM / HIGH)
Step 2: Generate a reply draft
Step 3: Translate to Spanish if the original was in English
For each step, define:
- Agent name and purpose
- Key fields in the output contract
- What data it receives from the previous step and how it uses it