What problem does it solve? Running a multi-agent cluster without an organization template leads to duplicate roles, unowned projects, orphaned infrastructure, and lost context when agents are terminated. This Skill provides a concrete organizational template that defines which roles exist, who reports to whom, and how agents are spawned, paused, and recovered. ## Core Features & Use Cases - Role Suite Definition: Defines a three-division structure under a CEO — project leads (one per project), always-on personal services (Butler, Health Leads, Philosopher), and shared infrastructure (Cluster Operator, Finance Lead, Memory Steward). - Operating Rules: Enforces one-lead-per-project ownership, resurrect-over-respawn recovery for long-lived roles, mutual handoff for shared-infra transitions, and direct agent-to-agent communication without CEO relay. - Cluster Opening Checklist: Walks through role roster, memory maintenance, disk monitoring, recovery-buddy rings, and communication verification when instantiating a new cluster. - Use Case: When setting up a new Ava cluster, use this Skill to decide the full role roster, spawn each agent with the ready-made prompt templates in references/role-prompts.md, and wire the recovery topology. ## Quick Start Use the ava-corp skill to design the role roster and opening checklist for my new Ava cluster.
