メニュー
Use when notifying agents about upcoming operations before execution. Trigger with pre-operation notification or pre-flight alert needs. 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-pre-op-notification |
| description | Use when notifying agents about upcoming operations before execution. Trigger with pre-operation notification or pre-flight alert needs. Loaded by ai-maestro-chief-of-staff-main-agent |
| user-invocable | false |
| license | Apache-2.0 |
| compatibility | Requires access to AI Maestro messaging system. Requires AI Maestro installed. |
| metadata | {"author":"Emasoft","version":"1.0.0"} |
| context | fork |
| agent | ai-maestro-chief-of-staff-main-agent |
Pre-operation notifications warn agents about upcoming disruptive operations before they happen. This ensures agents have time to save work and acknowledge readiness via AMP protocol.
amp-init.sh --autoamp-send.sh exclusively. Never call HTTP API directly.amp-send.sh.amp-init.sh --auto once per agent.| Direction | Rule |
|---|---|
| Team member -> MANAGER | COS intercepts, reviews, forwards via AMP |
| Team member -> external | COS checks reachability rules, forwards if allowed |
| External -> team member | Must go through COS or MANAGER |
Before sending, validate recipient against aimaestro-teams.sh list. Block and log violations.
When to use: Before skill or plugin installation, agent restart, configuration changes, or any disruptive operation.
Workflow:
aimaestro-teams.sh listamp-send.sh exclusivelyCopy this checklist and track your progress:
amp-send.shSee op-pre-operation-notification in Resources
| Type | Output |
|---|---|
| Pre-operation alert | Notification sent, delivery confirmed |
| Broadcast warning | Message sent to own-team agents, receipt logged |
| Issue | Resolution |
|---|---|
| Not delivered | Check agent registration, verify AMP initialized. See references Section 1.7 |
| Agent unreachable | Health check, retry after 10s |
| Team violation | Validate against aimaestro-teams.sh list before sending |
| AMP signing failure | Re-run amp-init.sh --auto |
Input: Skill install scheduled for agent code-impl-auth in 30s
amp-send.sh code-impl-auth "Pre-Op: Skill Install in 30s" \
"Upcoming skill installation. Expected downtime: 30s. Please save work and reply ok."
Expected result: Agent receives notification and replies "ok" within 60s; operation proceeds.