メニュー
Use when implementing inter-agent messaging or design document protocols. Trigger with communication pattern or messaging request. Loaded by ai-maestro-architect-agent-main-agent
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when decomposing systems into modules with clear boundaries. Trigger with modularization or module boundary request. Loaded by ai-maestro-architect-agent-main-agent
Use when designing architectures, identifying risks, creating roadmaps, or breaking work into tasks. Trigger with planning or architecture design request. Loaded by ai-maestro-architect-agent-main-agent
Use when managing requirements, initializing plans, or approving transitions. Trigger with requirements analysis or plan initialization request. Loaded by ai-maestro-architect-agent-main-agent
Use when recording stack choices, constraints, or managing handoffs. Trigger with session memory ops request. Loaded by ai-maestro-architect-agent-main-agent
Use when persisting decisions, patterns, and constraints across sessions. Trigger with session memory or handoff request. Loaded by ai-maestro-architect-agent-main-agent
Use when managing design document states or lifecycle transitions. Trigger with design lifecycle or state transition request. Loaded by ai-maestro-architect-agent-main-agent
| name | amaa-design-communication-patterns |
| description | Use when implementing inter-agent messaging or design document protocols. Trigger with communication pattern or messaging request. Loaded by ai-maestro-architect-agent-main-agent |
| context | fork |
| agent | ai-maestro-architect-agent-main-agent |
| user-invocable | false |
Centralizes communication patterns, messaging protocols, and design document standards. Requires AI Maestro running.
references/ directoryreferences/Copy this checklist and track your progress:
All shared resources are reference documentation files located in the references/ directory:
| Reference | Description |
|---|---|
| ai-maestro-message-templates.md | 1.1 Sending Acknowledgment When Receiving Design Request from AMCOS, 1.2 Requesting Clarification from AMCOS for Ambiguous Requirements, 1.3 Reporting Design Completion to AMCOS, 1.4 Notifying AMCOS That Handoff Document is Ready for AMOA, 1.5 Reporting Blocker That Prevents Design Progress, 1.6 Verifying ACK Receipt After Sending a Message, Example: Complete Message Send and Verify Workflow |
| message-response-decision-tree.md | Step 1: Priority Triage, Step 2: Message Type Routing, Step 3: Response Actions, Step 4: ACK Protocol |
| design-document-protocol.md | Document UUID Format (GUUID), Required Frontmatter Schema, Document Lifecycle, Validation Procedures, Search Procedures, GitHub Integration, Edge Cases and Error Handling, File Naming Convention, Cross-Plugin Protocol, Quick Reference |
| proactive-handoff-protocol.md | Standard Handoff Format, Automatic Handoff Triggers, Handoff Document Location, Mandatory Handoff Sections, Context, Progress, Current State, Blockers (if any), Next Steps, References, Proactive Writing Rules, Handoff Quality Checklist |
| task-completion-checklist.md | Before Reporting Task Complete, Verification Loop, Common Traps (Architect-Specific), Completion Report Format, Pre-Completion Checklist for Architects, When to Escalate vs Complete |
Example: Use ai-maestro-message-templates.md for standard message formats
| Error | Solution |
|---|---|
| Reference not found | Verify file exists in references/ |
| Message delivery failed | Ensure AI Maestro API is reachable |
| Handoff rejected | See edge-case-protocols.md for resolution steps |
Protocol guidance, message templates, decision trees, and checklists as Markdown reference docs.