EBFlow

Install this before your agents eat themselves.

Multi-agent demos talk. Production fails quieter: a webhook fires twice, a half-validated write sticks, a “completed” row wakes the same worker again. EBFlow is the skill you paste into Cursor, Claude, Codex, Gemini, or Grok so the agent builds a status machine, version gate, and debounce lock before it touches your DB.

One install prompt. Schemas + Railway/Postgres starter included. The rule: only continue if completed and a new version shows up.

View on GitHub
EBFlow production multi-agent workflow: Railway/DB feedback loop with status machine, route layer, idempotent validation, apply, context, history, failure paths, and loop control
Full control plane · same detail as the original architecture flowchart

Copy the prompt. Let the agent build the control plane. Keep the loop from eating your data.

The rule

Only continue if status = completed and a new version is detected.

Version check + status guard + debounce lock. That is the whole control plane.

Status machine

  1. pending
  2. processing
  3. validated
  4. applied
  5. completed

Failure path: failed → retry with backoff → escalated to a human.

How the loop works

  1. Main Agent receives a task / domain / project
  2. Users hit a website or API
  3. Request lands in the DB as pending + version
  4. DB/Railway event wakes a Sub-Agent
  5. Sub-Agent checks version + status (stops if stale)
  6. Route Layer chooses CRUD or API
  7. Validator runs (must be idempotent)
  8. Second Agent applies change → applied
  9. Main Agent writes context + history → completed + version bump
  10. Loop returns only on completed + new version

What you get

Install

Paste into Cursor, Claude Code, Codex, Gemini, or Grok: 

Install this skill globally: https://github.com/Ezra-Black/EB-Flow
Open Railway starter

Guides: Cursor, Claude, Codex, Gemini, Grok