Why Create Custom Collectives?
While Code and Create collectives cover software development and content creation, your organization likely has domain-specific needs:Industry-Specific Work
Finance, healthcare, legal, real estate, manufacturing - each has unique workflows
Organizational Processes
Sales, HR, operations, compliance - internal processes need automation
Specialized Expertise
Data science, design, research, education - specialized disciplines
Custom Workflows
Unique business processes that don’t fit standard collectives
Collective Directory Structure
A custom collective follows this structure:Creating Agents
Agents are defined in Markdown files with specific sections:Agent Template
Example: Financial Analyst Agent
File:.genie/collectives/finance/agents/analyst.md
Behavioral Protocols
- Use multiple analytical methods for validation
- Consider both quantitative and qualitative factors
- Provide context for all metrics
- Highlight key risks and opportunities
- Support conclusions with data
- Consider industry benchmarks
Output Format
Analysis Summary
- Key findings (3-5 bullet points)
- Critical metrics
- Trends identified
Detailed Analysis
- Financial ratios
- Trend analysis
- Comparative analysis
- Risk factors
Recommendations
- Actionable insights
- Risk mitigation strategies
- Next steps
Tools & Integrations
- Financial APIs (Alpha Vantage, Yahoo Finance)
- Spreadsheet integration
- Visualization tools
Example: Financial Risk Assessment Spell
File:.genie/collectives/finance/spells/risk-assessment.md
- Probability: 30% chance of losing one in next year
- Impact: $2M revenue loss
- Risk Score: $600K (High)
- Diversify client base (add 10 new clients)
- Strengthen relationships with top clients
- Create client retention program
- Build 6-month cash reserve
Creating Workflows
Workflows coordinate multiple agents for complex processes:Workflow Template
Example: Quarterly Financial Report Workflow
File:.genie/collectives/finance/workflows/quarterly-report.md
Creating Advisory Teams
Teams are groups of agents that collaborate on complex decisions:Team Template
Example: Finance Council
File:.genie/collectives/finance/teams/finance-council.md
Example: Finance Collective
Let’s build a complete Finance Collective:Structure
Usage Examples
Example: Health Collective
Healthcare and wellness collective:Agents
diagnostician
Health assessment and symptom analysis
researcher
Medical research and evidence review
educator
Patient education and health literacy
tracker
Health metrics tracking and trends
wellness-coach
Lifestyle and wellness guidance
pharmacist
Medication information and interactions
Spells
- medical-ethics.md: Ethical guidelines for health advice
- evidence-based.md: Use peer-reviewed research
- patient-centered.md: Focus on patient needs and understanding
- privacy-first.md: HIPAA compliance and privacy protection
Workflows
- symptom-assessment.md: Systematic symptom evaluation
- treatment-research.md: Research treatment options
- medication-review.md: Check interactions and side effects
- wellness-plan.md: Create personalized wellness plans
Example: Legal Collective
Legal and compliance collective:Agents
contract-reviewer
Contract review and analysis
legal-researcher
Legal research and precedents
compliance-officer
Regulatory compliance checking
risk-assessor
Legal risk assessment
drafter
Legal document drafting
negotiator
Contract negotiation support
Spells
- due-diligence.md: Thorough review protocol
- risk-mitigation.md: Legal risk reduction
- plain-language.md: Write clearly, not legalese
- precedent-analysis.md: Learn from case law
Workflows
- contract-review.md: Systematic contract analysis
- compliance-audit.md: Regulatory compliance check
- dispute-resolution.md: Conflict resolution process
- policy-creation.md: Create company policies
Best Practices
Start with Core Agents
Start with Core Agents
Begin with 4-6 essential agents:Good First Set:
- Primary executor agent
- Quality reviewer agent
- Risk/compliance agent
- Subject matter expert agent
- Create 30 agents immediately
- Over-specialize too early
- Duplicate existing collective capabilities
Create Spells for Consistency
Create Spells for Consistency
Spells ensure consistent behavior:
Design Workflows for Common Processes
Design Workflows for Common Processes
Identify repeatable processes first:High-Value Workflows:
- Frequent (weekly/monthly/quarterly)
- Multi-step coordination
- Quality-critical
- Cross-agent collaboration
- One-off tasks
- Simple single-agent work
- Ad-hoc requests
Leverage Existing Collectives
Leverage Existing Collectives
Don’t reinvent the wheel:Cross-collective collaboration is encouraged!
Test Before Deploying
Test Before Deploying
Validate your collective works:
Document Everything
Document Everything
Good documentation ensures:
- Others can use your collective
- You remember how it works later
- Agents have clear guidelines
- Quality stays consistent
- Agent capabilities and usage
- Spell protocols and reasoning
- Workflow steps and validation
- Team decision processes
Getting Started
1
Identify Domain Need
What domain-specific work do you need?Questions to Ask:
- What repetitive tasks exist?
- What expertise is needed?
- What processes are manual?
- What decisions need multiple perspectives?
2
Create Collective Directory
3
Create Core Agents
Start with 3-5 essential agents:Refine the generated agent definition
4
Define Behavioral Spells
Create 2-3 key spells for consistency:Refine the generated spell
5
Build First Workflow
Create one high-value workflow:Test and refine
6
Create Advisory Team (Optional)
For complex decisions, create a team:
7
Test Everything
8
Iterate and Improve
- Gather feedback
- Add missing capabilities
- Refine protocols
- Optimize workflows
CLI Commands for Custom Collectives
Sharing Custom Collectives
Once you’ve built a valuable collective, share it:Export Your Collective
Documentation for Users
Include a README:Agents
- analyst: Financial analysis and insights
- auditor: Compliance and controls
- forecaster: Projections and scenarios
Workflows
- quarterly-report: Generate quarterly financial reports
- budget-planning: Annual budget creation
Usage Examples
[Examples here]Requirements
- Access to financial data APIs
- Spreadsheet integration
- Python 3.8+
License
MITCollective Inheritance
Build on existing collectives:Cross-Collective Workflows
Workflows can span multiple collectives:Next Steps
Code Collective
Learn from 34 specialized development agents
Create Collective
See shape-shifting in action
Workflows
Master workflow orchestration
Community Collectives
Browse community-created collectives
Resources
Collective Templates
Collective Templates
Download starter templates:
- Finance Collective Template
- Healthcare Collective Template
- Legal Collective Template
- Sales Collective Template
- HR Collective Template
Community Collectives
Community Collectives
Browse and install community collectives:
Best Practices Guide
Best Practices Guide
Naming Conventions:
- Agents: noun (analyst, reviewer, creator)
- Spells: noun or verb-noun (risk-assessment, commit-advisory)
- Workflows: noun-phrase (quarterly-report, budget-planning)
- One agent per file
- One spell per file
- One workflow per file
- Clear, descriptive names
- Purpose statement for everything
- Usage examples in every agent
- Validation criteria in workflows
- Decision processes in teams
Troubleshooting
Troubleshooting
Agent not working as expected:
- Review agent definition clarity
- Check if relevant spells are applied
- Validate input format
- Test with simpler tasks first
- Test each step independently
- Check validation gates
- Verify agent availability
- Review error messages
- Ensure diverse perspectives
- Provide sufficient context
- Review decision process
- Consider adding/removing members
Ready to build your own collective? Start small, test often, and iterate based on feedback. The best collectives emerge from real needs and continuous refinement.

