agent-engineering

Design production AI agent architectures with multi-agent coordination and reliability controls.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill agent-engineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-engineering
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/agent-engineering
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill agent-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you design and evaluate production AI agent systems that don’t just work in demos, but also coordinate safely, reliably, and within cost and reliability budgets.

Core Features & Use Cases

  • Production-ready agent architecture: lifecycle state management (claim → execute → verify → commit → release), durable handoffs, and recovery across crashes.
  • Multi-agent coordination patterns: orchestrator/worker, fan-out/merge, evaluator/optimizer, consensus/fusion, sequential chain, and hybrid—plus when each is worth the overhead.
  • Reliability and audit gates: observability, cost budgets, idempotency, failure recovery, safety caps, and claim locks—along with common failure-mode detection and mitigation.
  • Delegation decision framework: overhead crossover guidance (including when to keep work inline vs delegate) to prevent over-delegation and silent stalls.

Quick Start

Use the agent-engineering skill to audit your current multi-agent workflow and recommend the correct coordination pattern, failure-mode mitigations, and production readiness checks.

Frequently Asked Questions about agent-engineering

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

FAQPage Schema
How do I prevent race conditions and silent stalls in multi-agent coordination?

Prevent race conditions and stalls in multi-agent coordination by applying claim locks and explicit lifecycle state management. This ensures agents safely claim, execute, verify, and release tasks without overwriting each other's work.

What's the best way to design multi-agent systems for production reliability?

Design multi-agent systems for production reliability by implementing durable handoffs, idempotency, cost budgets, and failure recovery. This prevents demo-only failures and ensures orchestrated workflows survive crashes across session boundaries.

When should I use orchestrator/worker patterns versus fan-out/merge for AI agents?

Use orchestrator/worker patterns for delegation and fan-out/merge for parallel processing. Evaluating overhead crossover guidance helps determine when coordination overhead is worth it versus keeping tasks inline.

How do I add observability and safety caps to an orchestrated AI workflow?

Add observability and safety caps to orchestrated AI workflows by integrating audit gates and cost budgets into the lifecycle. This monitors execution, detects context contamination, and prevents runaway spending.

Can I audit an existing multi-agent workflow for failure-mode mitigations?

Yes, you can audit an existing multi-agent workflow to detect failure modes like claim races and context contamination. The process evaluates your current setup and recommends correct coordination patterns and reliability controls.