system-design

Define agent boundaries, orchestration patterns, and tool assignments for multi-agent systems.

2|2|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/srulyt/srulys-agent-packs --skill system-design-srulyt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-design
Source: https://github.com/srulyt/srulys-agent-packs/tree/main/.roo/skills/system-design
Command: npx skills add https://github.com/srulyt/srulys-agent-packs --skill system-design-srulyt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides essential domain knowledge and principles for designing robust and efficient multi-agent systems, helping users architect agent boundaries, orchestration patterns, and tool assignments.

Core Features & Use Cases

  • Agent Boundary Definition: Learn principles for creating clear, non-overlapping agent responsibilities.
  • Orchestration Strategies: Understand trade-offs between central orchestrators and direct agent-to-agent communication.
  • Tool Assignment Rationale: Get guidance on assigning tools like edit, command, and read based on agent tasks.
  • Use Case: When designing a new AI agent pack, use this skill to determine the optimal number of agents, their specific roles, and how they should communicate to achieve a complex goal.

Quick Start

Use the system-design skill to understand how to define agent boundaries.

Frequently Asked Questions about system-design

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

FAQPage Schema
How do I design effective boundaries for multi-agent systems?

Designing effective boundaries for multi-agent systems requires creating clear, non-overlapping agent responsibilities. This approach ensures each agent handles specific tasks without conflicting with other agents in the workflow.

What is the best way to orchestrate communication between AI agents?

Orchestrating AI agents involves understanding trade-offs between central orchestrators and direct agent-to-agent communication. Central orchestrators offer structured control, while direct communication allows faster, decentralized interactions.

How do I assign tools like edit, command, and read to specific agents?

Assigning tools like edit, command, and read requires evaluating specific agent tasks within the multi-agent architecture. Tool assignment rationale ensures agents only access the capabilities needed to achieve their goals.

Do I need prior software architecture experience to design multi-agent systems?

Yes, designing multi-agent systems requires understanding of agentic workflows and system design principles. This Skill targets software architects and AI engineers defining system structures and agent interactions.

When should I use a central orchestrator instead of direct agent-to-agent communication?

Use a central orchestrator when structured control and error handling are critical for multi-agent workflows. Choose direct agent-to-agent communication when you need faster, decentralized interactions without central bottlenecks.

How do I handle errors in multi-agent AI architectures?

Handling errors in multi-agent AI architectures involves defining clear agent boundaries and applying orchestration patterns. Proper error handling ensures robust system structures when agents fail to complete assigned tasks.