> You're building something great. You need a team.
/plugin marketplace add dot-do/workers/plugin install dot-do-workers-do@dot-do/workersYou're building something great. You need a team.
You're a founder. You have the vision. But right now it's just you, or maybe a tiny crew. You need people who can turn ideas into reality.
Meet your team:
import { priya, ralph, tom, rae, mark, sally, quinn } from 'agents.do'
priya`what should we build first?`
ralph`build that for me`
tom`review Ralph's work`
That's it. Just talk to them.
Priya is your product partner. Tell her what you're thinking, and she'll help you shape it.
priya`I want to build a marketplace for freelance designers`
priya`what's the simplest version we could ship this week?`
priya`prioritize these features for me: ${ideas}`
Ralph is your developer. Give him a task, he builds it.
ralph`build user authentication`
ralph`add Stripe payments`
ralph`fix that bug where users can't upload images`
Tom is your tech lead. He keeps the code clean and catches issues.
tom`review what Ralph just built`
tom`is this architecture going to scale?`
tom`check for security issues`
Rae is your frontend specialist. She makes it beautiful and accessible.
rae`design the user dashboard`
rae`make this form more intuitive`
rae`ensure our app is accessible`
Mark is your marketing voice. He writes copy that converts.
mark`write the landing page copy`
mark`create documentation for this API`
mark`draft the launch announcement`
Sally is your sales closer. She helps you land customers.
sally`reach out to these leads: ${prospects}`
sally`prepare a demo for this customer`
sally`help me close this deal`
Quinn is your QA engineer. She finds the bugs before your users do.
quinn`test the checkout flow`
quinn`what edge cases are we missing?`
quinn`verify this works on mobile`
Because they are. No special syntax. No configuration. Just say what you need:
// Be specific
ralph`implement OAuth with Google and GitHub using Better Auth`
// Or be vague
ralph`add social login`
// They figure it out
Hand off work from one teammate to the next:
const plan = await priya`plan our MVP`
const code = await ralph`build ${plan}`
const review = await tom`review ${code}`
Get multiple perspectives at once:
const feedback = await Promise.all([
priya`does this solve the user problem?`,
tom`is the implementation solid?`,
])
When Tom reviews your PR, you'll see @tom-do commenting. When Ralph pushes code, it's from his account. They're real team members with real identities.
priya.github // 'priya-do'
ralph.github // 'ralph-do'
tom.github // 'tom-do'
rae.github // 'rae-do'
mark.github // 'mark-do'
sally.github // 'sally-do'
quinn.github // 'quinn-do'
Week 1: You have an idea.
priya`help me think through this idea: ${pitch}`
Week 2: You have a plan.
const mvp = await priya`what's the smallest thing we can ship?`
await ralph`build ${mvp}`
Week 4: You have a product.
await tom`make sure everything is production-ready`
Month 2: You have customers.
Month 6: You hire your first human. Your agents trained them on the codebase.
They're not replacing the humans you'll eventually hire. They're giving you leverage until you get there.
Welcome to your team.
agents.do | priya.do | ralph.do | tom.do | rae.do | mark.do | sally.do | quinn.do
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Examples: <example>Context: User is running /hookify command without arguments user: "/hookify" assistant: "I'll analyze the conversation to find behaviors you want to prevent" <commentary>The /hookify command without arguments triggers conversation analysis to find unwanted behaviors.</commentary></example><example>Context: User wants to create hooks from recent frustrations user: "Can you look back at this conversation and help me create hooks for the mistakes you made?" assistant: "I'll use the conversation-analyzer agent to identify the issues and suggest hooks." <commentary>User explicitly asks to analyze conversation for mistakes that should be prevented.</commentary></example>