| name | pipeline |
| description | Execute sequential, stage-based assembly line tasks where the output of one stage becomes the input of the next stage. Useful for progressive refinement workflows like Research -> Draft -> Review -> Format. Not for parallel execution (use divide-conquer) or consensus (use consensus-delegation). Triggers: "파이프라인", "순차 처리", "단계별 처리", "pipeline", "sequential processing".
|
Pipeline
The Pipeline pattern organizes tasks into sequential stages, where the output (artifact) of a preceding stage serves as the input instruction/context for the next stage.
5-Stage Workflow
Input ──► [ Stage A ] ──► (Artifacts) ──► [ Stage B ] ──► (Artifacts) ──► Output
Worker A Worker B
- Definition: Outline the stages, assign specific assistant configurations, and define the handover criteria.
- Setup: Provide a shared directory path via
workspaceOverride so all stages modify the same project directory.
- Execution:
- Spawn the first stage:
agent__startSession(..., waitForResult=true).
- Collect the output path and stage summary upon completion.
- Handover: Bind the output paths and preceding summaries into the task prompt of the next stage session.
- Final Format: Aggregate the final stage's output and present it to the user.
🛠️ MCP Tools Guide
- Sequential Spawns: Use
agent__startSession with waitForResult=true or use agent__checkSession(sessionId, wait=true) to synchronize.
- Context Filtering: Avoid passing the entire conversation logs of previous stages to prevent context bloat. Only pass the summarized markdown text and file paths.
See pipeline-specs.md for details.
References
