By emasoft
Multi-project agent management - staff planning, lifecycle, approval workflows, failure recovery. Requires AI Maestro for inter-agent messaging.
Add a new project to Chief of Staff management
Assign an agent to a managed project and send onboarding message
Send notification to multiple agents simultaneously with filtering by role or project
Check status of pending approval requests from EAMA
Configure plugins for an agent's project by adding, removing, or managing plugin scope
Manages approval requests and coordinates with manager. Requires AI Maestro installed.
Chief of Staff main agent - manages remote agents across projects. Requires AI Maestro installed.
Manages agent lifecycle - spawn, terminate, hibernate, wake. Requires AI Maestro installed.
Analyzes agent performance and reports strengths/weaknesses. Requires AI Maestro installed.
Configures plugins locally for each agent in their project folders. Requires AI Maestro installed.
Use when spawning, terminating, hibernating, or waking agents. Trigger with agent spawn, termination, or hibernation requests.
Use when recovering from agent failures or coordinating agent replacements. Trigger with failure events.
Use when applying or checking GitHub labels for agent assignment and status tracking. GitHub label taxonomy reference for the Chief of Staff Agent. Trigger with `/ecos-label-taxonomy`.
Use when managing multiple projects simultaneously, tracking project states, syncing with GitHub Projects, or coordinating cross-project dependencies. Trigger with multi-project coordination requests.
Use when notifying agents about upcoming operations, requesting acknowledgments before proceeding, or sending failure notifications after operation errors. Trigger with notification or alert events.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Version: 1.2.0
The Emasoft Chief of Staff (ECOS) manages remote agents across multiple projects. It handles staff planning, agent lifecycle, approval workflows, failure recovery, and coordinates with the Assistant Manager (EAMA) and Orchestrator (EOA).
Key Role: ECOS is responsible for keeping agents ready and correctly configured. It must notify the manager (EAMA) after every change, and request approval for critical operations.
See docs/ROLE_BOUNDARIES.md for complete role definitions.
ECOS is organization-wide - there is ONE Chief of Staff managing agents across ALL projects.
| Aspect | ECOS (Chief of Staff) | EOA (Orchestrator) |
|---|---|---|
| Scope | Organization-wide (ONE) | Project-linked (ONE per project) |
| Manages | Agent EXISTENCE | Agent WORK |
| Creates | Agents, teams | Task assignments |
| Owns | Agent registry | GitHub Project kanban |
| Question answered | "Who exists?" | "Who does what?" |
This plugin uses two skills for agent and messaging operations:
ai-maestro-agents-management skill - For all agent lifecycle operations (create, terminate, hibernate, wake, install plugins, list agents, check health)agent-messaging skill - For all inter-agent communication (send messages, check inbox, broadcast notifications, approval requests)IMPORTANT: When spawning agents, always include the standard Claude Code flags as program arguments:
| Argument | Purpose |
|---|---|
continue | Resume previous session context |
--dangerously-skip-permissions | Skip permission dialogs for automation |
--chrome | Enable Chrome DevTools integration |
--add-dir <TEMP> | Add temp directory access |
Platform-specific temp directories:
/tmp%TEMP% or C:\Users\<user>\AppData\Local\Temp┌─────────────────────────────────────────────────────────────────┐
│ USER │
└─────────────────────┬───────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ EAMA (Assistant Manager) │
│ - User's right hand, sole interlocutor │
│ - Approves/rejects ECOS requests │
└──────┬──────────────────────────────────────────────────────────┘
│ requests approval, reports status
▼
┌─────────────────────────────────────────────────────────────────┐
│ ECOS (Chief of Staff) │
│ - Manages agent lifecycle │
│ - Coordinates approvals and notifications │
│ - Handles failure recovery │
└──────┬─────────────────────┬─────────────────────┬──────────────┘
│ │ │
▼ ▼ ▼
ARCHITECT ORCHESTRATOR INTEGRATOR
(EAA) (EOA) (EIA)
Note: ECOS does NOT manage tasks or kanban boards. When a new agent is created or an agent is replaced, ECOS notifies EOA so that EOA can handle task (re)assignment.
Task distribution, agent coordination, progress monitoring - executes plans via subagents. Requires AI Maestro for inter-agent messaging.
Comprehensive validation, management, and standardization suite for Claude Code plugins and marketplaces. Includes 190+ validation rules, plugin lifecycle management, marketplace operations, health checks, security auditing, GitHub repo validation, plugin/marketplace repo scaffolding, and standardization tooling. Features severity hierarchy, --strict mode, language-aware token estimation, and universal plugin/marketplace templates.
GHE (GitHub-Elements) - Automated project management for Claude Code using GitHub Issues as persistent memory with orchestrated DEV/TEST/REVIEW workflow.
Portable utility tools for Claude Code plugin marketplaces. Includes release automation and markdown TOC generation.
Exports current session segment (since last compaction) with system-reminder stripping -- main conversation, subagent transcripts, sidechains, and debug logs in structured markdown
npx claudepluginhub emasoft/emasoft-plugins --plugin emasoft-chief-of-staffInstall a customised team of AI agents — a chief-of-staff orchestrator that routes to division leads and specialists — tailored to your own business, departments, or the people you manage. Works with Claude Code and Codex.
Task distribution, agent coordination, progress monitoring - executes plans via subagents. Requires AI Maestro for inter-agent messaging.
AI Agent Team Operating System for Claude Code — persistent team management, meetings, task wall, company loop engine, and real-time dashboard
Agent team management - create, expand, and cleanup teams for worktree sessions
Multi-agent coordination with agent-swarm MCP
Universal multi-agent collaboration framework — channels, DMs, tasks, state, inbox