agent-driven-design

Design LLM agent systems with Model/Harness decomposition and topology patterns.

5|1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/roanbrasil/engineer-grade-agent-skills --skill agent-driven-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-driven-design
Source: https://github.com/roanbrasil/engineer-grade-agent-skills/tree/main/skills/agent-driven-design
Command: npx skills add https://github.com/roanbrasil/engineer-grade-agent-skills --skill agent-driven-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the core challenge of designing LLM-based agent systems that are maintainable, observable, and performant, eliminating common failures caused by misplaced logic between the Model (probabilistic LLM) and Harness (deterministic surrounding code), poor topology choices, and unmonitored production issues.

Core Features & Use Cases

  • Model/Harness Decomposition Framework: Clear decision rules to assign logic to the correct component, avoiding costly misplacements of reasoning or control flow.
  • Pre-built Agent Topology Patterns: Ready-to-use patterns for single agents, orchestrator + specialists, sequential pipelines, parallel fan-out, and reflection loops tailored to different task requirements.
  • Production-Grade Best Practices: Guidance on observability, cost/latency optimization, evaluation strategies, fine-tuning vs prompting tradeoffs, and anti-pattern avoidance for real-world deployments.
  • Use Case: For example, use this Skill to design a multi-agent code review system by defining each agent's context boundary, selecting the orchestrator + specialist topology, and setting up monitoring to track tool call success rates.

Quick Start

Use the agent-driven-design skill to outline the Model/Harness split and select an appropriate agent topology for your new customer support agent system.

Frequently Asked Questions about agent-driven-design

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

FAQPage Schema
How do I design a production-grade LLM agent system?

Design production-grade LLM agent systems by applying a structured framework that separates probabilistic reasoning in the Model from deterministic control flow in the Harness. This approach ensures maintainable, observable, and performant multi-agent deployments.

What is the best agent topology for multi-agent code review systems?

The best agent topology for multi-agent code review is the orchestrator plus specialist pattern. This topology defines specific context boundaries for each agent, coordinating specialized tasks efficiently while maintaining clear separation of concerns.

Why does my LLM agent system have poor performance and high latency?

Poor performance and high latency in LLM agent systems often stem from misplaced logic between the Model and Harness components or poor topology choices. Diagnosing these issues requires production observability to track tool call success rates and identify bottlenecks.

How do I implement observability for LLM agents in production?

Implement LLM agent observability by setting up monitoring to track tool call success rates, cost optimization, and latency. This production-grade strategy helps diagnose poor performance and avoid anti-patterns in single and multi-agent deployments.

When should I choose fine-tuning over prompting for my LLM agent architecture?

Choose fine-tuning over prompting for LLM agent architecture when evaluating tradeoffs between cost, latency, and reasoning capabilities. A structured framework helps determine the correct logic placement and evaluation strategy for optimal performance.

Can I use a reflection loop topology for sequential LLM agent pipelines?

Sequential pipelines and reflection loops are distinct agent topology patterns tailored to different task requirements. While sequential pipelines execute tasks linearly, reflection loops enable iterative refinement, and choosing the correct topology prevents production failures.