ECC v2.0.0-rc.1 合作伙伴、赞助者与演讲包¶

ECC gives teams one reusable layer for skills, hooks, rules, MCP conventions,
release gates, and operator workflows across Claude Code, Codex, OpenCode,
Cursor, Gemini, Zed, GitHub Copilot, and terminal-only workflows.

ECC 2.0 sponsor slot for cross-harness agent workflows

Hey [name],

I am getting ECC v2.0.0-rc.1 ready for release review.

The project is now positioned around one reusable operator layer for agentic
work across Claude Code, Codex, OpenCode, Cursor, Gemini, Zed, GitHub Copilot,
and terminal workflows.

The sponsor fit is pretty direct: ECC reaches the exact builders who are
standardizing their AI coding stack, security posture, and workflow automation.

The current public sponsor ladder is:

- Pilot Partner: $200/mo
- Business Sponsor: $500/mo
- Strategic Partner: $1,000+/mo

Business sponsors get logo placement and release visibility. Strategic partners
can turn it into a deeper integration or launch motion.

Repo: https://github.com/affaan-m/ECC
Sponsor: https://github.com/sponsors/affaan-m
Release notes: https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/release-notes.md

If useful, I can send the short sponsor packet and a proposed first 30-day plan.

Affaan

ECC 2.0 is getting close to rc.1.

The release is centered on cross-harness agent workflows: reusable skills,
hooks, rules, MCP conventions, release gates, and an optional Hermes operator
shell.

The partner angle is not "another prompt pack." It is a tested operating layer
for teams using more than one AI coding harness.

I think there is a real integration or co-launch angle here if your team wants
better setup, policy, security, or workflow portability for agent users.

Repo: https://github.com/affaan-m/ECC

I am open to a small number of ECC 2.0 implementation sprints for teams that
are standardizing AI coding workflows.

The useful scope is usually:

1. audit the current harness setup;
2. turn repeated workflows into ECC skills, hooks, and rules;
3. add release, security, and CI gates;
4. create a team operating loop that works across Claude Code, Codex, OpenCode,
   Cursor, Gemini, Zed, GitHub Copilot, and terminal workflows.

This is not generic AI consulting. The output is a working harness operating
system your team can keep using.

ECC started as an open-source workflow layer for Claude Code and is now moving
toward a cross-harness operating system for agentic work.

The talk is about the practical problems teams hit after the first AI coding
honeymoon: scattered prompts, duplicated setup, weak release gates, fragile
security posture, and no clear operating loop across tools.

I can show how ECC uses reusable skills, hooks, MCP conventions, release gates,
AgentShield-style security checks, and an optional Hermes operator shell to make
agentic work more measurable and portable.

ECC v2.0.0-rc.1 preview pack is ready for final release review.

The main point: ECC 2.0 is a meta-harness for agentic work.

It is the portable layer that keeps skills, hooks, MCP conventions, release
gates, security checks, and team workflows reusable across the AI coding tools
people actually use.

It now has a reviewed public surface for:

- reusable skills, hooks, rules, and MCP conventions;
- Claude Code, Codex, OpenCode, Cursor, Gemini, Zed, GitHub Copilot, and
  terminal workflows;
- Hermes as the optional operator shell;
- release, security, queue, discussion, Linear, observability, and video-suite
  gates.
- a gated Itô prediction-market skill pack for research, comparison, planning,
  and risk review, with Itô API access kept separate and approval-based.

The GitHub prerelease and npm `next` package are live now. The release remains
approval-gated for plugin paths, video URLs, final outbound URLs, and billing
claims that have not been freshly rechecked.

Feedback wanted: install friction, cross-harness gaps, partner integrations,
sponsor fit, prediction-market research use cases, and examples of teams using
multiple AI coding harnesses.