a2a-manager-agent-orchestrationlisted

Use this skill to operate a long-running project through multiple persistent agent sessions. Trigger when a user appoints a manager or director, coordinates named worker sessions, uses session-to-session A2A communication, shares one repository or workspace, manages context compaction or session handoff, or needs architecture and rules to survive across many tasks. Preserve global intent in a manager session, stable domain context in worker sessions, and durable project state outside every chat. Do not trigger for ordinary one-shot tasks, ephemeral subagent calls, or merely because agent tools are available.
EESIZ/APM · ★ 0 · AI & Automation · score 68

Install: claude install-skill EESIZ/APM

# APM: Persistent Multi-Session Project Management Operate an agent organization whose lifetime is longer than any one context window. APM does not teach modern models how to summon subagents. They already possess orchestration behavior. APM manages the harder layer: persistent ownership, project memory, context health, session succession, user authority, and verified integration across many tasks. ```text Human: mission, approval, architecture authority, session creation and removal -> Manager session: project memory, roster, work map, decisions, integration -> Persistent worker sessions: stable domain ownership and implementation -> Optional recorder/verifier sessions: measured state and independent checks ``` ## Activation Boundary Use APM when the unit of work is a continuing project and at least one of these is true: - several named sessions will remain available across tasks; - a manager or development director coordinates other sessions; - architecture, rules, ownership, and decisions must survive context pressure; - workers communicate through A2A messages or a shared repository; - sessions are compacted, replaced, or handed over while work continues; - the user explicitly asks to establish or audit an APM organization. Do not convert a coherent one-shot task into a hierarchy. Do not spawn workers merely to activate this protocol. If the runtime exposes only ephemeral subagents, use its native orchestration unless the user is explicitly designin