@mmerterden/multi-agent-pipeline weekly downloads statistics

@mmerterden/multi-agent-pipeline

🇹🇷 Türkçe: README.tr.md

A 6-phase AI development pipeline for Claude Code, Copilot CLI and Codex CLI. Drives a Jira issue or GitHub URL to a merged PR in one command - analysis → plan → TDD → review → test → commit → PR - with multi-repo orchestration, a plan-approval gate, CLI-aware parallel review, and store-compliance checks. Component and Figma-to-code work is dispatched to the per-stack marketplace plugins (iOS/SwiftUI, Android/Compose) rather than bundled, so component skills live in one place.

Runs natively on Claude Code, Copilot CLI and Codex CLI. macOS only. Zero runtime dependencies.

📐 Architecture diagrams - the 6-phase flow, operating modes, review/triage, Figma subphases, component layout. Ecosystem diagram - how this repo, the multi-agent-plugins marketplace and multi-agent-toolkit-mcp compose.

Prerequisites

• Node.js >= 20.11 - required; the pipeline's own tooling runs on it.
• jq - required for ten paths, optional for the rest. 96 shell files call it. The ten that publish or decide - the autopilot queue, Jira comments, Jira Issue Links, PR reviews, issue updates, the plan file, both Figma fetchers, log search and Jira auth - refuse with exit 3 rather than run, because a missing jq renders as empty DATA and the work carries on with it. Everywhere else it still degrades. The install prints a note when it is missing.
• gh - for GitHub issue and PR work. Its built-in --jq is independent of the jq binary.

Quick Start

# from the public registry (no auth) - pick the CLIs you actually use
npx @mmerterden/multi-agent-pipeline install --claude    # Claude Code only (default)
npx @mmerterden/multi-agent-pipeline install --copilot   # Copilot CLI only
npx @mmerterden/multi-agent-pipeline install --codex     # Codex CLI only
npx @mmerterden/multi-agent-pipeline install --all       # all three

# then, once:
/multi-agent:setup          # keychain token scan + git identity + default stack

No npx on that machine?

npx ships with npm, and npm ships with Node - so "npx: command not found" almost always means Node is missing from that shell, not that anything is wrong with the package. Check first, then pick the row that matches:

node -v; npm -v; command -v node npm npx

What you see	What to do
nothing at all	Install Node >= 20.11: brew install node, or the LTS installer from nodejs.org
node works, npx does not	npm i -g @mmerterden/multi-agent-pipeline then multi-agent-pipeline install --claude
nvm is installed but the shell does not see it	source ~/.nvm/nvm.sh && nvm use --lts, or just open a new terminal
npm is ancient (< 5.2, which predates npx)	npm i -g npm@latest, or use the global-install row above

And the path that needs neither npx nor a global install - clone and run the installer directly:

git clone https://github.com/mmerterden/multi-agent-pipeline.git
cd multi-agent-pipeline
node index.js install --claude        # add --dry-run first to see what it would write

npm exec @mmerterden/multi-agent-pipeline install --claude also works on any npm 7+ without npx on PATH.

One error that is not an npx problem. This package declares os: ["darwin"], so npm refuses to install it anywhere else and says npm ERR! notsup Unsupported platform. That is deliberate (ADR-0012), not a missing tool: every credential read shells security, every iOS build xcodebuild, every piece of visual evidence simctl.

Tool flags combine (--claude --codex). With no tool flag at all, the installer targets Claude Code only. Other flags: --dry-run (show what would be written, write nothing), --platform=ios|android|all (skip the stack skills you do not need), --link (symlink instead of copy, for local development).

Run a task - the input type is auto-detected:

/multi-agent "PROJ-1234"                              # Jira id → fetch, plan, build
/multi-agent "https://github.com/org/repo/issues/42"  # GitHub issue URL
/multi-agent "my-app#42"                              # repo + issue number
/multi-agent "fix dark-mode contrast on LoginView"    # free-text bug/feature
/multi-agent:jira                                     # browse your open Jira issues → pick
/multi-agent:issue                                    # browse unassigned GitHub issues → pick

Every input runs the same short intake - account → (repo) → maturity check → dev-context - then enters Phase 0. A Jira id or GitHub URL is fetched and maturity-checked before any code is written; free-text skips the fetch and goes straight to planning. Multi-repo tasks add extra repos at the dev-context step.…