agentic-design-patternslisted

# Agentic Design Patterns A decision aid for choosing and implementing the right structure for an agentic / multi-step LLM system. This skill does two things: (1) maps a problem to the pattern(s) that solve it, and (2) for the chosen pattern, gives an implementation spec that distinguishes **LLM calls** from **deterministic code** and states the **context strategy** for each call. Most real systems combine several patterns. Do not force a single choice when composition is the right answer. ## How to use this skill 1. Read the user's problem and extract the **symptoms** (what's hard, what's breaking, what's expensive). 2. Match symptoms to pattern(s) using the **Selection table** below. 3. For each selected pattern, open `references/patterns.md` and read that pattern's entry. It contains the step-by-step mechanics: every step tagged `[LLM]` or `[CODE]`, a literal prompt template for each `[LLM]` step, and the context strategy. 4. When proposing an architecture, **explicitly label which steps are model calls and which are plain code**, and **state what each LLM call carries in its context** (fresh / appended / retrieved / batched). This is the most common thing engineers get wrong, so make it explicit. 5. If multiple patterns apply, describe how they nest (see **Composition** below). ## The 20 patterns, by family **Orchestration** — how work is structured, split, and routed 1. Prompt Chaining · 2. Routing · 3. Parallelization · 4. Planning · 5. Multi-Agent Collaboration ·