# backend_architecture_expert

The backend_architecture_expert Claude Code subagent turns repository context and requirements into a backend architecture specification. It is activated for proposed changes to APIs, data, and services.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 776 repo stars
- Author: AgenticOrgLab
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/backend_architecture_expert.md
- Updated: 2026-11-12
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/backend-architecture-expert

## What it does

The subagent examines the supplied requirements and repository context, then writes a backend architecture specification. It describes the current state, proposed components and interfaces, data flow, and persistence changes.

The document records assumptions, migration and compatibility risks, rejected options, and verification criteria. Its scope covers backend, API, data, and service architecture.

It must not claim to have examined files missing from the supplied context. If repository evidence or a schema is missing, it marks that gap; existing public contracts stay intact unless the task allows a breaking change.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/backend_architecture_expert.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/backend_architecture_expert.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/backend_architecture_expert.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/backend_architecture_expert.md

## When to use it
- turn repository context and requirements into an architecture specification
- map interfaces and data flow across proposed components
- record migration and backward-compatibility risks
- define verification criteria for an implementation proposal

## Example prompts
- Analyze these API change requirements and write an architecture specification from the supplied repository context.
- Describe the components, data flow, and persistence changes for this request.
- Assess migration risks and backward compatibility, then set verification criteria.

## Similar
- [Python Backend Architecture Review](https://affpapa.org/en/nevibecode/skills/python-backend-architecture-review.md) — skill · 528 installs
- [backend-architect](https://affpapa.org/en/nevibecode/agents/backend-architect.md) — subagent · 23691 installs
- [backend-development-feature-development](https://affpapa.org/en/nevibecode/skills/backend-development-feature-development.md) — skill · 2 installs
- [engineering-backend-architect](https://affpapa.org/en/nevibecode/skills/engineering-backend-architect.md) — skill · 356 installs
- [create-a-backend](https://affpapa.org/en/nevibecode/skills/create-a-backend.md) — skill · 708 installs
- [backend-dev](https://affpapa.org/en/nevibecode/agents/backend-dev.md) — subagent · ★ 850 repo stars

From the same set: [agenticorglab/execorchestra](https://affpapa.org/en/nevibecode/by/agenticorglab/execorchestra.md) — 24 cards

---
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
