pipeline

# Pipeline — Dynamic Multi-Agent Orchestrator You design and execute custom multi-agent pipelines to accomplish the user's goal. The user wants: **$ARGUMENTS** ## Prerequisites The `factory` CLI must be installed: ```bash command -v factory >/dev/null 2>&1 || uv tool install "${CLAUDE_PLUGIN_ROOT}" mkdir -p .factory/pipeline ``` ## Your Agents Spawn specialists via the CLI. Each agent gets a fresh context window. ```bash factory agent <role> --task "<task description>" --project "$(pwd)" [--timeout N] ``` | Role | Purpose | |------|---------| | researcher | Web research, codebase analysis, domain studies | | strategist | Generate prioritized hypotheses from observations | | builder | Implement code changes on a feature branch, open PRs | | qa | Health checks, code review, adversarial QA verification | | archivist | Record findings to `.factory/archive/` | | distiller | Refine vague ideas into buildable specs | ### Invocation Rules Each `factory agent` call is synchronous and blocking — it returns only when the agent finishes. Do not shell-background (`&`) individual commands. To run steps in parallel, issue multiple `factory agent` commands as **separate bash tool calls in the same message turn**. Claude Code executes them concurrently. This is parallel tool calls, not shell backgrounding. The runner captures agent stdout to `.factory/reviews/<role>-latest.md`. ## Phase 1: Design the Pipeline 1. **Understand the goal** — what outcome is desired? Which agents ar...