メニュー
Use when onboarding new agents to the team, providing role briefings, conducting project handoffs, and ensuring agents are ready to contribute effectively. Trigger with new agent or new project setup. Loaded by ai-maestro-chief-of-staff-main-agent
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when applying or checking GitHub labels for agent assignment and status tracking. Trigger with label management or taxonomy lookup requests. Loaded by ai-maestro-chief-of-staff-main-agent
CHIEF-OF-STAFF's role in the PRRD / TRDD / Kanban workflow. COS does NOT own kanban columns directly — it ROUTES messages and proposals between the team layer (ORCH/ARCH/INT/MEMBER) and the governance layer (MANAGER). Use when COS forwards a PRRD proposal, relays approval decisions, broadcasts TRDD status updates, or aggregates team status for AMAMA.
Use when sending failure notifications after operation errors. Trigger with failure events, error reporting, or incident notification. Loaded by ai-maestro-chief-of-staff-main-agent
Use when managing team registry, inter-agent messaging, role boundaries, or sub-agent delegation. Trigger with team coordination tasks. Loaded by ai-maestro-chief-of-staff-main-agent
Use when requesting or processing agent acknowledgments before proceeding with operations. Trigger with acknowledgment requests or ACK timeout handling. Loaded by ai-maestro-chief-of-staff-main-agent
Use when replacing a failed agent with a new instance. Trigger with agent replacement or failover events. Loaded by ai-maestro-chief-of-staff-main-agent
| name | amcos-onboarding |
| description | Use when onboarding new agents to the team, providing role briefings, conducting project handoffs, and ensuring agents are ready to contribute effectively. Trigger with new agent or new project setup. Loaded by ai-maestro-chief-of-staff-main-agent |
| user-invocable | false |
| license | Apache-2.0 |
| compatibility | Requires AI Maestro messaging API access, project documentation access, and role definition documents. Requires AI Maestro installed. |
| metadata | {"author":"Emasoft","version":"1.0.0"} |
| context | fork |
| agent | ai-maestro-chief-of-staff-main-agent |
Agent onboarding integrates new AI agents into a coordinated team. The Chief of Staff ensures each new agent understands their role, project context, key procedures, and communication channels.
Copy this checklist and track your progress:
| Onboarding Type | Output |
|---|---|
| New agent | Agent understands role and context |
| New project | Project registered, team assigned |
| Role change | Agent updated with new responsibilities |
When/Steps: Initiate session, verify identity, work through checklist items, confirm completion, document.
When/Steps: Retrieve role definition, explain responsibilities, clarify reporting, set expectations, confirm understanding.
When/Steps: Provide project overview, share current state, explain conventions, transfer knowledge, verify comprehension.
Validate handoff documents before sending using the validation checklist and scripts.
Input: "Onboard new agent libs-svg-renderer for SVG rendering tasks on project svg-player"
Output:
Onboarding libs-svg-renderer:
1. Role briefing sent: SVG renderer, reports to apps-svgplayer-development
2. Project handoff: svg-player repo, conventions, current sprint context
3. Agent confirmed ready. Registry updated.
[DONE] libs-svg-renderer onboarded successfully.
See onboarding-overview-and-examples in Resources for examples and handoff validation.
| Issue | Resolution |
|---|---|
| Agent does not respond | Verify session active, retry with higher priority, escalate if persistent |
| Agent confused by briefing | Provide specific examples, break down responsibilities, have agent repeat back |
| Handoff incomplete | Review checklist, identify gaps, send supplementary information |