Skip to content

mikeparcewski/wicked-garden / skills/agentic/agentic-patterns

wicked-garden-agentic-agentic-patterns

Verified

Use when designing or analyzing multi-agent architectures — covers core patterns (sequential, hierarchical, parallel, event-driven), anti-patterns, and the five-layer model (Cognition → Context → Interaction → Runtime → Governance) for separating concerns in production-grade agentic systems. NOT for reviewing existing agentic code (use review-methodology) or framework selection (use the frameworks skill).

Agentic Patterns

Reference guide for proven agentic architecture patterns and common anti-patterns to avoid.

Core Patterns

PatternUse whenExampleTradeoffs
SequentialLinear workflow, clear dependencies, predictable stagesResearch → Analyze → Draft → ReviewSimple coordination; bottlenecks if any agent is slow
HierarchicalComplex task decomposable into subtasks; central coordinationPM agent delegates to designer / dev / QAClear accountability, scales; single point of failure at parent
CollaborativeDiverse perspectives matter; no clear leadMultiple reviewers collaborating on code reviewRich outputs; needs conflict resolution + consensus
AutonomousTasks are fully independent; parallel executionMultiple monitoring agents checking different servicesMax parallelism; no shared learning or coordination
Human-in-the-LoopHigh-stakes decisions, regulatory gates, human feedbackAgent drafts report; human approves before sendingAdds latency; ensures safety and quality
ReActDynamic environments; need adaptive behavior on feedbackDebug agent: try fix → observe tests → adaptFlexible; high token/latency cost for reasoning
Plan-ExecutePredictable environment; planning overhead justifiedMulti-step pipeline with known transformationsEfficient; brittle if environment changes
ReflectionQuality > speed; self-improvement valuableWriter drafts → critiques → refinesHigher quality; more tokens and latency

See refs/pattern-catalog.md for full descriptions and implementation notes per pattern.

Anti-Patterns Quick Reference

  1. God Agent: Single agent doing everything. Split responsibilities.
  2. Tight Coupling: Agents depend on internal implementation details. Use interfaces.
  3. Missing Guardrails: No constraints on agent actions. Add validation and limits.
  4. Deep Nesting: Agents calling agents calling agents. Flatten hierarchy.
  5. No Observability: Can't see what agents are doing. Add logging and tracing.
  6. Sequential Bottleneck: Everything waits for slowest agent. Add parallelism.
  7. Context Bloat: Passing entire history to every agent. Compress and filter.
  8. Redundant Agents: Multiple agents doing same thing. Consolidate.
  9. Hardcoded Prompts: Prompts baked into code. Externalize and version.
  10. Missing Timeouts: Agents can run forever. Add time and resource limits.

Pattern Selection Decision Tree

Is task decomposable into subtasks?
├─ YES: Is there a clear lead/coordinator role?
│   ├─ YES: Use Hierarchical
│   └─ NO: Use Collaborative
└─ NO: Does task require adaptation based on results?
    ├─ YES: Can you plan all steps upfront?
    │   ├─ YES: Use Plan-Execute
    │   └─ NO: Use ReAct
    └─ NO: Do you have multiple independent tasks?
        ├─ YES: Use Autonomous
        └─ NO: Use Sequential

Add Human-in-the-Loop gates for any high-stakes decisions. Add Reflection layer when quality is critical.

Combining Patterns

Patterns are composable:

  • Hierarchical + ReAct: Parent plans, children adapt execution
  • Sequential + Reflection: Each stage includes self-review
  • Collaborative + Human-in-Loop: Peer review with human arbitration
  • Autonomous + Hierarchical: Independent teams with team leads

Pattern Anti-Affinities

Avoid these combinations:

  • Plan-Execute + ReAct: Contradictory - either plan upfront or adapt dynamically
  • Autonomous + Tight Coordination: Defeats the purpose of autonomy
  • Deep Hierarchies + Reflection: Exponential token cost

Quick Start

  1. Identify if task is decomposable (subtasks?) or atomic
  2. Identify if execution is predictable (plan?) or dynamic (adapt?)
  3. Identify if agents should coordinate (hierarchy/collaboration) or work independently
  4. Check anti-patterns list against current design
  5. See refs/pattern-catalog.md for detailed examples

References

  • refs/pattern-catalog.md - Detailed pattern descriptions with implementation examples
  • refs/anti-patterns-design.md - Design anti-patterns (God Agent, Tight Coupling, Missing Guardrails, Deep Nesting, No Observability)
  • refs/anti-patterns-operational.md - Operational anti-patterns (Sequential Bottleneck, Context Bloat, Redundant Agents, Hardcoded Prompts, Missing Timeouts)
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 197kUpdated Claude CodeCodexVerifiedInstall