mikeparcewski/wicked-garden-agentic-frameworks
skills/agentic/frameworks/SKILL.md
Use when selecting or comparing agentic frameworks (LangChain, LangGraph, CrewAI, AutoGen, etc.) — curated comparison by use case, language, and maturity. Gets latest context via Context7 when available. NOT for reviewing existing agentic code (use review-methodology) or architecture patterns (use agentic-patterns).
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-agentic-frameworksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 12, 2026, 7:04 AM39.3s5 files scanned
SKILL.md
- name:
- wicked-garden-agentic-frameworks
- description:
- |
- portability:
- portable
- phase_relevance:
- ["design", "review"]
- archetype_relevance:
- ["*"]
Agentic Frameworks
Comprehensive guide to agentic frameworks, their strengths, and how to choose the right one.
Quick Comparison Table
| Framework | Language | Best For | Maturity | Learning Curve | |-----------|----------|----------|----------|----------------| | Anthropic ADK | TypeScript | Claude-specific, production | High | Low | | LangGraph | Python | Complex workflows, state | High | Medium | | CrewAI | Python | Role-based teams | Medium | Low | | AutoGen | Python | Multi-agent conversations | Medium | Medium | | Pydantic AI | Python | Type-safe agents | Medium | Low | | OpenAI Agents SDK | Python | OpenAI-specific | Low | Low | | LlamaIndex Agents | Python | RAG-heavy applications | High | Medium | | Haystack | Python | Production pipelines | High | Medium | | Semantic Kernel | C#/Python | Microsoft ecosystem | Medium | Medium | | LangChain | Python | Rapid prototyping | High | Medium-High | | Agency Swarm | Python | OpenAI Assistants API | Low | Low | | Dify | Low-code | No-code workflows | Medium | Very Low |
Selection Criteria
1. Orchestration Capabilities
Simple Sequential:
- LangChain (chains)
- Haystack (pipelines)
- Pydantic AI
Complex Workflows:
- LangGraph (state machines)
- ADK (delegated workflows)
- AutoGen (conversation patterns)
Team-Based:
- CrewAI (role-based)
- Agency Swarm (org structure)
2. State Management
No Built-in State: LangChain, Pydantic AI
Checkpointed State: LangGraph (built-in), ADK (context preservation)
Distributed State: Custom implementation needed for all
3. Tool Integration
Extensive Tool Libraries: LangChain (largest ecosystem), LlamaIndex (RAG-focused), Haystack (production tools)
Easy Tool Definition: Pydantic AI (type-safe), ADK (TypeScript decorators), OpenAI Agents SDK (function calling)
Custom Tools: All frameworks support custom tools
4. Error Handling
Built-in Retry/Fallback: ADK (comprehensive), LangGraph (error handling nodes), Haystack (pipeline error handling)
Manual Error Handling: CrewAI, AutoGen, Pydantic AI
5. Observability
Native Tracing: LangSmith (for LangChain/LangGraph), Braintrust (for ADK)
Third-Party Integration: All support OpenTelemetry, most support LangFuse, Arize
Framework Profiles
See refs/framework-profiles-1.md (ADK, LangGraph, CrewAI) and refs/framework-profiles-2.md (AutoGen, Pydantic AI, LlamaIndex) for detailed profiles.
Anthropic Agent Developer Kit (ADK)
Best for: Production Claude applications Strengths: TypeScript with type safety, built-in context management, comprehensive error handling, delegated workflows Weaknesses: Claude-only, TypeScript/Node only, smaller community When to choose: Building on Claude exclusively, TypeScript/Node stack, need production-ready patterns
LangGraph
Best for: Complex stateful workflows Strengths: State machine abstraction, built-in checkpointing, human-in-the-loop support, time-travel debugging Weaknesses: Steeper learning curve, can be overkill, more boilerplate When to choose: Complex workflows with branches/loops, need state persistence, want human approval gates
CrewAI
Best for: Role-based agent teams Strengths: Intuitive role/task abstraction, simple API, good for hierarchical teams Weaknesses: Less mature, limited state management, fewer production features When to choose: Team-based workflows, quick prototyping, straightforward delegation
AutoGen
Best for: Multi-agent conversations Strengths: Flexible conversation patterns, group chat capabilities, human-in-the-loop Weaknesses: Can be verbose, conversation management complexity When to choose: Agents need to debate/collaborate, conversational workflows
Pydantic AI
Best for: Type-safe Python agents Strengths: Type safety via Pydantic, simple clean API, dependency injection, multi-provider Weaknesses: New/less mature, smaller ecosystem, limited orchestration patterns When to choose: Want type safety, simple agent use cases, already using Pydantic
LlamaIndex Agents
Best for: RAG-heavy applications Strengths: Excellent retrieval capabilities, query planning, tool use with data Weaknesses: Best for RAG use cases, heavier framework When to choose: Heavy RAG requirements, complex data retrieval, query planning needs
Decision Tree
Start: What's your primary use case?
├─ Complex stateful workflow with branches/loops
│ └─ Use: LangGraph
├─ Role-based team of agents
│ └─ Use: CrewAI or ADK
├─ RAG-heavy application
│ └─ Use: LlamaIndex Agents
├─ Multi-agent conversations/debates
│ └─ Use: AutoGen
├─ Simple sequential workflow
│ ├─ TypeScript?
│ │ └─ Use: ADK
│ └─ Python?
│ └─ Use: Pydantic AI or LangChain
├─ Production pipeline
│ └─ Use: Haystack or ADK
└─ Maximum flexibility
└─ Build from scratch or use LangGraph
Language Considerations
Python Frameworks: LangChain, LangGraph, CrewAI, AutoGen, Pydantic AI, LlamaIndex
- Largest ecosystem, most tutorials/examples, best for data science/ML integration
TypeScript Frameworks: Anthropic ADK
- Better type safety, Node.js ecosystem, good for web applications
C# Frameworks: Semantic Kernel
- Microsoft ecosystem, .NET integration
Multi-Provider vs Single-Provider
Multi-Provider (LLM-agnostic): LangChain, LangGraph, CrewAI, AutoGen, Pydantic AI
- Can switch between OpenAI, Anthropic, etc.
- More flexibility but may not leverage provider-specific features
Single-Provider (Optimized): ADK (Claude), OpenAI Agents SDK (OpenAI)
- Better integration with specific provider
- Access to provider-specific features but less flexibility
Production Readiness
Most Production-Ready: Anthropic ADK, LangGraph, Haystack, LlamaIndex
Good for Production: CrewAI, LangChain, AutoGen
Early/Experimental: Pydantic AI, OpenAI Agents SDK, Agency Swarm
When NOT to Use a Framework
Build from scratch if: very simple use case, specific requirements unmet, want maximum control, or learning exercise. Framework overhead not worth it for single LLM calls, static prompts, or no agent behavior.
Quick Recommendations
Just getting started: CrewAI or Pydantic AI | State management: LangGraph | TypeScript: ADK | RAG: LlamaIndex | Team-based: CrewAI or ADK | Max flexibility: LangGraph | Production Claude: ADK
References
refs/framework-profiles-1.md- ADK, LangGraph, CrewAI detailed profilesrefs/framework-profiles-2.md- AutoGen, Pydantic AI, LlamaIndex profiles + comparison matrixrefs/migration-patterns-paths.md- Common migration paths between frameworksrefs/migration-patterns-testing.md- Migration testing, rollback, and effort estimates
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026