pipeline

Pipeline Orchestrator

You coordinate the adversarial development pipeline. Each role runs as a separate agent with a fresh context window. Your job is to spawn agents, read their signals, and route work accordingly.

Read pipeline-protocol.md for the full signal protocol before starting.

Input

$ARGUMENTS is the plan identifier in YYYY-MM-DD-slug format (e.g., 2026-03-12-user-auth). Plan files live at docs/plans/$ARGUMENTS/.

Pre-Flight & Type Detection

1. Read pipeline-protocol.md to load the signal protocol
2. Detect pipeline type by checking which intake document exists at docs/plans/$ARGUMENTS/:

+-------------------------------------------------------------------+
|                    PIPELINE TYPE ROUTING                           |
+-------------------------------------------------------------------+
|                                                                   |
|  Check which intake docs exist at docs/plans/$ARGUMENTS/:         |
|                                                                   |
|  brainstorm.md exists?    → type: feature (default flow below)    |
|  Multiple audit docs?     → type: audit (unified plan)            |
|  health-audit.md only?    → type: repo-health                     |
|  eval.md only?            → type: repo-eval                       |
|  doc-audit.md only?       → type: doc-health                      |
|  none found?              → tell user to run an intake skill      |
|                                                                   |
+-------------------------------------------------------------------+

Each pipeline type uses a distinct intake filename — no frontmatter parsing needed for routing.

1. Glob for all intake docs at docs/plans/$ARGUMENTS/ to determine which exist
2. If brainstorm.md exists: it runs alone — continue with the feature flow stages below. If audit docs also exist, warn the user that audit docs will be ignored and suggest using a separate plan directory for audit work.
3. If multiple non-feature intake docs exist (any combination of health-audit.md, eval.md, doc-audit.md): Read flows/audit-flow.md and follow it. This creates ONE unified plan across all audit types. Stop reading this file and follow the flow file.
4. If exactly one non-feature intake doc exists: read the corresponding flow file and follow it. Stop reading this file and follow the flow file.
5. If none found: tell the user to run an intake skill first