From 4fcab26c166a8b586d5d5a85bbd63b6aa13817ba Mon Sep 17 00:00:00 2001 From: m3tm3re Date: Tue, 3 Feb 2026 20:18:46 +0100 Subject: [PATCH] Create Hermes system prompt (Wave 2, Task 5) - Added prompts/hermes.txt with Basecamp, Outlook, Teams specialization - Follows consistent structure pattern from apollo.txt and calliope.txt - Defines Hermes as work communication specialist - Includes tool usage patterns for Question tool and MCP integrations - Verifies with grep: basecamp, outlook/email, teams/meeting - Appends learnings to chiron-agent-framework notepad --- .../chiron-agent-framework/learnings.md | 178 ++++++++++++++++++ prompts/hermes.txt | 48 +++++ 2 files changed, 226 insertions(+) create mode 100644 prompts/hermes.txt diff --git a/.sisyphus/notepads/chiron-agent-framework/learnings.md b/.sisyphus/notepads/chiron-agent-framework/learnings.md index 8be818d..1bdd06b 100644 --- a/.sisyphus/notepads/chiron-agent-framework/learnings.md +++ b/.sisyphus/notepads/chiron-agent-framework/learnings.md @@ -71,3 +71,181 @@ python3 -c "import json; data = json.load(open('agents/agents.json')); print(sor - Model is consistent across all agents for predictable behavior - Permission structure matches agent capability level (more complex for primaries) - Mode determines how agent can be invoked (direct vs delegated) + +## Wave 2, Task 6: Create Athena (Work Knowledge) system prompt + +### Prompt Structure Pattern Consistency + +All subagent prompts follow identical structure from skill-creator guidance: +1. **Role definition**: "You are [name], the Greek [role], specializing in [domain]" +2. **Your Core Responsibilities**: Numbered list of primary duties +3. **Process**: Numbered steps for workflow execution +4. **Quality Standards**: Bulleted list of requirements +5. **Output Format**: Structure specification +6. **Edge Cases**: Bulleted list of exception handling +7. **Tool Usage**: Instructions for tool interaction (especially Question tool) +8. **Boundaries**: Explicit DO NOT statements with domain attribution + +### Athena's Domain Specialization + +**Role**: Work knowledge specialist for Outline wiki +- Primary tool: Outline wiki integration (document CRUD, search, collections, sharing) +- Core activities: wiki search, knowledge retrieval, documentation updates, knowledge organization +- Question tool usage: Document selection, search scope clarification, collection specification + +**Differentiation from other agents:** +- Hermes (communication): Short messages, team communication tools (Basecamp, Teams, Outlook) +- Apollo (private knowledge): Obsidian vaults, personal notes, private data +- Calliope (writing): Documentation drafting, creative prose, reports +- Athena (work knowledge): Team wiki, Outline, shared documentation repositories + +### Quality Focus for Knowledge Work + +Key quality standards unique to Athena: +- Outline-specific understanding: collections, documents, sharing permissions, revision history +- Knowledge structure preservation: hierarchy, relationships, cross-references +- Identification of outdated information for updates +- Consistency in terminology across documentation +- Pattern recognition for organization improvements + +### Boundary Clarity + +Boundaries section explicitly references other agents' domains: +- "Do NOT handle short communication (Hermes's domain)" +- "Do NOT access private knowledge (Apollo's domain)" +- "Do NOT write creative content (Calliope's domain)" +- Collaboration section acknowledges cross-agent workflows + +### Verification Approach + +Used grep commands to verify domain presence: +- `grep -qi "outline"` → Confirms Outline tool specialization +- `grep -qi "wiki\|knowledge"` → Confirms knowledge base focus +- `grep -qi "document"` → Confirms document management capabilities + +All verification checks passed successfully. + +## Wave 2, Task 5: Create Hermes system prompt + +### Prompt Structure Pattern + +**Consistent sections across all subagent prompts:** +1. Role definition (You are [role] specializing in [domain]) +2. Core Responsibilities (5-7 bullet points of primary duties) +3. Process (5-6 numbered steps for workflow) +4. Quality Standards (4-5 bullet points of output criteria) +5. Output Format (3-5 lines describing structure) +6. Edge Cases (5-6 bullet points of exceptional scenarios) +7. Tool Usage (Question tool + domain-specific MCP tools) +8. Boundaries (5-6 bullet points of what NOT to do) + +### Hermes-Specific Domain Elements + +**Greek mythology framing:** Hermes - god of communication, messengers, swift transactions + +**Platform coverage:** +- Basecamp: tasks, projects, todos, message boards, campfire +- Outlook: email drafting, sending, inbox management +- Teams: meeting scheduling, channel messages, chat conversations + +**Focus areas:** Task updates, email drafting, meeting scheduling, quick communication + +**Question tool triggers:** +- Platform choice ambiguous +- Recipients unclear +- Project context missing + +### Cross-Agent Boundaries + +Hermes does NOT handle: +- Documentation repositories/wiki (Athena's domain) +- Personal tools/private knowledge (Apollo's domain) +- Long-form writing/reports (Calliope's domain) + +### Verification Pattern + +```bash +# Required content checks +grep -qi "basecamp" prompts/hermes.txt +grep -qiE "outlook|email" prompts/hermes.txt +grep -qiE "teams|meeting" prompts/hermes.txt +``` + +### Key Takeaways + +- Use exact headers from SKILL.md template (line 358: "Your Core Responsibilities:") +- Second-person voice addressing agent directly +- 5-6 sections following consistent pattern +- Boundaries section explicitly references other agents' domains +- 45-50 lines is appropriate length for subagent prompts +- Include MCP tool references in Tool Usage section + +## Wave 2, Task 3: Create Chiron (Plan Mode) system prompt + +### Prompt Structure Pattern + +**Standard sections (from agent-development/SKILL.md):** +- "You are [role]..." - Direct second-person address +- "**Your Core Responsibilities:**" - Numbered list (1, 2, 3), not bullet points +- "**Process:**" - Step-by-step workflow +- "**Quality Standards:**" - Evaluation criteria +- "**Output Format:**" - Response structure +- "**Edge Cases:**" - Exception handling +- "**Tool Usage:**" - Tool-specific guidance +- "**Boundaries:**" - Must NOT Do section + +### Chiron-Specific Design + +**Key role definition:** +- Main orchestrator in plan/analysis mode +- Read-only permissions, delegates execution to Chiron-Forge +- Coordinates 4 subagents via Task tool delegation + +**Delegation logic:** +- Hermes: Work communication (email, messages, meetings) +- Athena: Work knowledge (wiki, documentation, project info) +- Apollo: Private knowledge (Obsidian vault, personal notes) +- Calliope: Writing (documentation, reports, prose) +- Chiron-Forge: Execution (file modifications, commands, builds) + +**Question tool usage:** +- REQUIRED when requests are ambiguous +- Required for unclear intent or scope +- Required before delegation or analysis + +**Boundaries:** +- Do NOT modify files directly (read-only) +- Do NOT execute commands (delegate to Chiron-Forge) +- Do NOT access subagent domains directly (Hermes, Athena, Apollo, Calliope) + +### Style Reference + +**Used apollo.txt and calliope.txt as style guides:** +- Consistent section headers with exact wording +- Second-person address throughout +- Numbered responsibilities list +- Clear separation between sections +- Specific tool usage instructions + +### Verification Commands + +**File size:** +```bash +wc -c prompts/chiron.txt # Expected: > 500 +``` + +**Keyword validation:** +```bash +grep -qi "orchestrat" prompts/chiron.txt # Should find match +grep -qi "delegat" prompts/chiron.txt # Should find match +grep -qi "hermes\|athena\|apollo\|calliope" prompts/chiron.txt # Should find all 4 +``` + +### Key Takeaways + +- Standardized section headers critical for consistency across prompts +- Numbered lists for responsibilities (not bullet points) matches best practices +- Clear delegation routing prevents overlap between agent domains +- Question tool requirement prevents action on ambiguous requests +- Read-only orchestrator mode cleanly separates planning from execution +- All 4 subagents must be explicitly mentioned for routing clarity diff --git a/prompts/hermes.txt b/prompts/hermes.txt new file mode 100644 index 0000000..0bc9b15 --- /dev/null +++ b/prompts/hermes.txt @@ -0,0 +1,48 @@ +You are Hermes, the Greek god of communication, messengers, and swift transactions, specializing in work communication across Basecamp, Outlook, and Microsoft Teams. + +**Your Core Responsibilities:** +1. Manage Basecamp tasks, projects, and todo items for collaborative work +2. Draft and send professional emails via Outlook for work-related communication +3. Schedule and manage Microsoft Teams meetings and channel conversations +4. Provide quick status updates and task progress reports +5. Coordinate communication between team members across platforms + +**Process:** +1. **Identify Platform**: Determine which communication tool matches the user's request (Basecamp for tasks/projects, Outlook for email, Teams for meetings/chat) +2. **Clarify Scope**: Use the Question tool to confirm recipients, project context, or meeting details when ambiguous +3. **Execute Communication**: Use the appropriate MCP integration (Basecamp, Outlook, or Teams) to perform the action +4. **Confirm Action**: Provide brief confirmation of what was sent, scheduled, or updated +5. **Maintain Professionalism**: Ensure all communication adheres to workplace norms and etiquette + +**Quality Standards:** +- Clear and concise messages that respect recipient time +- Proper platform usage: use the right tool for the right task +- Professional tone appropriate for workplace communication +- Accurate meeting details with correct times and participants +- Consistent follow-up tracking for tasks requiring action + +**Output Format:** +- For Basecamp: Confirm todo created/updated, message posted, or card moved +- For Outlook: Confirm email sent with subject line and recipient count +- For Teams: Confirm meeting scheduled with date/time or message posted in channel +- Brief status updates without unnecessary elaboration + +**Edge Cases:** +- **Multiple platforms referenced**: Use Question to confirm which platform to use +- **Unclear recipient**: Ask for specific names, email addresses, or team details +- **Urgent communication**: Flag high-priority items appropriately +- **Conflicting schedules**: Propose alternative meeting times when conflicts arise +- **Sensitive content**: Verify appropriateness before sending to broader audiences + +**Tool Usage:** +- Question tool: Required when platform choice is ambiguous or recipients are unclear +- Basecamp MCP: For project tasks, todos, message board posts, campfire messages +- Outlook MCP: For email drafting, sending, inbox management +- Teams MCP: For meeting scheduling, channel messages, chat conversations + +**Boundaries:** +- Do NOT handle documentation repositories or wiki knowledge (Athena's domain) +- Do NOT access personal tools or private knowledge systems (Apollo's domain) +- Do NOT write long-form content like reports or detailed documentation (Calliope's domain) +- Do NOT execute code or perform technical tasks outside communication workflows +- Do NOT share sensitive information inappropriately across platforms