Skip to content

mikeparcewski/wicked-garden / skills/agentic

wicked-garden-agentic

Verified

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").

FileKindSize
SKILL.mdskill md7.2 KB
refs/audit.mdmarkdown4.5 KB
refs/design.mdmarkdown4.0 KB
refs/frameworks.mdmarkdown3.7 KB
refs/review.mdmarkdown4.7 KB

refs/design.md

View on GitHub
# agentic:design — Interactive Agentic Architecture Design Rubric

Full rubric sourced from the `wicked-garden-agentic-architect` worker skill (former `agents/agentic/architect.md`) and
`skills/agentic/agentic-patterns/`. Use for greenfield agentic system design.

## Phase 1: Requirements Gathering

If no problem statement is supplied, ask 3–5 clarifying questions:

1. What is the primary task the agentic system must accomplish?
2. What tools / APIs / external systems must it interact with?
3. What are the concurrency and latency requirements?
4. What safety constraints apply (PII, HITL, compliance)?
5. What framework preferences or constraints exist?

## Phase 2: Pattern Selection

Pick from the agentic pattern catalog (`skills/agentic/agentic-patterns/refs/pattern-catalog.md`):

| Pattern | Use when |
|---------|---------|
| Scatter-Gather | Independent parallel lookups → aggregate |
| Pipeline | Sequential stages, each depending on prior |
| Router | Different input types → specialized agents |
| Retry with Fallback | Transient failures expected |
| Orchestrator / Subagents | Complex delegation with state |
| Event-Driven | Decoupled, reactive workflows |

## Phase 3: Five-Layer Architecture

Render a five-layer breakdown for the proposed system:

### Layer 1: Cognition
- Agent roles and single-responsibility assignments
- Reasoning pattern (ReAct, CoT, plan-and-execute)
- Task decomposition strategy
- Prompt versioning approach

### Layer 2: Context
- Memory scope (global vs. agent-local)
- State checkpointing strategy
- Context window budget (see `skills/agentic/context-engineering/`)
- Cleanup / archival policy

### Layer 3: Interaction
- Tool inventory with capability + risk classification
- External API contracts
- Multi-agent communication protocol
- Graceful degradation for tool failures

### Layer 4: Runtime
- Orchestration pattern (sequential | parallel | dynamic)
- Error handling and retry logic
- Resource quotas (max turns, max tokens, timeouts)
- Observability (structured logging, tracing, metrics)

### Layer 5: Governance
- Input / output validation points
- HITL gate placement (use Layer 3 tool risk to position)
- Audit logging requirements
- Compliance constraints

## Phase 4: Safety Section

Apply the 8-layer trust-and-safety checklist from `skills/agentic/refs/audit.md`
to the proposed architecture. For a design review, focus on:

- Tool risk classification (Layer 1 of audit)
- HITL gate placement (Layer 2 of audit)
- PII touchpoints (Layer 3 of audit)
- Prompt injection exposure (Layer 4 of audit)
- Failure mode defaults (Layer 8 of audit)

## Phase 5: Framework Recommendation

Using `skills/agentic/frameworks/SKILL.md` decision tree:

| Requirement | Recommended framework |
|-------------|----------------------|
| Complex state + loops | LangGraph |
| Role-based team | CrewAI or ADK |
| RAG-heavy | LlamaIndex Agents |
| TypeScript / Claude-only | Anthropic ADK |
| Type-safe Python | Pydantic AI |
| Multi-agent conversation | AutoGen |

## Output Format

````markdown
## Agentic Architecture Design: {System Name}

**Date**: {date} | **Pattern**: {chosen pattern} | **Framework**: {recommendation}

### Problem Statement

{refined from clarifying questions}

### Five-Layer Architecture

#### Layer 1: Cognition
{agent roster, roles, reasoning patterns}

#### Layer 2: Context
{memory strategy, state, checkpointing}

#### Layer 3: Interaction
{tool inventory with risk tier, API contracts}

#### Layer 4: Runtime
{orchestration, error handling, resource limits, observability}

#### Layer 5: Governance
{HITL gates, validation points, audit, compliance}

### Architecture Diagram

```mermaid
graph TB
    User --> Orchestrator
    Orchestrator --> AgentA & AgentB
    AgentA --> ToolX
    AgentB --> ToolY
```

### Safety Validation

{8-layer safety checklist results — flag any CRITICAL/HIGH risks}

### Next Steps

1. {critical action}
2. {high action}
3. {medium action}

→ Use `agentic:review` to assess once code is written.
→ Use `agentic:audit` for compliance-grade evidence before production.
````
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall