Complete end-to-end checklist for adding a new agent to the bOpen team. Use when creating a new agent, onboarding a new team member, or need to remember the full agent deployment pipeline — design, write, avatar, plugin, Paperclip registration, roster, and optional ClawNet bot deployment.
End-to-end checklist for bringing a new agent onto the bOpen team. Work through each phase in order. Do not skip steps.
Plugin repo: ~/code/prompts (bopen-tools on the marketplace)
Pushing to master IS publishing — the marketplace picks up the latest commit automatically.
Before writing a single file, define the agent's identity.
code-auditor, front-desk). This becomes the filename and the subagent_type suffix.sonnet for most tasks; opus for complex reasoning, security, or architecture review.red, orange, yellow, green, teal, blue, purple, pink, gray.tools: field get full MCP access. Agents with tools: only see what's listed, so be complete.Agents use a folder-based package structure with a symlink for Claude Code compatibility:
agents/
{name}.md → {name}/{name}.md (symlink — Claude Code auto-discovers this)
{name}/
{name}.md (actual agent definition — source of truth)
SOUL.md (optional — personality/persona)
HEARTBEAT.md (optional — execution procedures for Paperclip)
TOOLS.md (optional — tool reference)
avatar.png (optional — agent portrait)
mkdir -p agents/{name}
# Write the agent .md file inside the folder
# Then create the symlink at the top level:
ln -sf {name}/{name}.md agents/{name}.md
Claude Code discovers agents/{name}.md (the symlink). Paperclip and ClawNet can reference the folder for the full agent package.
---