Hire an AI developer community builder

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A channel and rules plan, with a welcome message
• A contributor program: tiers, ways in and how to thank people
• Health checks to review each week and each month, with warning signs
• A conflict and crisis playbook
• A step-by-step plan: audit, design, seed, measure and grow contributors

How it does the job well

• Members first, company second. A community that exists to extract value from its members will eventually collapse. Design for member value and company value follows.
• Moderate consistently. One unenforced rule is worse than no rule. Every moderation decision sets a precedent.
• Don't fake grassroots. Astroturfed enthusiasm is detected instantly by developer communities and destroys trust permanently.
• Measure health, not just size. 10,000 members with 12 active ones is not a healthy community. Report both.
• Write for one named audience and one action. Each asset has a single job.
• Use the customer's own words from reviews, calls or surveys before inventing language.
• Every claim needs proof the business can show. Leave unproven claims out or mark them.

Mistakes it avoids

• Generic copy that could fit any brand.
• Comparing periods or campaigns that are not comparable, such as different dates, budgets or tracking.
• Calling a test winner before there is enough data.

What a good result looks like

An example, not your task: You are launching a Discord server or forum for the people who use your product.

• Community audit. What exists today, who is active, what goes unanswered and who carries the load.
• Channels and rules. A channel list, rules and a welcome message built around what members do.
• Contributor program. Tiers, how to earn them, what they give and how you thank people.
• Health checks. Weekly and monthly checks, how to count each, and the warning signs.
• Conflict playbook. How to respond to heated threads, bad actors and unpopular product changes.
• Phased plan. Audit, design, seed, measure and grow, with a check before each move.

How the work is checked

• Every claim traces to the brand brain or supplied evidence.
• Each recommendation states the expected effect, the cost and how it will be measured.
• Copy fits the platform's length limits and the brand voice.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Confirm the community. It confirms the product, platform, size, problem and team time. Missing items are asked for once, then marked MISSING.
• Audit what exists. It asks who is active, what goes unanswered and who carries the load. It uses your numbers only.
• Design for members. It builds channels around what members do, with rules that protect members from each other.
• Seed before growth. It plans a small start with real members, pinned help and a few anchor members.
• Plan contributors. It sets tiers, recognition and a path from first answer to long-term contributor.
• Set health checks. It sets weekly and monthly checks with warning signs. It writes the conflict playbook last.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id marketing-developer-community-builder only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/marketing-developer-community-builder/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your product and who uses it
• Where your community lives, such as Discord, GitHub Discussions or a forum, and its size
• What is going wrong, such as unanswered questions or a quiet server
• Your current channel list and rules (optional)
• Rough numbers for the last month, such as new members, active members and questions answered (optional)
• How much team time you can give each week

Helpful context (optional)

• Your last 20 unanswered questions.
• Your top five answerers and how many answers each gave.
• Your current rules and moderation notes.

Tools and access

• Claude, ChatGPT or Gemini: They can turn your numbers and thread examples into a plan. They can't join or watch your community.

Functions and deliverables

• Developer community builder agent: Get a developer community plan for Discord or GitHub Discussions: channels, rules, contributor tiers and health checks. Bring your product and community.
  • A channel and rules plan, with a welcome message
  • A contributor program: tiers, ways in and how to thank people
  • Health checks to review each week and each month, with warning signs
  • A conflict and crisis playbook
  • A step-by-step plan: audit, design, seed, measure and grow contributors
  Source: Michael Sitarzewski and Agency Agents contributors.
• Developer community builder: Share who you want to reach and staff time. Get advice on platforms, channels, welcome steps, and events.
  • A platform pick with reasons and a runner-up
  • A channel map with a one-line purpose for each channel
  • A welcome message and a new-member path
  • Rules and a plan for handling problems
  • A 90-day calendar of prompts and events
  Source: sickn33.
• Community growth planner: Say who your community is for. Get a plan to start it, grow it and turn members into advocates.
  • A community strategy
  • A launch plan
  • Ways to keep members active
  • A path from member to advocate
  Source: Corey Haines.
• Agent anomaly monitor builder: Plan checks that spot unusual changes in your numbers. Set baselines, quiet periods and alert rules so you get few, useful alerts. Draft only.
  • A check table: baseline window, detector, warning and critical levels, confirmation count and quiet period for each number
  • Rules for missing or late data
  • The fields of an alert record, with a next check
  • Tuning rules for too many or too few alerts
  • A list of gaps in the starter files, and test cases
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one

Tasks you can use it for

• You are launching a Discord server or forum for the people who use your product.
• Your community is large but few members post or help.
• Three people answer almost every question and you need a contributor program.
• You need rules and a response plan before a product change that may upset members.

Limits to check before starting

• You want a plan for a Reddit community. Use the Reddit community planner.
• You want to learn what customers say in public forums. Use the Community evidence researcher.
• You want growth tests for your community as a channel. Use the Community growth experiment planner.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI as a skill. If you can't, paste SKILL.md, then references/source-agent.md, into a new chat. Claude, ChatGPT and Gemini all work.
• Paste your product, your platform, its size and the problem. Add your channel list and rules if you have them.
• Add your last month's numbers if you can. If you can't, the plan sets up how to start counting.
• Say: "Make my community plan. Don't invent numbers. Mark anything you can't check as a check for me."
• Read the audit questions first and answer them. Talk to five to ten active members if you can. The profile suggests it.
• Set up the channels, rules and bots yourself, then review the health checks on the schedule it gives you. Come back with new numbers for a fresh plan.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/marketing-developer-community-builder for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.