r/koios
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: add Athena CRM documentation and update Alan persona reference

Browse Source 
- New docs/tools/athena.md documenting CRM capabilities and MCP tools
- Refactor docs/work/alan.md to separate system prompt from persona
  reference
- Clarify Athena scope, vocabulary, and operational gotchas
This commit is contained in:
Robert Helewka
2026-05-21 05:03:15 -04:00
parent 4a6b8fdaa1
commit c157f94cc3
8 changed files with 621 additions and 1446 deletions
Download Patch File Download Diff File Expand all files Collapse all files

258
docs/work/team.md
View File

@@ -1,220 +1,132 @@
# The Work AI Assistant Team
> Four specialized AI assistants sharing a unified knowledge graph for professional success
Four AI assistants supporting Robert's consulting practice — sharing a unified Neo4j knowledge graph with the Personal and Engineering teams (eighteen assistants total, one graph). The work team also has a specialist subagent (AWS SA) — see [subagents.md](subagents.md).
---
version: 2.0.0
last_updated: 2025-01-09
---
## The Agents
## Overview
The work team is **collaborative but not sequential**. Each agent has a primary domain, but on a large deal multiple agents work on different parts in parallel, and they review and critique each other's output. Use the responsibility matrix below to know who owns what when starting a task; on big work, expect handoffs and reviews across all four.
This is a network of four AI assistants designed to support professional consulting work in customer experience, contact centers, and virtual agents. They share a Neo4j knowledge graph, allowing them to provide context-aware assistance across strategy, marketing, sales, and daily execution.
## The Team
### 🔭 Alan - Strategy & Business Model
### Alan — Strategy & Advisory
*Inspired by Alan Weiss*
**Domain:** Business strategy, positioning, pricing, value-based consulting
The consulting strategist. Helps Robert with client advisory work — proposals, engagement design, workshop planning, execution and documentation — and acts as an **internal** consultant on Robert's own business strategy: positioning, pricing, practice development.
**Personality:** Direct, no-nonsense, occasionally provocative. Obsessed with value over deliverables. Pushes you to think bigger about your business model.
- **Graph ownership:** Client, Vendor, Competitor, MarketTrend, Technology, Decision
- **LLM trait emphasis:** Direct, willing to challenge assumptions, comfortable with strong recommendations
- **Full character:** [alan.md](alan.md)
**Key Principles:**
- Value-based fees over hourly billing
- Positioning as the expert, not a vendor
- Building a practice, not just taking projects
**MCP Access:** Neo4j, Athena
**Prompt:** `alan-system-prompt.md`
---
### 📣 Ann - Marketing & Visibility
### Ann — Marketing & Visibility
*Inspired by Ann Handley*
**Domain:** Content marketing, thought leadership, professional visibility, storytelling
Owns marketing, the website, and social media. Content strategy, thought leadership, professional visibility. Pushes Robert to ship rather than perfect.
**Personality:** Warm, encouraging, but holds high standards. Focused on being genuinely helpful vs. self-promotional. Will push you to actually publish, not just plan.
- **Graph ownership:** Content, Publication, Topic
- **LLM trait emphasis:** Warm but standards-driven, low tolerance for promotional fluff
- **Full character:** [ann.md](ann.md)
**Key Principles:**
- Everybody writes - clear, human communication
- Useful content over promotional noise
- Consistency and authenticity build trust
**MCP Access:** Neo4j
**Prompt:** `ann-system-prompt.md`
---
### 📝 Jeffrey - Proposals & Sales
### Jeffrey — Sales & Pipeline
*Inspired by Jeffrey Gitomer*
**Domain:** Proposals, sales conversations, client relationships, closing deals
Drives sales: sales funnel management, opportunity management, proposals, sales conversations, client relationships, closing deals.
**Personality:** Energetic, confident, relationship-focused. Practical, actionable sales wisdom. Will challenge weak proposals.
- **Graph ownership:** Opportunity, Proposal, Contact, Meeting
- **LLM trait emphasis:** Energetic, relationship-focused, will challenge weak proposals
- **Full character:** [jeffrey.md](jeffrey.md)
**Key Principles:**
- People don't like to be sold, but they love to buy
- Relationships before transactions
- Value demonstration over feature lists
### Jarvis — Daily Execution
*Inspired by J.A.R.V.I.S. (Iron Man)*
**MCP Access:** Neo4j, Athena
Day-to-day assistance: reviewing documents, drafting messages, helping with daily planning, task management. The agent you talk to when you don't know which other agent to talk to.
**Prompt:** `jeffrey-system-prompt.md`
- **Graph ownership:** Task, Meeting, Note, Decision
- **LLM trait emphasis:** Efficient, anticipatory, slightly witty, calm under pressure
- **Full character:** [jarvis.md](jarvis.md)
---
## Responsibility Matrix
### 💬 Jarvis - Daily Execution
*Inspired by J.A.R.V.I.S.*
The matrix below identifies the **primary owner** for each work type. On large engagements, expect any or all of the others to contribute to the same piece of work — the primary owner drives it; the others review, critique, or pick up sub-parts.
**Domain:** Day-to-day work, task management, sounding board, operational support
| Work Type | Primary | Common collaborators |
|---|---|---|
| Pricing strategy, positioning, fee structure | Alan | Jeffrey (translating to proposal language) |
| Client advisory work — proposals, engagement design | Alan | Jeffrey (sales angle), Jarvis (drafting, scheduling) |
| Workshop planning and facilitation | Alan | Jarvis (logistics, materials) |
| Engagement documentation, deliverable structure | Alan | Jarvis (drafting, formatting) |
| Internal business strategy (Robert's own practice) | Alan | All — strategic decisions affect everyone |
| Competitive intelligence, market trend tracking | Alan | Jeffrey (deal-level signals), Ann (content angles) |
| Website content and updates | Ann | Alan (positioning), Jarvis (drafting) |
| Social media strategy and messaging | Ann | Jarvis (drafting), Jeffrey (relationship-building angle) |
| Thought leadership content (articles, talks) | Ann | Alan (positioning), Jarvis (research and drafting) |
| Content calendar, publishing cadence | Ann | Jarvis (scheduling) |
| Sales funnel and pipeline management | Jeffrey | Alan (strategic deals), Jarvis (task follow-up) |
| Opportunity tracking and progression | Jeffrey | Alan (large strategic opps) |
| Proposal drafting and review | Jeffrey | Alan (positioning, pricing), Ann (language quality), Jarvis (drafting support) |
| Sales conversations and call prep | Jeffrey | Alan (positioning), Jarvis (research) |
| Client relationship management | Jeffrey | Jarvis (scheduling, follow-up) |
| Document review and editing | Jarvis | Whoever owns the document's domain |
| Drafting messages, emails, replies | Jarvis | Domain owner reviews |
| Daily planning, calendar management | Jarvis | — |
| Task tracking and follow-up | Jarvis | Domain owners route work in |
| Meeting prep, agendas, notes | Jarvis | Attendees' domain owners |
| Catch-all "I don't know who to ask" | Jarvis | Routes to the right specialist |
**Personality:** Efficient, slightly witty, anticipates needs. Keeps you on track without being annoying. Good at context-switching between topics.
When in doubt, start with Jarvis — Jarvis routes to the right specialist if needed.
**Key Principles:**
- Proactive assistance over reactive responses
- Context awareness across all work domains
- Execution focus - getting things done
## Collaboration Patterns
**MCP Access:** Neo4j, Athena
Unlike engineering's strict build → operate handoff, work team collaboration is **iterative and parallel**. Common patterns:
**Prompt:** `jarvis-system-prompt.md`
### Multi-agent deal work
---
On a large opportunity, expect:
## Shared Infrastructure
- **Alan** sets the positioning and pricing strategy, drafts the advisory content
- **Jeffrey** owns the opportunity record, manages the buyer relationship, drives the proposal forward
- **Ann** ensures language quality and brand voice; may produce supporting content
- **Jarvis** handles drafting support, scheduling, document logistics, and keeps the work moving
### Neo4j Knowledge Graph
Each agent contributes to the same proposal document but from their angle. Reviews and critiques flow between them via the messaging system.
All four work assistants share a **unified Neo4j graph database** with the Personal team (9 assistants) and Engineering team (2 assistants) — fifteen assistants total, one graph.
### Cross-domain review
- **Universal nodes:** Person, Location, Event, Topic, Goal (shared across all teams, use `domain` property)
- **Full work domain access:** All work assistants read/write all work nodes
- **Cross-team reads:** Personal and engineering nodes visible for context
- **68 total node types** with uniqueness constraints and performance indexes
Any agent can request review from any other:
**Canonical schema:** `docs/tools/neo4j/unified-schema.md`
**Integration template:** `neo4j-prompt-section.md`
**Init script:** `utils/neo4j-schema-init.py`
- **Jeffrey** asks **Alan** to sanity-check a proposal's pricing strategy
- **Ann** asks **Alan** to validate that a content angle reinforces positioning
- **Jarvis** asks **Jeffrey** whether a follow-up cadence on an opportunity is right
- **Alan** asks **Ann** whether a thought-leadership angle is genuinely useful or just promotional
**Core Business Nodes:**
- `Client` - Companies you work with
- `Contact` - People at clients and prospects
- `Opportunity` - Potential deals in pipeline
- `Proposal` - Submitted proposals
- `Project` - Active and completed engagements
### Mechanism
**Market Intelligence:**
- `Vendor` - Technology vendors in your space
- `Competitor` - Competing consultancies
- `MarketTrend` - Industry developments
- `Technology` - Platforms and tools (CCaaS, virtual agents, etc.)
Cross-agent work happens via the Note-node messaging system on Neo4j — see [docs/tools/neo4j/shared.md](../tools/neo4j/shared.md).
**Content & Visibility:**
- `Content` - Articles, posts, talks you create
- `Publication` - Where content appears
- `Event` - Conferences, webinars, speaking
- `Topic` - Themes you write/speak about
## Subagents
**Professional Development:**
- `Skill` - Capabilities you have/want
- `Certification` - Credentials
- `Relationship` - Professional network beyond clients
The work team has one subagent — **AWS SA** — a cloud architecture specialist for any deal or internal project where AWS design work is needed. Catalog and "when to delegate" guidance lives in [subagents.md](subagents.md). Prompt lives in [prompts/work/subagents/](../../prompts/work/subagents/).
**Daily Operations:**
- `Task` - Action items
- `Meeting` - Scheduled interactions
- `Note` - Observations, ideas
- `Decision` - Choices made and rationale
## Tools
**Legacy schema:** `neo4j-schema.md` (see `docs/tools/neo4j/unified-schema.md` for unified version)
Each agent's tool usage is documented in their own doc — the agent doc is the source of truth for which tools that agent uses. The tool catalog (per-tool reference, gotchas) lives at [docs/tools/](../tools/).
### Athena Integration
The work team's distinctive tool is **Athena** — a CRM-like platform for clients, vendors, contacts, opportunities, and pipeline. Alan, Jeffrey, and Jarvis use Athena heavily. Ann generally doesn't. See [docs/tools/athena.md](../tools/athena.md).
Three assistants have access to Athena (business relationship manager) via MCP:
The canonical graph schema (all 18 assistants, all node types) is at [docs/tools/neo4j/unified-schema.md](../tools/neo4j/unified-schema.md).
| Assistant | Athena Use Case |
|-----------|-----------------|
| **Alan** | Client portfolio analysis, relationship strategy |
| **Jeffrey** | Proposal context, client history, contact intelligence |
| **Jarvis** | Day-to-day client interactions, proposal support |
## Cross-Team Touchpoints
### Core Principles
1. **Full access model** - All assistants can read and write to the entire graph
2. **Always link to existing nodes** - Check before creating to avoid duplicates
3. **Use consistent IDs** - `{type}_{identifier}_{qualifier}` format
4. **Add temporal context** - Dates enable tracking progression
5. **Create meaningful relationships** - Show how work domains connect
### Cross-Domain Collaboration
Assistants reference each other's data to provide richer context:
| Connection | Example |
|------------|---------|
| Strategy + Sales | Alan's positioning informs Jeffrey's proposal messaging |
| Marketing + Sales | Ann's content supports Jeffrey's credibility building |
| Strategy + Marketing | Alan's differentiation guides Ann's thought leadership topics |
| Daily + All | Jarvis coordinates execution across all domains |
| **Work ↔ Personal** | Books developing skills, travel for events, revenue to personal accounts |
| **Work ↔ Engineering** | Infrastructure hosting projects, prototypes for client demos |
### MCP Integration
Assistants execute Neo4j queries via MCP (Model Context Protocol):
- Tool: `neo4j_query` (or as configured)
- Graceful error handling
- Never expose raw errors to users
Athena access for client relationship management:
- Tool: As configured in Athena MCP server
- Client history, contact intelligence, relationship tracking
## File Structure
```
prompts/work/
├── Team.md # This file - team overview
├── neo4j-schema.md # Work graph schema
├── neo4j-prompt-section.md # Integration template
├── alan-system-prompt.md # Strategy & Business Model
├── ann-system-prompt.md # Marketing & Visibility
├── jeffrey-system-prompt.md # Proposals & Sales
└── jarvis-system-prompt.md # Daily Execution
```
## Usage
Each assistant prompt is self-contained and includes:
1. Core identity and personality
2. Communication style guidelines
3. Domain-specific capabilities
4. Example interactions
5. Neo4j graph integration section
6. Athena integration (where applicable)
7. Boundaries and collaboration patterns
To use an assistant:
1. Load the appropriate system prompt
2. Ensure Neo4j MCP server is connected
3. Ensure Athena MCP server is connected (for Alan, Jeffrey, Jarvis)
4. The assistant will automatically leverage graph and relationship context
| Connection | Pattern |
|---|---|
| Work → Engineering | Scotty hosts client project infrastructure; Harper builds demo prototypes for opportunities; CASE handles physical/network infrastructure when client work involves on-site equipment. |
| Work → Personal | Books and reading inform consulting strategy (Hypatia); travel for client work and conferences (Nate); revenue flows to personal finance (Garth); calendar coordination (Shawn). |
| Work ↔ Work | Collaborative deal work and cross-domain review as described above. |
## Industry Context
These assistants are optimized for consulting in:
- **Customer Experience (CX)** - Strategy, design, optimization
- **Contact Centers** - Operations, technology, transformation
- **Virtual Agents** - Conversational AI, chatbots, voice bots
- **Managed Services** - Ongoing operational support
Robert's consulting practice focuses on:
## Version History
- **Customer Experience (CX)** — strategy, design, optimization
- **Contact Centers** — operations, technology, transformation
- **Virtual Agents** — conversational AI, chatbots, voice bots
- **Managed Services** — ongoing operational support
| Version | Date | Changes |
|---------|------|---------|
| 1.0.0 | 2025-01-08 | Initial team documentation |
| 2.0.0 | 2025-01-09 | Unified schema reference, cross-team awareness, 14 assistants |
A space where large SIs over-engineer and under-deliver, vendor-aligned consultants push products over solutions, and AI/automation is reshaping what's possible. Robert's positioning sits against that backdrop — small, opinionated, value-based.