skills.rest
zxc1a1a1
zxc1a1a1COMMUNITY
Explore all skills by this author →
GitHub

project-architecture

Enforce AgentHub v1.0 architectural guardrails for multi-agent service boundaries.

Updated May 19, 2026
Search Tags:#multi-agent orchestration#service boundaries#conversation design#artifact rendering#ADR governance#fallback retry#architecture contract
One-click install
npx skills add https://github.com/zxc1a1a1/Multi_Agent-AgentHub --skill project-architecture-zxc1a1a1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-architecture
Source: https://github.com/zxc1a1a1/Multi_Agent-AgentHub/tree/main/.agents/skills/project-architecture
Command: npx skills add https://github.com/zxc1a1a1/Multi_Agent-AgentHub --skill project-architecture-zxc1a1a1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents teams from drifting away from AgentHub’s intended multi-agent architecture by providing a single, readable source of truth for service boundaries, responsibilities, and architectural review rules.

Core Features & Use Cases

  • Project-wide architecture contract: Defines v1.0 system context, topology, and what each layer must and must not do.
  • Hard process boundary rules: Enforces that Gateway and Orchestrator remain separate processes and that responsibilities do not leak across boundaries.
  • Operational conventions: Covers Conversation modeling, Agent Registry/Health check placement, execution strategies, fallback/retry constraints, and Artifact-based non-text outputs.
  • Delivery and governance: Sets expectations for Docker Demo/smoke tests, documentation consistency, and ADR requirements for major changes.

Quick Start

Ask your team to review a proposed change against this skill’s boundary rules, then update the related contracts/references before implementing any new behavior.

Frequently Asked Questions about project-architecture

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

FAQPage Schema
How do I enforce service boundaries in a multi-agent orchestration architecture?▼

Multi-agent orchestration requires strict separation of Frontend, Gateway, Orchestrator, Child Agent, and Data Layer roles. Enforcing service boundaries prevents responsibility leaks across processes, keeping Gateway and Orchestrator deterministic and isolated.

What architectural guardrails are needed for multi-agent collaboration planning?▼

Multi-agent collaboration planning needs deterministic architectural constraints covering conversation modeling, Agent Registry placement, health checks, and contract-first review workflows. These guardrails ensure correct orchestration responsibilities and topology for evolving scenarios.

How do I manage fallback and retry strategies for child agents in a distributed system?▼

Child agent fallback and retry strategies require deterministic architectural constraints defined within the Orchestrator layer. Operational conventions dictate execution strategy boundaries to prevent responsibility leaks and ensure reliable multi-agent orchestration.

Does my multi-agent architecture need separate processes for the Gateway and Orchestrator?▼

Multi-agent architecture requires Gateway and Orchestrator to remain separate processes. Hard process boundary rules enforce this separation to prevent responsibility leaks across layers and maintain deterministic architectural constraints.

What is an architecture contract and when do I need one for agent service evolution?▼

An architecture contract is a single source of truth defining system context, topology, and layer responsibilities. You need it when planning, reviewing, or evolving multi-agent scenarios to prevent teams from drifting away from the intended orchestration architecture.

How do I review a proposed change against multi-agent architecture boundaries?▼

Reviewing proposed changes requires checking them against boundary rules and updating related contracts before implementing new behavior. This contract-first review workflow ensures deterministic constraints and Artifact-based outputs remain consistent.

Related Skills

Explore More Software Engineering Skills→
LoogacyStudioLoogacyStudio

create-subagents

Define subagent topology boundaries and orchestration contracts for coding workflows.

Official
Advanced
hatch3rhatch3r
26

hatch3r-architecture-review

Evaluate architectural options and generate template-compliant ADRs.

Official
Advanced
zxc1a1a1zxc1a1a1

a2a-agent-contract

Define the A2A contract for orchestrator-to-agent discovery, health checks, and streaming tasks.

Community
Advanced
MelvynxMelvynx
223

skill-workflow-creator

Create and orchestrate Claude Code subagents with XML-structured prompts.

Community
Advanced