ECC 2.2 installs an engineering process into AI agents: one setup brings planning, testing, review and memory along
Synopsis
ECC 2.2 packages an engineering process as an installable plugin so an AI agent plans before it builds, verifies changes with tests, reviews its own work from a fresh context, and turns repeated wins into reusable skills and workflows. Previously that process had to be rebuilt in every prompt; installed once, it becomes part of how the agent works. The project is MIT-licensed open source, works best with Claude Code today, has native Codex and Qoder plugin paths, and provides capability-limited adapters for Cursor, OpenCode, Gemini and other harnesses.
Interpretation
ECC chains planning, testing, implementation, review, verification, memory and improvement into a fixed engineering process that serves as the default way an AI agent writes code, instead of asking users to restate that process in every prompt. Previously such a process had to be rebuilt in each prompt, and the agent itself only wrote code, with planning, verification and review not built into how it worked. The project describes its process as plan -> test -> implement -> review -> verify -> remember -> improve and states that installing it once makes it part of how the agent works.
The process ships as a plugin, and after installation the agent gains a set of specialized agents, skills and commands covering planning, review, build repair, security, architecture and domain work. The available resources include 72 agents, 327 skills and 98 legacy command shims, plus hooks, rules, memory, continuous learning and AgentShield security scanning. Installation runs through the guided installer npx ecc-universal@2.2.3 setup; the universal package requires Node.js 18 or newer, and Claude plugin setup also requires Git and Claude Code 2.1 or newer on PATH.
Support across harnesses is not equal, and the project separates native plugin paths from capability-limited adapters according to a support status matrix. It works best with Claude Code today, Codex and Qoder have native plugin paths, while Cursor, OpenCode, Gemini, Zed, GitHub Copilot, Antigravity, Qwen and others connect through capability-limited adapters. The project explicitly asks readers to check the support status matrix before assuming feature parity, and states that a single maintainer ships weekly across 7 harnesses.
Perspective
The demonstrated scope is the installation and usage instructions for ECC 2.2: the guided installer covers Claude Code, Codex and Kimi Code, the universal package requires Node.js 18 or newer, and Claude plugin setup also requires Git and Claude Code 2.1 or newer. The project advises checking the support status matrix before assuming feature parity.
The project states that a single maintainer ships weekly across 7 harnesses and warns that harnesses may not have feature parity. It also notes that a version pin is not a security audit or an integrity check, and that release source and registry integrity should be reviewed before running package code. The material is the project's own account and gives no quantitative evaluation.
