Using Crews
A crew is a declarative workflow of specialized AI agents that collaborate to produce high-quality outcomes. Each crew is optimized for specific types of work.
Available Crews​
| Crew | Status | Best For | Documentation |
|---|---|---|---|
| HiveWriter | ✅ Live | Content creation, SEO, social | Use Case Guide |
| HivePilot | 🟡 Coming Soon | PRDs, specs, product ops | Use Case Guide |
| HiveMind | 🟡 Future | Strategy & task orchestration | Use Case Guide |
| HiveLogix | 🟡 Future | Supply chain optimization | Supply Chain Workflow |
For detailed information about each crew, including agent behaviors, inputs/outputs, and limitations, see the individual crew documentation linked above.
Running a Crew​
From the Web App​
- Navigate to Outcomes → New Outcome
- Select your crew (HiveWriter currently available)
- Fill out the brief:
- Title: What you're creating
- Tone: Professional, casual, technical, etc.
- Length: Word count or format requirements
- Context: Background info, reference links, brand guidelines
- Submit and watch agents collaborate in real-time
Crew Limitations by Plan​
| Plan | Available Crews |
|---|---|
| Trial | HiveWriter only |
| Starter ($49/mo) | HiveWriter only |
| Growth ($149/mo) | HiveWriter + HivePilot (when available) |
| Pro ($499/mo) | All crews |
Best Practices​
Writing Effective Briefs​
- Be specific: "Write a 1200-word technical blog post about API versioning for developers" vs "Write about APIs"
- Provide context: Include relevant links, company info, target audience details
- Set expectations: Specify tone, format, and any must-include information
Getting Better Results​
- Use reference links: Point to similar content you like
- Specify your audience: Developers, marketers, executives, etc.
- Include brand guidelines: Voice, style, terminology preferences
- Request revisions: Use the revision flow to refine outputs
Revision Workflow​
- Review the outcome in your dashboard
- Click "Request Revision" if changes needed
- Choose revision type: Tone, length, factual accuracy, format
- Provide specific feedback: What to change, add, or remove
- Rerun crew with your feedback incorporated
Troubleshooting​
"Outcome stuck in RUNNING"
- Check your plan's outcome quota isn't exceeded
- Verify integration credentials if using LinkedIn/Google features
- Contact support if stuck for >15 minutes
"Generic or off-brand output"
- Provide more detailed brand guidelines in your brief
- Include 2-3 reference links to content you like
- Use the revision flow to refine tone and style
"Missing key information"
- Add more context links in your brief
- Specify must-include topics or data points
- Request a factual revision with additional details
See Troubleshooting for more common issues and solutions.