pipeline-coordinator-reference

What problem does it solve?

This Skill eliminates silent failures and context drift that occur when chaining multiple specialized agents in sequential workflows, where each stage depends on the output of the previous stage. Without explicit data contracts between stages, agents often receive stale context, incorrect file paths, or missing fields, leading to hard-to-debug errors.

Core Features & Use Cases

• Explicit Data Contract Enforcement: Defines machine-readable schemas for handoffs between pipeline stages to ensure all required data is present and correctly formatted before advancing.
• Concrete Pipeline Example: Uses a four-stage test-coverage pipeline (explore, gap analysis, test writing, summary) to demonstrate the coordinator pattern in a real-world scenario.
• Use Case: Ideal for teams building sequential multi-agent workflows like automated test generation, code quality analysis, or document processing pipelines where each step builds directly on the prior stage's output.

Quick Start

Use the pipeline-coordinator-reference skill to build a sequential agent pipeline for your test coverage workflow with strict data contracts between each stage.