Skip to content

feat(zcode-pipeline): add multi-agent development conveyor plugin - #158

Closed
milinsky wants to merge 2 commits into
zai-org:mainfrom
milinsky:feat/zcode-pipeline
Closed

milinsky wants to merge 2 commits into
zai-org:mainfrom
milinsky:feat/zcode-pipeline

Conversation

@milinsky

@milinsky milinsky commented Nov 3, 2026 •

Copy link
Copy Markdown

Plugin type

  • UI Plugin — provides MCP Apps interactive pages
  • Standard plugin — no MCP Apps interactive pages
  • Not applicable — repository-level changes only

Affected manifest name: zcode-pipeline

What user problem does this solve

LLM coding agents guess requirements, skip steps, claim tests pass without running them, and forget everything between sessions. This plugin turns development into a conveyor of 13 specialized subagents where every stage is gated by the previous one's artifact, every claim must be proven by actual runs, and every accepted epic feeds a permanent project knowledge base.

What it does

Three named flow profiles:

Profile Path When
full Briefer → Architect → Tech Lead → Tech Writer → Developer → Security/Goal/Code Reviews (cycles to full approval) → QA → Manager (ACCEPTED/REJECTED) → Summarizer → commit features, refactors, anything touching contracts
fast-track Briefer → Developer → Code Review (+ Security on risk triggers) → commit small reversible edits (1–2 files, no new contracts)
analysis Briefer → parallel expert audits (architecture / security / code quality / feasibility) → Analyst (verified synthesis) → bridge to development audits, feature feasibility, risk assessment — no code changes

Key features:

  • Living knowledge base (): per-component wiki + epic chronicles, updated after every accepted epic
  • Project initialization (): detects stack, pulls current best practices into , generates project
  • Self-testing (): 13 agent-contract regression probes on a sandbox fixture
  • Epic budgets: token spend tracked, warn at 70%, stop-and-ask at 100%
  • Multi-epic: per-epic state files + queue, stage-boundary switching
  • Analysis → development bridge: analyst saves a ready draft-brief for conveyor-ready findings

Visible behavior and testing

  • Self-test: 13/13 probes PASS (validated on both Russian and English prompts)
  • Battle-tested on two real epics: a greenfield CLI project (6 tasks, 98 tests) and a local web GUI (3 tasks, +59 tests), including escalations, review cycles, and a caught browser-breaking BLOCKER
  • Paired RU-EN translation review: 14 CLEAN / 5 MINOR / 0 CRITICAL

Version and marketplace registration

  • Version: 2.3.2 (manifest and marketplace entry are identical)
  • Category: developer-tools
  • Registered in root marketplace.json

Dependencies, side effects, and licensing

  • No external dependencies — pure stdlib Python, no MCP servers, no network requirements
  • Side effects: writes to directory in the user's project (briefs, tasks, reviews, QA reports, knowledge base); SessionStart hook reads state files (read-only reminder)
  • Network access: initializer agent may use WebSearch/WebFetch for best-practice guides (optional, user-initiated via /init-project)
  • License: GPL-3.0-or-later
  • Third-party code: none

README languages

  • README.md — English (full)
  • README_CN.md — Chinese (full)
  • Source repository: milinsky/zcode-pipeline with additional Russian README

@panda920

panda920 commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator

✅ Internal validation passed. A ZCode maintainer will review the change next; after acceptance, release checks run separately and this PR is closed automatically.

…oji ban

v2.3.0: no-comments rule tightened (docstring bloat banned, linter
suppression banned with examples)
v2.3.1: comment recommendation flow (developer proposes, reviewer decides)
v2.3.2: universal rule zai-org#5 — no emoji anywhere (code, docs, commits)
@milinsky
milinsky force-pushed the feat/zcode-pipeline branch from 90aedfb to 1ad048b Compare November 3, 2026 23:57
@panda920

panda920 commented Nov 4, 2026

Copy link
Copy Markdown
Collaborator

✅ Internal validation passed. A ZCode maintainer will review the change next; after acceptance, release checks run separately and this PR is closed automatically.

@milinsky milinsky closed this Nov 7, 2026
@milinsky
milinsky deleted the feat/zcode-pipeline branch November 7, 2026 06:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants