Skip to content
Skills Library
Programming · Automation

ecc-workflow

/ecc-workflow

Everything Claude Code (ECC) engineering harness and multi-agent workflow system. Use when planning, implementing features, fixing bugs, applying TDD, running code reviews, or orchestrating subagents across Claude Code, Codex, Antigravity, Cursor, and Windsurf.

Repository
REA_Skill ↗
Licence
MIT
Last repository change
10.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
5
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Everything Claude Code (ECC) engineering harness and multi-agent workflow system. Use when planning, implementing features, fixing bugs, applying TDD, running code reviews, or orchestrating subagents across Claude Code, Codex, Antigravity, Cursor, and Windsurf.

Original author description

Everything Claude Code (ECC) engineering harness and multi-agent workflow system. Use when planning, implementing features, fixing bugs, applying TDD, running code reviews, or orchestrating subagents across Claude Code, Codex, Antigravity, Cursor, and Windsurf.

How it works

  1. 🏛️ The 6-Stage ECC Development Pipeline
  2. 🔄 ECC Orchestration Workflows (orch-)
  3. 🤝 Pairing ECC with REA & Agent Reach
  4. 🛠️ Official ECC Setup & Tools
Original SKILL.md headings · 94 lines, 678 words
SKILL.md preview
---
name: ecc-workflow
description: Everything Claude Code (ECC) engineering harness and multi-agent workflow system. Use when planning, implementing features, fixing bugs, applying TDD, running code reviews, or orchestrating subagents across Claude Code, Codex, Antigravity, Cursor, and Windsurf.
---

# ECC Workflow (Everything Claude Code Agent Harness)

The ultimate agent harness performance optimization system based on [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code). It equips AI coding agents with research-first development, TDD discipline, systematic debugging, automated code reviews, and verification gates.

---

## 🏛️ The 6-Stage ECC Development Pipeline

Every non-trivial engineering task follows the ECC standard pipeline:

```mermaid
flowchart LR
    A["0. Research & Reuse"] --> B["1. Plan First"]
    B --> C["2. TDD (Red-Green-Refactor)"]
    C --> D["3. Autonomous Code Review"]
    D --> E["4. Pre-Commit Security Audit"]
    E --> F["5. Verification Before Completion"]
```

### Stage 0: Research & Reuse (Mandatory Before Coding)
1. **GitHub Code Search First:** Search GitHub repositories and existing code for proven implementations or templates before writing anything new:
   ```bash
   gh search repos "<keyword>" --limit 5
   gh search code "<pattern>" --limit 5
   ```
2. **Library Docs First:** Confirm API signatures, versions, and patterns in official vendor documentation rather than guessing.
3. **Agent Reach for Web Intel:** When external platform discussions, issue threads, or benchmarks are needed, invoke `agent-reach` to gather structured findings without API fees.
4. **Registry Verification:** Search package managers (npm, PyPI, crates.io) for battle-tested libraries before writing custom utilities.

### Stage 1: Plan First
1. Never jump straight into code without a concrete sequence of implementation.
2. Produce structured architecture plans: PRD, technical design, edge-case analysis, and task checklist.
3. Establish clear acceptance criteria for every phase.

### Stage 2: Test-Driven Development (TDD)
1. **RED:** Write failing unit, integration, or E2E tests first. Observe the test fail to verify that it tests the right assertion.
2. **GREEN:** Write the minimal implementation required to make the tests pass.
3. **REFACTOR:** Clean up code, remove duplication, and improve performance while keeping tests green.
4. Target 80%+ test coverage across core business logic.

### Stage 3: Autonomous Code Review
Run immediate diff-level reviews before committing:
- **Null safety & edge cases:** Defend against unexpected nulls, undefined values, and unhandled exceptions.
- **Concurrency & Race Conditions:** Ensure thread safety, mutex discipline, and atomic state transitions.
- **Dependency & Regression Pitfalls:** Ensure existing features remain unbroken.

### Stage 4: Pre-Commit Security & Zero-Secret Audit
- **Strict Zero-Secret Law:** Under NO circumstances should ANY secret, private key, JWT, or credential be committed:
  ```bash
  git diff --cached
  ```
- Ensure `.env`, `.env.local`, credentials, and tokens are strictly excluded in `.gitignore`.
- Sanitize git remote URLs (never embed access tokens).

### Stage 5: Verification Before Completion
- **Evidence Before Assertions:** Never claim a task is complete or fixed without running verification commands and checking exit codes.
- Run the full test suite, build process, and linter.

---

## 🔄 ECC Orchestration Workflows (`orch-*`)

| Workflow | Use Case | Execution Sequence |
| :--- | :--- | :--- |
| **`orch-add-feature`** | Brand new capability | Research & Reuse → Implementation Plan → TDD → Code Review → Verification → Gated Commit |
| **`orch-change-feature`**| Altering existing behavior | Spec Update → Update Tests to New Behavior → Code Adjustment → Verify Green → Review |
| **`orch-fix-defect`** | Bug or defect fix | Reproduce as Failing Regression Test → Root Cause Tracing → Fix to Green → Verification |
| **`orch-refine-code`** | Refactoring | Verify Green Baseline → Refactor Structure Without Changing Behavior → Verify Still Green |

---

## 🤝 Pairing ECC with REA & Agent Reach

When performing reverse engineering, vulnerability assessments, or app security with **REA**:
1. **Systematic Investigation:** Use ECC's `systematic-debugging` methodology to trace root causes in disassembled code rather than making speculative edits.
2. **Defensive Hardening via TDD:** When fixing a security vulnerability discovered by REA or the `website-security-audit`, write an automated test reproducing the vulnerable payload first, apply the remediation, and verify the test passes.
3. **Live Intelligence via Agent Reach:** Use Agent Reach to pull CVE bulletins, patch notes, and GitHub advisory threads directly into the ECC research phase.

---

## 🛠️ Official ECC Setup & Tools

Install ECC tools and universal configurations:
```bash
# ECC Universal NPM package
npm install -g ecc-universal

# ECC Security & AgentShield
npm install -g ecc-agentshield
```
Official Repository: [https://github.com/affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code)
Website: [https://ecc.tools](https://ecc.tools)
Files in this package (2)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · smartworldarafath/REA_Skill100MIT
eliozh/ecc-workflow100MIT

Database snapshot: 13.11.2026 · package version 54a9b7d247aa (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100ecc
    ECC (Everything Claude Code) is an open-source toolkit that adds agents, skills, slash commands, rules, hooks and a shared memory vault to coding agents such as Claude Code and Codex. Use it when a user asks to "install ECC", "set up ecc-universal", "add a planning, TDD and…
  • 100ecc
    Install, configure, verify, update, or recover affaan-m/ECC, the MIT-licensed agent harness with native Claude Code and Codex plugins plus selective adapters for other supported clients. Use when the user names ECC, Everything Claude Code, ecc-universal, ecc@ecc, `ecc setup`, or…
  • 95workflow-tdd
    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
  • 90ecc-harness-os
    基于 ECC(affaan-m/ECC,Agent Harness 操作系统)为 CLI coding agent 安装与配置整套 工程纪律:当用户要把「计划→测试→实现→评审→沉淀」流程固化进 Claude Code/Codex/Kimi 等 harness、跨 harness 共享技能与会话记忆、或对已装 ECC 做 doctor/repair 体检修复与 AgentShield 安全扫描时触发。边界:不做多 agent 可视化协作仿真,不解决纯网页 chat 产品的接入,不充当专用记忆层选型方案。
  • 100brownfield-retrospective
    Run the ECC engineering process retroactively against an existing project slice. Audit current state, reconstruct past decisions, produce a four-axis gap register (thinking, coding practice, missing features, technology selection), then execute fixes forward through the…
  • 100tdd-workflow
    Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.