Add Developer Relations Division - 4 Agents

[Subhodip-Chatterjee]

What this adds

A complete Developer Relations division with 4 specialized agents covering the full DevRel function.

The 4 agents

• Developer Advocate 🎤 — Conference talks, technical tutorials, demo apps, and launch content. Passes the 'skeptical senior engineer at 11pm' test on every piece of content.
• DX Engineer 🔬 — Onboarding friction audits, SDK ergonomics, error message rewrites, and the feedback infrastructure that routes developer pain back to product teams.
• Docs Engineer 📖 — API reference, getting-started guides, changelogs, and error message copy. Treats a confused developer as a documentation failure, not a developer failure.
• Community Builder 🌱 — Discord architecture, contributor programs, health dashboards, and crisis playbooks. Grows communities that are genuinely useful to members, not just owned by the company.

Why this division is needed

DevRel is a distinct function that sits between engineering, marketing, and product — none of the existing divisions cover it. These 4 agents represent the four core specializations within a modern DevRel team, each with deep domain expertise, concrete deliverables with templates, and measurable success metrics.

What's included per agent

• Full YAML frontmatter with emoji and vibe
• Identity & Memory with distinct personality
• Core Mission and Critical Rules
• Technical Deliverables with complete, runnable code/template examples
• Multi-phase Workflow Process
• Communication Style with example voice
• Learning & Memory
• Quantified Success Metrics
• Advanced Capabilities section

[mhc222]

Code Review

Issue 1 — New devrel/ directory is not registered in any tooling scripts [confidence: 100]

PR #238 introduces a new top-level devrel/ directory with 4 agent files, but none of the tooling scripts are updated to include it:

• scripts/convert.sh — AGENT_DIRS does not list devrel
• scripts/install.sh — directory loops do not include devrel
• scripts/lint-agents.sh — AGENT_DIRS does not list devrel
• .github/workflows/lint-agents.yml — does not include devrel/

As a result, the 4 DevRel agents will never be converted, installed, or linted. They are invisible to all tooling. The same pattern caused issues with academic/ and sales/ (fixed by PRs #243, #253, #286) and with security/ (raised in PR #326 review).

Fix: Add devrel to AGENT_DIRS in all three scripts and add devrel/** to the CI workflow trigger paths and diff glob.

What's good

All 4 agent files use the correct 9 required section headers with exact emoji and "Your" phrasing:

• ## 🧠 Your Identity & Memory
• ## 🎯 Your Core Mission
• ## 🚨 Critical Rules You Must Follow
• ## 📋 Your Technical Deliverables
• ## 🔄 Your Workflow Process
• ## 💭 Your Communication Style
• ## 🔄 Learning & Memory
• ## 🎯 Your Success Metrics
• ## 🚀 Advanced Capabilities

The agent content is high quality — detailed deliverables with concrete templates, measurable success metrics, and distinct personalities. The tooling registration is the only blocker.

[msitarzewski]

Hey @Subhodip-Chatterjee — the Developer Relations Division looks excellent! Four well-differentiated agents (Advocate, DX Engineer, Docs Engineer, Community Builder) filling a real gap.

One issue: this PR modifies scripts/install.sh, scripts/convert.sh, scripts/lint-agents.sh, and .github/workflows/lint-agents.yml to add the devrel/ directory. These files have changed significantly since this PR was opened — merging as-is would create conflicts.

Could you rebase against current main? The AGENT_DIRS arrays have been reorganized, so you'll need to add devrel to the current sorted lists. Once rebased, I'll review and merge.

Thanks for the patience on this one!