wicked-garden-agentic-agentic-patterns
Skill9 starsChanged 7 months agoMITView on GitHub
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).
In this repository142 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- plugin-json-schemaSkill
- readme-style-guideSkill
- releaseSkill
- scaffoldSkill
- wicked-garden-agentic-architectSkill
- wicked-garden-agentic-context-engineeringSkill
- wicked-garden-agentic-frameworksSkill
- wicked-garden-agentic-performance-analystSkill
- wicked-garden-agentic-review-methodologySkill
- wicked-garden-agentic-safety-reviewerSkill
- wicked-garden-agenticSkill
- wicked-garden-agentic-trust-and-safetySkill
- wicked-garden-appsSkill
- wicked-garden-archetypeSkill
- wicked-garden-build-guideSkill
- wicked-garden-classifySkill
- wicked-garden-coreSkill
- wicked-garden-data-engineerSkill
- wicked-garden-dataSkill
- wicked-garden-deliberateSkill
- wicked-garden-demoSkill
- wicked-garden-domain-coverageSkill
- wicked-garden-domain-extractorSkill
- wicked-garden-domain-modelerSkill
- wicked-garden-domainSkill
- wicked-garden-draftSkill
- wicked-garden-editor-scaffoldSkill
- wicked-garden-engineering-api-documentarianSkill
- wicked-garden-engineering-architectureSkill
- wicked-garden-engineering-backendSkill
- wicked-garden-engineering-debuggingSkill
- wicked-garden-engineering-docsSkill
- wicked-garden-engineering-frontendSkill
- wicked-garden-engineering-integrationSkill
- wicked-garden-engineering-large-scale-migrationSkill
- wicked-garden-engineering-migration-engineerSkill
- wicked-garden-engineering-patchSkill
- wicked-garden-engineeringSkill
- wicked-garden-engineering-solution-architectSkill
- wicked-garden-engineering-system-designSkill
- wicked-garden-engineering-unit-test-qualitySkill
- wicked-garden-governed-workerSkill
- wicked-garden-groundSkill
- wicked-garden-jam-brainstorm-facilitatorSkill
- wicked-garden-jam-councilSkill
- wicked-garden-jamSkill
- wicked-garden-learnSkill
- wicked-garden-mcp-scaffoldSkill
- wicked-garden-mcpSkill
- wicked-garden-mem-captureSkill
- wicked-garden-mem-ingestSkill
- wicked-garden-memSkill
- wicked-garden-personaSkill
- wicked-garden-platform-auditSkill
- wicked-garden-platform-compliance-officerSkill
- wicked-garden-platform-complianceSkill
- wicked-garden-platform-errorsSkill
- wicked-garden-platform-gate-benchmark-rebaselineSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Missing Guardrails: No constraints on agent actions.
- Distinctive: line 62
Add Human-in-the-Loop gates for any high-stakes decisions.
- Distinctive: line 63
Add Reflection layer when quality is critical.
- Distinctive: line 85
Check anti-patterns list against current design
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agentic Patterns
Reference guide for proven agentic architecture patterns and common anti-patterns to avoid.
Core Patterns
| Pattern | Use when | Example | Tradeoffs |
| Sequential | Linear workflow, clear dependencies, predictable stages | Research → Analyze → Draft → Review | Simple coordination; bottlenecks if any agent is slow |
| Hierarchical | Complex task decomposable into subtasks; central coordination | PM agent delegates to designer / dev / QA | Clear accountability, scales; single point of failure at parent |
| Collaborative | Diverse perspectives matter; no clear lead | Multiple reviewers collaborating on code review | Rich outputs; needs conflict resolution + consensus |
| Autonomous | Tasks are fully independent; parallel execution | Multiple monitoring agents checking different services | Max parallelism; no shared learning or coordination |
| Human-in-the-Loop | High-stakes decisions, regulatory gates, human feedback | Agent drafts report; human approves before sending | Adds latency; ensures safety and quality |
| ReAct | Dynamic environments; need adaptive behavior on feedback | Debug agent: try fix → observe tests → adapt | Flexible; high token/latency cost for reasoning |
| Plan-Execute | Predictable environment; planning overhead justified | Multi-step pipeline with known transformations | Efficient; brittle if environment changes |
| Reflection | Quality > speed; self-improvement valuable | Writer drafts → critiques → refines | Higher quality; more tokens and latency |
See refs/pattern-catalog.md for full descriptions and implementation notes per pattern.
Anti-Patterns Quick Reference
- God Agent: Single agent doing everything. Split responsibilities.
- Tight Coupling: Agents depend on internal implementation details. Use interfaces.
- Missing Guardrails: No constraints on agent actions. Add validation and limits.
- Deep Nesting: Agents calling agents calling agents. Flatten hierarchy.
- No Observability: Can't see what agents are doing. Add logging and tracing.
- Sequential Bottleneck: Everything waits for slowest agent. Add parallelism.
- Context Bloat: Passing entire history to every agent. Compress and filter.
- Redundant Agents: Multiple agents doing same thing. Consolidate.
- Hardcoded Prompts: Prompts baked into code. Externalize and version.
- 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 SequentialAdd 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
- Identify if task is decomposable (subtasks?) or atomic
- Identify if execution is predictable (plan?) or dynamic (adapt?)
- Identify if agents should coordinate (hierarchy/collaboration) or work independently
- Check anti-patterns list against current design
- See refs/pattern-catalog.md for detailed examples
References
refs/pattern-catalog.md- Detailed pattern descriptions with implementation examplesrefs/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)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

