orchestration-agent-architect

Designs AI agent architectures using 21 design patterns mapped to Resparkable orchestration primitives.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/human-centric-engineering/resparkable --skill orchestration-agent-architect-human-centric-engineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestration-agent-architect
Source: https://github.com/human-centric-engineering/resparkable/tree/main/.claude/skills/orchestration-agent-architect
Command: npx skills add https://github.com/human-centric-engineering/resparkable --skill orchestration-agent-architect-human-centric-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the right architecture for an AI agent system is hard: developers must pick among many agentic design patterns, combine them correctly, weigh latency/cost/autonomy trade-offs, and translate the design into concrete platform primitives. This Skill guides that design phase so agent systems are grounded in proven patterns rather than ad-hoc prompts. ## Core Features & Use Cases - Pattern selection and composition: Recommends from 21 agentic design patterns (routing, RAG, reflection, guardrails, HITL, and more) with selection tables, troubleshooting guides, and six ready-made composition recipes. - Platform mapping: Maps every pattern to concrete Resparkable orchestration primitives such as agents, capabilities, workflow step types, knowledge bases, and evaluation judges. - Production readiness review: Provides trade-off analysis, anti-pattern warnings, and a production checklist covering rate limits, idempotency, observability, and cost alerting. - Use Case: A developer says "build me a support chatbot that looks up orders and escalates refunds." The Skill recommends Routing + RAG + Tool Use + Guardrails + HITL, maps them to a route step, knowledge base, capabilities, and a human_approval step, then hands off to the orchestration-solution-builder for implementation. ## Quick Start Ask the agent architect to design an AI agent system for your use case, for example by describing the business problem and requesting a pattern-based architecture mapped to Resparkable primitives.

Frequently Asked Questions about orchestration-agent-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right agentic design pattern for my AI agent?▼

Use the pattern selection guide: match the user's need (multi-step tasks, routing, quality improvement, external API calls) to one of 21 patterns such as Prompt Chaining, Routing, Reflection, or Tool Use. Start with the simplest pattern that solves the problem.

How do I design a multi-agent AI system architecture?▼

Combine the Multi-Agent pattern with Planning, RAG, and Goal Monitoring using the composition recipes as starting architectures. Each pattern maps to concrete primitives like agent_call steps, orchestrator steps, and knowledge bases.

Why is my AI agent hallucinating and how do I fix it?▼

Hallucination usually means the agent lacks grounding in real data. The troubleshooting guide recommends adding RAG for knowledge retrieval and tightening guardrails with layered input and output filtering.

How do I reduce LLM token costs in an agent workflow?▼

Apply resource-aware optimisation with tiered model routing: send most queries to budget models and reserve frontier models for hard problems. Prompt caching, context compression, and output limits provide additional savings.

When should I use human-in-the-loop approval in an agent system?▼

Use human-in-the-loop for high-stakes actions like financial transactions, data deletion, or public communications. Avoid requiring approval for every action, since that creates bottlenecks that defeat automation.

What are common anti-patterns when building AI agents?▼

Common mistakes include over-engineering with multi-agent systems when prompt chaining suffices, relying on one mega-prompt, deferring guardrails, using frontier models for everything, and stuffing entire documents into context instead of using RAG.