agentic-patterns

Designs or audits LLM-agent systems using a layered pattern catalog and autonomy gate.

Updated Jun 14, 2026
One-click install
npx skills add https://github.com/AdamKrysztopa/architectural-decisions --skill agentic-patterns-adamkrysztopa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-patterns
Source: https://github.com/AdamKrysztopa/architectural-decisions/tree/main/skills/agentic-patterns
Command: npx skills add https://github.com/AdamKrysztopa/architectural-decisions --skill agentic-patterns-adamkrysztopa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams building LLM agents routinely over-engineer — reaching for multi-agent swarms when a single call would do — or ship agents missing basic guardrails like step budgets, tracing, and human approval gates. This Skill guides the design of a new agentic system or audits an existing one against a catalog of known failure modes. ## Core Features & Use Cases - Greenfield layered design interview: Walks an autonomy gate (single call → workflow → agent → multi-agent) then composes reasoning loop, topology, memory, reliability, governance, and integration layers, each with its named cost. - Nine-point agent code review: Audits existing agent systems for seven over-building defects, one under-building check, and one stale-scaffold check, then recommends the highest-leverage simplification. - Decision persistence: Records every recommendation — including explicit refusals like "no agent needed" — as a proposed decision file with an auditable constitution. - Use Case: Ask whether your support bot needs a multi-agent setup; the Skill maps your current design, flags ungated irreversible actions and missing step budgets, and recommends collapsing to one well-tooled agent with HITL gates. ## Quick Start Ask the agent to review my LangGraph multi-agent setup and tell me whether a single agent with tools would be sufficient.

Frequently Asked Questions about agentic-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide between a workflow and an agent for my LLM task?

Use the autonomy gate: if a developer can lay out the steps predictably, build a workflow; only choose an agent when the model must decide the next action at runtime, retrieval must be adaptive, or the path space is too large to hardcode. A single well-prompted call is the cheapest correct answer when one pass suffices.

When should I use multiple agents instead of one?

Only when a single well-tooled agent genuinely cannot hold the task — for example, stages with little shared context owned by separate teams. Multi-agent designs multiply cost, latency, and communication failure, so the default recommendation is one good agent with tools.

What are the most common defects in production agent code?

The recurring defects are: an agent where a workflow would do, multi-agent where one agent would do, loops without a step budget, unvalidated tool outputs, no durable memory for long runs, ungated irreversible actions, and missing tracing. A nine-point checklist covers these plus under-building and stale scaffolds.

Does agentic RAG differ from standard retrieval-augmented generation?

Yes. Agentic RAG makes retrieval a runtime decision — the loop decides whether to fetch, grades results, and re-queries on weak evidence — costing roughly 3-10x the tokens of static RAG. It is only justified after advanced static RAG with hybrid search and reranking is already sound.

What guardrails does every agent need before shipping?

Every agent needs a hard step budget with an explicit budget-exhausted end, tracing of every thought/action/observation, and offline evaluation on a fixed task set. Agents taking irreversible actions additionally need human-in-the-loop gates, and untrusted input requires input/output/tool guardrails.