skills/agentic/SKILL.md
Agentic-systems domain skill: review, design, audit, and framework selection for AI agent systems. Routes to one of four actions (review | design | audit | frameworks) backed by the rubrics in refs/. Use when: "agentic review", "review this agent system", "full agentic codebase review", "trust and safety audit", "audit my agents for GDPR/HIPAA/SOC2/NIST compliance", "design an agentic system", "design a multi-agent architecture", "which agentic framework should I use", "compare LangChain vs CrewAI vs AutoGen", or any former /wicked-garden:agentic:{review|design|audit|frameworks} invocation. Disambiguation: this domain reviews and designs **AI agent systems**. For ordinary source code use the engineering review; for a binding go/no-go verdict use the archetype review (see docs/domains.md → "review appears in three domains").
npx skillsauth add mikeparcewski/wicked-garden wicked-garden-agenticInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
One entry point for the agentic domain. Pick the action from the request, parse its args, load its ref, and apply it inline.
| Action | Use for | Args | Ref |
|--------|---------|------|-----|
| review | Full agentic-codebase review: framework detection, topology, architecture + safety + performance, remediation roadmap | [path] [--quick] [--framework NAME] [--output FILE] | refs/review.md |
| design | Greenfield agentic system design: requirements → pattern + five-layer architecture → safety validation → design doc | [problem description] [--output FILE] | refs/design.md |
| audit | Compliance-grade trust+safety audit: tool risk classification, HITL gates, PII handling, evidence | [path] [--standard GDPR\|HIPAA\|SOC2\|NIST] [--output FILE] [--scenarios] | refs/audit.md |
| frameworks | Framework selection / comparison / wizard | [--compare fw1,fw2,...] [--language python\|typescript\|java\|go] [--use-case TYPE] | refs/frameworks.md |
Routing hints:
review. Compliance-grade safety
evidence → audit. Greenfield design → design. Picking or comparing
frameworks → frameworks.Full agentic-codebase review: framework detection → topology → architecture + safety + performance assessments → pattern scoring → unified remediation roadmap.
[path], --quick, --framework, --output.Read("${CLAUDE_PLUGIN_ROOT}/skills/agentic/refs/review.md") — the full
5-step review rubric: framework+topology detection, architecture assessment,
safety 8-layer, performance assessment, pattern scoring + issue taxonomy,
and output format.--quick, stop and return
the structural summary. Otherwise apply all rubric steps directly.--output file when set; otherwise return inline.For large codebases, or when independent parallel assessments are wanted, dispatch the three fork skills as parallel workers instead of applying rubric steps 2–4 inline, then merge their findings into the ref's unified roadmap:
wicked-garden-agentic-architect — five-layer architecture + agent topologywicked-garden-agentic-safety-reviewer — guardrails, prompt injection, PII, HITLwicked-garden-agentic-performance-analyst — tokens, latency, cost, parallelizationInteractive design session for a new agentic system: requirements → pattern +
five-layer architecture → safety validation → design doc. Greenfield only —
use review to assess existing code, audit for compliance evidence.
[problem description] and --output.Read("${CLAUDE_PLUGIN_ROOT}/skills/agentic/refs/design.md") — the design
rubric: requirements gathering, pattern selection, five-layer architecture,
safety section, framework recommendation, and output format.--output file when set; otherwise return inline.Deep trust+safety audit: classifies tool risks, verifies HITL gates, checks PII
handling, optionally emits compliance evidence + wicked-scenarios. Use review
for the broader architecture+perf+safety sweep.
[path], --standard, --output, --scenarios.Read("${CLAUDE_PLUGIN_ROOT}/skills/agentic/refs/audit.md") — the 8-layer rubric,
checklist, compliance extensions, and output format.--standard is given, append the matching compliance checklist from the ref.--scenarios, emit a wicked-scenarios block per CRITICAL/HIGH finding.--output file when set; otherwise return inline.Framework selection / comparison / wizard. NOT for reviewing existing agentic
code (use review) or architecture design (use design).
--compare → side-by-side comparison; filters only
(--language, --use-case) → filtered selection; no args → interactive
5-question wizard.Read("${CLAUDE_PLUGIN_ROOT}/skills/agentic/refs/frameworks.md") — the
mode detection table, wizard questions, decision tree, comparison table,
scoring template, and output format.skills/agentic/frameworks/ knowledge module.design action of this skill as the next step.The domain's reference knowledge lives beside this skill and is loaded on demand:
skills/agentic/agentic-patterns/ — pattern catalog + five-layer modelskills/agentic/context-engineering/ — context/token optimization techniquesskills/agentic/frameworks/ — curated framework profiles + decision treeskills/agentic/review-methodology/ — systematic review approachskills/agentic/trust-and-safety/ — guardrail + HITL patternsdevelopment
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.
tools
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.
development
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).
tools
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).