メニュー
Use when creating new agents. Trigger with agent spawn requests, pre-flight validation, or new agent creation. 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-spawning |
| description | Use when creating new agents. Trigger with agent spawn requests, pre-flight validation, or new agent creation. 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 |
Creates new agent instances with OAuth validation, plugin setup, and registry registration.
ai-maestro-agents-management and agent-messaging skills availableaimaestro-teams.sh list CLICopy this checklist and track your progress:
gh auth status 2>&1 | grep -q "project" || echo "ERROR: Missing project scope"
Required: repo, project, read:project. If missing, request human to run gh auth refresh -h github.com -s project,read:project. Do NOT proceed if scopes are missing.
amcos-permission-management skill. BLOCK until approved.<role-prefix>-<project>-<descriptive> (must be unique)$HOME/.claude/plugins/cache/ai-maestro/<plugin>/<latest>/ to $HOME/agents/<session>/.claude/plugins/<plugin>/ai-maestro-agents-management skill with args: --dangerously-skip-permissions --chrome --add-dir /tmp --plugin-dir <path> --agent <agent-name>uv run python scripts/amcos_team_registry.py add-agentagent-messaging skill| Role | --agent Flag Value |
|---|---|
| Orchestrator | ai-maestro-orchestrator-main-agent |
| Architect | ai-maestro-architect-main-agent |
| Integrator | ai-maestro-integrator-main-agent |
| Programmer | ai-maestro-programmer-main-agent |
| Step | Expected Output |
|---|---|
| Pre-flight | OAuth scopes confirmed |
| Spawn | tmux session created, agent running |
| Registry | Agent registered as "running" |
| Issue | Resolution |
|---|---|
| OAuth scopes missing | Block spawn, request human gh auth refresh |
| Plugin validation failed | Verify cache exists at source path |
| Session name collision | Choose different unique name |
| Resource limit exceeded | Queue request, hibernate oldest idle |
# 1. Verify scopes
gh auth status 2>&1 | grep -q "project" && echo "OK"
# 2. Copy plugin
cp -r ~/.claude/plugins/cache/ai-maestro/ai-maestro-programmer-agent/latest/* \
~/agents/ampa-svgbbox-impl/.claude/plugins/ai-maestro-programmer-agent/
# 3. Create via ai-maestro-agents-management skill:
# Name: ampa-svgbbox-impl, Dir: ~/agents/ampa-svgbbox-impl/
# Args: --agent ai-maestro-programmer-main-agent
# 4. Register + send welcome message
Copy this checklist and track your progress: