agentic-architecture · git:20260601.8eda6f7 · 2026-06-01 · sha256 9c21f9177247bcd1
agentic-architecture git:20260601.8eda6f7A
Immutable. This exact content never changes and is served at /api/v1/blob/9c21f9177247bcd1.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_tcfgbj2tmyolse3y/9c21f9177247bcd158823cba36e47f7fdb22e03ae719527817d57e5dcbb62127.json
Then /plugin install agentic-architecture@markdownregistry-tcfgbj2tmyolse3y in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: agentic-architecture description: | Architecture of LLM agent systems: orchestration topologies (single agent, supervisor/sub-agents, pipelines, networks), memory/context strategy, the tool layer, and human-in-the-loop/control. Architect-level system design, not prompt wording. USE WHEN: designing agentic/LLM-agent systems, "agent orchestration", "multi-agent", "supervisor", "sub-agents", "tool use", "agent memory", "human-in-the-loop", workflow vs autonomous agent, agent topology/control. DO NOT USE FOR: single prompt/RAG retrieval design (use rag skills); model serving (use `inference-serving-topology`); provider routing (use `model-gateway-routing`). allowed-tools: Read, Grep, Glob --- # Agentic System Architecture ## First choice: workflow vs autonomous agent - **Workflow** (fixed, code-orchestrated steps with LLM calls): predictable, cheap, debuggable. **Prefer this** when the steps are known. - **Autonomous agent** (LLM decides the next action in a loop): flexible, handles open-ended tasks, but less predictable and costlier. Use only when the path genuinely can't be pre-defined. ## Orchestration topologies | Topology | Shape | Fits | |---|---|---| | Single agent + tools | One loop, a toolbox | Most tasks; start here | | Supervisor / sub-agents | Orchestrator delegates to specialists (own context) | Decomposable tasks, context isolation | | Pipeline / chain | Staged hand-offs | Known multi-stage transforms | | Network / peer agents | Agents message each other | Rarely needed; high complexity/cost | Bias to the **simplest** topology that works; isolate context with sub-agents when a subtask would flood the main context. ## Cross-cutting design concerns - **Memory/context**: short-term (conversation), long-term (vector/store), and scratch. Compaction/summarization to fit the window; what persists across runs? - **Tool layer**: typed tools with clear contracts; least-privilege; validate tool I/O; tools are the agent's blast radius — scope them. - **Control & safety**: human-in-the-loop approval for irreversible/outward actions; step/turn budgets; loop/termination conditions; guardrails. - **Determinism & cost**: cap iterations, cache, and prefer workflows for the deterministic parts. Observability: trace each step (tool calls, tokens, cost). - **Failure handling**: retries, fallbacks, and a defined "give up / escalate" path; don't let agents loop forever. ## When to recommend what - Known steps → workflow. Open-ended + decomposable → supervisor + sub-agents. - One coherent task → single agent + tools. Reach for multi-agent networks only when simpler shapes demonstrably fail.