Working with RISR's AI Team
Your guide to Maya, Sam, Quinn, Charlie, Hugo, and Archie — the AI agents who work alongside us.
🚀 Quick Start
Six AI agents, each with their own specialty and Slack presence.
Shared Tools (All Agents)
Good For
- Content drafts & blog posts
- Campaign planning
- Brand voice questions
- Marketing research
Shared Tools (All Agents)
Good For
- Prospect research
- Pipeline reports
- Deal prep & call prep
- Competitor analysis
Shared Tools (All Agents)
Good For
- PRDs & feature specs
- Product metrics
- User research synthesis
- Roadmap planning
Shared Tools (All Agents)
Good For
- Customer health reports
- QBR preparation
- Onboarding help
- Account history summaries
Shared Tools (All Agents)
Engineering Extras
Good For
- Bug investigation
- Code questions
- Deployment help
- Database queries
Shared Tools (All Agents)
Infrastructure Extras
Good For
- "What can the agents do?"
- Technical issues
- Questions about capabilities
- Agent system explanations
@mention in their channel, DM them directly, or @mention wherever they're present.
💬 Just Ask
The agents are more capable than you might expect. Don't overthink it — if you're wondering "can they do X?" just try it.
Try prompts like these:
If they can't help, they'll say so. If they need more context, they'll ask. You won't break anything by asking.
🛠️ Tools & Capabilities
What each agent can access and do.
Each agent has their own @risr.com Google account. For security, they can only send and receive emails to/from @risr.com addresses — no external emails. They can also view (but not edit) the team calendar.
| Agent | Additional Tools | Best Used For |
|---|---|---|
| Maya 🦕 | Shared tools only | Content drafts, campaign planning, brand questions |
| Sam 🏌️ | Shared tools only | Prospect research, pipeline reports, deal prep |
| Quinn 🧙 | Shared tools only | PRDs, feature specs, metrics, user research |
| Charlie 🧞♂️ | Shared tools only | Customer health, QBR prep, onboarding help |
| Hugo 🎅 | Claude Code, GitHub, Heroku, Sentry, AWS, Postgres | Bug hunts, code questions, deployment help |
| Archie 🏗️ | System Config, Agent Management | "What can agents do?", technical issues |
📁 Files & Images
What agents can receive and create.
Each agent has their own folder. When they save something, it's there instantly.
Access Files →📥 They Can Receive
- Images dropped in Slack (they'll see and analyze them)
- PDFs and docs uploaded to chat
- Links to Google Drive files (if they have access)
- Links to Notion pages
📤 They Can Create
- Markdown docs and reports
- Spreadsheet-style data exports
- Save anything to their
files/folder - Research compilations
🧠 Memory
Agents don't just forget everything between conversations. This is one of the most powerful features.
Agents keep notes. When you tell Maya something important about brand voice, she writes it down. Next time she drafts copy, she remembers.
How It Works
Agent Memory
MEMORY.md — Their long-term memory. Key decisions, preferences, important context.
memory/YYYY-MM-DD.md — Daily notes. What happened, what they learned.
Shared Memory
risr-shared/ — Company-wide context ALL agents can read. Company decisions, customer info, product updates, process docs.
Add to Their Memory
Tell them directly — they'll write it down:
Share Across All Agents
Need ALL agents to know something? Tell any agent to update the shared context:
The agent will update risr-shared/ so every other agent sees it next time they work.
✨ Getting Better Results
Small changes in how you ask can make a big difference.
Let Them Use Their Tools
Instead of giving agents every detail, ask them to look things up. They have powerful tools — let them be agentic!
Pro Tips for Power Users
🎯 Give Context Up Front
⚡ Ask for Sub-Agents for Parallel Work
📝 Ask for Drafts, Then Iterate
🔄 Ask Them to Self-Review
✅ Ask Them to Double-Check
⚡ Sub-Agents
For big tasks, agents can spawn helpers to work in parallel.
How It Works
When you give an agent a big task, they can spawn "sub-agents" to work simultaneously.
You don't need to ask for this — agents do it automatically when it makes sense. But you can be explicit:
EXAMPLE
"Research these 5 competitors"
Behind the scenes:
- Agent spawns 5 sub-agents
- Each researches one competitor
- Results compiled and returned
🆘 Escalation
When agents point you to someone else.
Sometimes an agent will say:
This happens for config changes, new tool access, or capability requests.
He manages agent infrastructure and can make changes. Archie can answer questions about what's possible, but Brandon approves changes.
⚠️ Limitations
The real constraints and workarounds.
Why: Safety — we want human review on external communications.
Workaround: Ask them to draft, you review and send (or they send after you approve).
Why: Privacy — agents have their own accounts.
Workaround: Forward or paste relevant threads to them.
Why: No payment access.
Workaround: They can draft the request for you.
Why: Privacy between sessions.
Workaround: Ask them to check with another agent or share context yourself.
Why: They're not psychic.
Workaround: Share context, ask them to research.
Review anything important, especially numbers, customer names, and external-facing content.
Architecture
Slack → Gateway Server → Agent
↓
Workspace
(files, memory)
↓
Tools
(APIs, search, etc.)
Each agent has:
- Slack account — Their identity in Slack
- Workspace folder — Their files, memory, instructions
- Tool access — What systems they can use
- Session — Current conversation context
Sessions
A "session" is a conversation thread. Within a session, the agent remembers everything said. Between sessions, they rely on memory files.
Sessions can get long. When they do, older context gets summarized to make room for new messages.
The Gateway
All messages route through a gateway server that:
- Routes messages to the right agent
- Manages tool permissions
- Handles session state
- Runs on our infrastructure (not a third-party service)
Memory Files
agent-workspace/ ├── SOUL.md # Personality, role definition ├── AGENTS.md # Operating instructions ├── MEMORY.md # Long-term memory ├── memory/ │ ├── 2026-01-30.md │ └── 2026-01-29.md ├── files/ # Deliverables └── tools/ # Tool-specific notes
Shared Context
risr-shared/ ├── company/ │ ├── biz-summary.md │ ├── team.md │ └── team-profiles/ ├── product/ ├── customers/ └── docs/
All agents read from risr-shared/ but write to their own workspace.
📋 Quick Reference
- #marketing-ai (Maya)
- #sales-ai (Sam)
- #product-mgmt-ai (Quinn)
- #customer-success-ai (Charlie)
- #eng-ai (Hugo)