# cascade

An orchestrator for edits that touch several services at once: field renames, new headers, API contract sync.

- plugin · `type=plugin` · Claude Code · ★ 9
- Author: alibrahim
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/alibrahim/cascade/tree/HEAD/plugins/cascade
- Updated: 2026-03-28
- HTML: https://affpapa.org/en/nevibecode/plugins/cascade

## What it does

Your coding agent is fine inside a single repo. A field rename that has to travel through several services, SDKs and an API contract is where it breaks down. Cascade runs that change from one orchestrator session.

Five agents sit behind it. The planner works out which services are affected and in what order. A worker edits one service at a time, contracts get updated after each step rather than at the end, and a verifier hunts for stale references and mismatches. Failures go back for a fix and a second check. Ordering runs upstream first: touch catalog-service before auth-service and the code will point at a field that does not exist yet.

Run `/cascade-init` before anything else. It writes `cascade.yaml` with service paths, ports, entry points and dependencies. The stack does not matter — Python, JavaScript, Go, anything with HTTP APIs and text sources. You fill in `cascade.yaml` yourself, and wrong dependency entries send the orchestrator down the wrong order. That is the usual failure point.

## Install

### Claude Code (native platform)

**Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add anthropics/claude-plugins-community
```
In the agent chat (not a shell):
```text
/plugin install cascade@claude-community
```

## When to use it
- push a field rename through every service
- refresh API contracts after each service edit
- catch stale references to a renamed field
- order edits from upstream services to downstream ones
- add a shared header across all services at once

## Example prompts
- Rename `role` to `account_type` across all services
- Add a `phone` field to users and propagate it to every service
- Show service status and contract versions

## Similar
- [narrative-cascade-planner](https://affpapa.org/en/nevibecode/skills/narrative-cascade-planner.md) — skill · 1000 installs
- [saga-orchestration](https://affpapa.org/en/nevibecode/skills/saga-orchestration.md) — skill · 10700 installs
- [conductor](https://affpapa.org/en/nevibecode/plugins/conductor-oss-conductor.md) — plugin · ★ 24
- [encore-service](https://affpapa.org/en/nevibecode/skills/encore-service.md) — skill · 819 installs
- [backend-architect](https://affpapa.org/en/nevibecode/skills/backend-architect.md) — skill · 501 installs
- [software-patterns](https://affpapa.org/en/nevibecode/skills/software-patterns.md) — skill · 373 installs

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md