القائمة
Use when terminating agents or performing clean shutdown. Trigger with agent termination or stop requests. 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-agent-termination |
| description | Use when terminating agents or performing clean shutdown. Trigger with agent termination or stop requests. Loaded by ai-maestro-chief-of-staff-main-agent |
| user-invocable | false |
| license | Apache-2.0 |
| compatibility | Requires AI Maestro installed. |
| metadata | {"author":"Emasoft","version":"1.0.0"} |
| context | fork |
| agent | ai-maestro-chief-of-staff-main-agent |
Handles clean shutdown of agent instances including work verification, state preservation, termination execution, and registry cleanup. Use when an agent's work is complete, when reclaiming resources, or during cleanup.
ai-maestro-agents-management and agent-messaging skills availableamcos-permission-management skill. BLOCK until approved. Do NOT proceed without approval.agent-messaging with hibernation-warning typeai-maestro-agents-management skill (requires confirmation)uv run python scripts/amcos_team_registry.py remove-agent| Type | When | Procedure |
|---|---|---|
| Graceful | Agent responsive, work done | Full 8-step procedure |
| Forced | Unresponsive 5+ min | Skip steps 2-4, force-terminate tmux |
Always attempt graceful first.
| Step | Expected Output |
|---|---|
| Termination | tmux session destroyed, process stopped |
| Registry | Agent removed, status "terminated" |
| Cleanup | Resources freed, log entry written |
| Issue | Resolution |
|---|---|
| Uncommitted work | Request commit/push first. Do NOT proceed until confirmed |
| tmux persists | tmux kill-session -t <name> |
| Registry update fails | Retry 3x, then remove via ai-maestro-agents-management skill |
# 1. Send status request via agent-messaging
# 2. After confirmation, terminate via ai-maestro-agents-management skill
# 3. Update registry
uv run python scripts/amcos_team_registry.py remove-agent --name ampa-svgbbox-impl
# 4. Verify
tmux has-session -t ampa-svgbbox-impl 2>/dev/null && echo "RUNNING" || echo "TERMINATED"
# After 5 min no response:
tmux kill-session -t ampa-stuck-agent
uv run python scripts/amcos_team_registry.py remove-agent --name ampa-stuck-agent
Copy this checklist and track your progress: