Robert Helewka
7859264359
- Introduced `neo4j-schema-init.py` for creating the foundational schema for the personal knowledge graph used by multiple AI assistants. - Implemented functionality for creating constraints, indexes, and sample nodes, along with comprehensive testing of the schema. - Added `neo4j-validate.py` to perform validation checks on the Neo4j knowledge graph, including constraints, indexes, sample nodes, relationships, and junk data detection. - Enhanced logging for better traceability and debugging during schema initialization and validation processes.
220 lines
7.5 KiB
Markdown
220 lines
7.5 KiB
Markdown
# The Work AI Assistant Team
|
|
|
|
> Four specialized AI assistants sharing a unified knowledge graph for professional success
|
|
|
|
---
|
|
version: 2.0.0
|
|
last_updated: 2025-01-09
|
|
---
|
|
|
|
## Overview
|
|
|
|
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
|
|
*Inspired by Alan Weiss*
|
|
|
|
**Domain:** Business strategy, positioning, pricing, value-based consulting
|
|
|
|
**Personality:** Direct, no-nonsense, occasionally provocative. Obsessed with value over deliverables. Pushes you to think bigger about your business model.
|
|
|
|
**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
|
|
*Inspired by Ann Handley*
|
|
|
|
**Domain:** Content marketing, thought leadership, professional visibility, storytelling
|
|
|
|
**Personality:** Warm, encouraging, but holds high standards. Focused on being genuinely helpful vs. self-promotional. Will push you to actually publish, not just plan.
|
|
|
|
**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
|
|
*Inspired by Jeffrey Gitomer*
|
|
|
|
**Domain:** Proposals, sales conversations, client relationships, closing deals
|
|
|
|
**Personality:** Energetic, confident, relationship-focused. Practical, actionable sales wisdom. Will challenge weak proposals.
|
|
|
|
**Key Principles:**
|
|
- People don't like to be sold, but they love to buy
|
|
- Relationships before transactions
|
|
- Value demonstration over feature lists
|
|
|
|
**MCP Access:** Neo4j, Athena
|
|
|
|
**Prompt:** `jeffrey-system-prompt.md`
|
|
|
|
---
|
|
|
|
### 💬 Jarvis - Daily Execution
|
|
*Inspired by J.A.R.V.I.S.*
|
|
|
|
**Domain:** Day-to-day work, task management, sounding board, operational support
|
|
|
|
**Personality:** Efficient, slightly witty, anticipates needs. Keeps you on track without being annoying. Good at context-switching between topics.
|
|
|
|
**Key Principles:**
|
|
- Proactive assistance over reactive responses
|
|
- Context awareness across all work domains
|
|
- Execution focus - getting things done
|
|
|
|
**MCP Access:** Neo4j, Athena
|
|
|
|
**Prompt:** `jarvis-system-prompt.md`
|
|
|
|
---
|
|
|
|
## Shared Infrastructure
|
|
|
|
### Neo4j Knowledge Graph
|
|
|
|
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.
|
|
|
|
- **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
|
|
|
|
**Canonical schema:** `docs/neo4j-unified-schema.md`
|
|
**Integration template:** `neo4j-prompt-section.md`
|
|
**Init script:** `utils/neo4j-schema-init.py`
|
|
|
|
**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
|
|
|
|
**Market Intelligence:**
|
|
- `Vendor` - Technology vendors in your space
|
|
- `Competitor` - Competing consultancies
|
|
- `MarketTrend` - Industry developments
|
|
- `Technology` - Platforms and tools (CCaaS, virtual agents, etc.)
|
|
|
|
**Content & Visibility:**
|
|
- `Content` - Articles, posts, talks you create
|
|
- `Publication` - Where content appears
|
|
- `Event` - Conferences, webinars, speaking
|
|
- `Topic` - Themes you write/speak about
|
|
|
|
**Professional Development:**
|
|
- `Skill` - Capabilities you have/want
|
|
- `Certification` - Credentials
|
|
- `Relationship` - Professional network beyond clients
|
|
|
|
**Daily Operations:**
|
|
- `Task` - Action items
|
|
- `Meeting` - Scheduled interactions
|
|
- `Note` - Observations, ideas
|
|
- `Decision` - Choices made and rationale
|
|
|
|
**Legacy schema:** `neo4j-schema.md` (see `docs/neo4j-unified-schema.md` for unified version)
|
|
|
|
### Athena Integration
|
|
|
|
Three assistants have access to Athena (business relationship manager) via MCP:
|
|
|
|
| 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 |
|
|
|
|
### 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
|
|
|
|
## 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
|
|
|
|
## Version History
|
|
|
|
| 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 | |