gh-vanman2024-domain-plugin-builder-plugins-domain-plugin-builder/commands/agents-create.md

description, argument-hint, allowed-tools

description	argument-hint	allowed-tools
Create agent(s) using templates - supports parallel creation for 3+ agents	<agent-name> "<description>" [--marketplace] | <agent-1> "<desc-1>" <agent-2> "<desc-2>" ... [--marketplace]	Task, Read, Write, Edit, Bash, Glob, Grep, TodoWrite

---

🚨 EXECUTION NOTICE FOR CLAUDE

When you invoke this command via SlashCommand(/domain-plugin-builder:agents-create ...), the system returns THESE INSTRUCTIONS below.

YOU are the executor. This is NOT an autonomous subprocess.

• ✅ The phases below are YOUR execution checklist
• ✅ YOU must run each phase immediately using tools (Bash, Read, Write, Edit, TodoWrite)
• ✅ Complete ALL phases before considering this command done
• ❌ DON'T wait for "the command to complete" - YOU complete it by executing the phases
• ❌ DON'T treat this as status output - it IS your instruction set

Immediately after SlashCommand returns, start executing Phase 0, then Phase 1, etc.

See @CLAUDE.md section "SlashCommand Execution - YOU Are The Executor" for detailed explanation.

---

Arguments: $ARGUMENTS

Security: Follow @~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/docs/security/SECURITY-RULES.md (never hardcode API keys)

Framework: Load @component-decision-framework.md and @dans-composition-pattern.md

Goal: Create properly structured agent file(s). For 3+ agents, use parallel execution.

EXECUTE each phase immediately using actual tools (Bash, Read, Write, Task, TodoWrite). Complete all phases in order.

Phase 0: Create Todo List

Create todo list for all phases below.

Phase 1: Parse Arguments, Determine Mode & Count Agents Goal: Extract agent specifications, determine mode, and execution strategy

Actions:

Parse $ARGUMENTS to extract:

• Agent names and descriptions
• Plugin name (from context or pwd)
• Marketplace mode (check for --marketplace flag)

If plugin not specified:

!{bash basename $(pwd)}

Determine base path - check if already in a plugin directory:

!{bash test -f .claude-plugin/plugin.json && echo "." || (echo "$ARGUMENTS" | grep -q "--marketplace" && echo "plugins/$(basename $(pwd))" || echo ".")}

Store as $BASE_PATH:

• If .claude-plugin/plugin.json exists: BASE_PATH="." (already in plugin directory)
• Else if --marketplace present: BASE_PATH="plugins/$PLUGIN_NAME"
• Else: BASE_PATH="." (standalone plugin mode)

All subsequent file operations use $BASE_PATH instead of hardcoded "plugins/$PLUGIN_NAME"

Use bash to parse $ARGUMENTS and count how many agents are being requested:

!{bash echo "$ARGUMENTS" | grep -oE '<[^>]+>' | wc -l}

Store the count. Then extract each agent specification:

• If count = 1: Single agent mode - extract and ""
• If count = 2: Two agents mode - extract both "" sets
• If count >= 3: Multiple agents mode - extract all "" sets

All agents use Task tool - whether creating 1 or 10 agents.

Note: Agents inherit tools from parent - no need to specify tools field.

Phase 2: Load Templates Goal: Study framework patterns

Actions:

Load agent template immediately: !{Read @agent-with-phased-webfetch.md}

Determine plugin location from context (default: domain-plugin-builder)

Phase 3: Create Agent(s) Goal: Generate agent file(s) efficiently

Actions:

Decision: 1-2 agents = build directly, 3+ agents = use Task() for parallel

For 1-2 Agents:

Build directly - execute these steps immediately:

1. Load template: !{Read @agent-with-phased-webfetch.md}

2. Load color decision framework: !{Read @agent-color-decision.md}

3. For each agent, create the file: !{Write $BASE_PATH/agents/$AGENT_NAME.md}

Include:

• Frontmatter with name, description, model: inherit, color (from decision framework)
• NO tools field - agents inherit tools from parent
• "Available Tools & Resources" section specifying:
  • MCP servers (e.g., mcp__github, mcp__supabase)
  • Skills (e.g., Skill(plugin:skill-name))
  • Slash commands (e.g., SlashCommand(/plugin:command-name))
• Progressive WebFetch for documentation
• Keep under 300 lines

4. Validate: !{Bash ~/.claude/plugins/marketplaces/domain-plugin-builder/plugins/domain-plugin-builder/skills/build-assistant/scripts/validate-agent.sh $BASE_PATH/agents/$AGENT_NAME.md}

No need for Task() overhead when building 1-2 agents

For 3+ Agents:

CRITICAL: Send ALL Task() calls in a SINGLE MESSAGE for parallel execution!

For each agent, create a Task() call with subagent_type="domain-plugin-builder:agents-builder" that includes:

• Agent name and description
• Instructions to load templates from build-assistant/templates/agents/
• File path: $BASE_PATH/agents/{agent-name}.md
• Frontmatter: name, description, model: inherit, color (from agent-color-decision.md)
• NO tools field - agents inherit from parent
• Available Tools & Resources section (MCP servers, skills, slash commands)
• Progressive WebFetch for docs
• Keep under 300 lines
• Validate with validation script

Send ALL Task() calls together in ONE message - they will execute in parallel!

Only proceed to Phase 4 after all Task() calls complete.

Phase 4: Validation and Registration

Validate all created agents:

For each agent: !{bash ~/.claude/plugins/marketplaces/domain-plugin-builder/plugins/domain-plugin-builder/skills/build-assistant/scripts/validate-agent.sh $BASE_PATH/agents/$AGENT_NAME.md}

If validation fails, read errors and fix issues.

Note: Agents don't need settings.json registration (only commands do).

Phase 5: Git Commit and Push Goal: Save work immediately

Actions:

• Add all agent files to git: !{bash git add plugins//agents/.md}
• Commit with message: !{bash git commit -m "$(cat <<'EOF' feat: Add agent(s) - AGENT_NAMES

Complete agent structure with framework compliance.

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com EOF )"}

• Push to GitHub: !{bash git push origin master}

Phase 6: Sync to Airtable Goal: Sync ALL created agents to Airtable in bulk

Actions:

Use bulk sync script for efficiency:

Bash: python ~/.claude/plugins/marketplaces/domain-plugin-builder/plugins/domain-plugin-builder/scripts/bulk-sync-airtable.py --plugin={plugin-name} --marketplace={marketplace-name} --type=agents

This syncs ALL agents in parallel instead of one at a time.

DO NOT skip this phase! Airtable sync is critical for marketplace integration.

Phase 7: Self-Validation

Run validation script to verify all work completed:

!{bash ~/.claude/plugins/marketplaces/domain-plugin-builder/plugins/domain-plugin-builder/skills/build-assistant/scripts/validate-agent.sh $BASE_PATH/agents/*.md}

Mark all todos complete if validation passes.

Phase 8: Summary Goal: Report results

Actions:

Display results:

Agents Created: Plugin: $PLUGIN_NAME Mode: $BASE_PATH (marketplace mode if "plugins/", standalone if ".") Location: $BASE_PATH/agents/

Files:

• $AGENT_1.md - $DESC_1 ✅
• $AGENT_2.md - $DESC_2 ✅
• etc.

Validation: All passed ✅ Git Status: Committed and pushed ✅ Airtable Sync: Attempted ✅

Next Steps:

• Invoke agents via Task tool: Task(subagent_type="$PLUGIN_NAME:$AGENT_NAME")
• Use in commands and skills
• Test agent capabilities