create-teamlisted

Create a team of specialized Claude Code agents based on the forge analysis. Agents are written to `~/.claude/agents/` so they have full subagent spawning support. ## Before Starting 1. Read `.context/forge-analysis.md` — this contains the project analysis from `/claude-army:analyze` 2. If the file doesn't exist, tell the user to run `/claude-army:analyze` first 3. Read the templates in `${CLAUDE_PLUGIN_ROOT}/templates/` for agent archetypes ## Agent Creation Process For each agent, read the matching template from `${CLAUDE_PLUGIN_ROOT}/templates/`, fill in project-specific details from the analysis, and write to `~/.claude/agents/`. ### Naming Convention All agents use the prefix `<project>-`: - `<project>-researcher.md` - `<project>-builder.md` - `<project>-reviewer.md` - `<project>-challenger.md` - `<project>-submitter.md` - `<project>-orchestrator.md` - `<project>-expert.md` - `<project>-test-writer.md` ### What Goes Into Each Agent **Researcher** — from analysis: - What information the builder needs - What verification is required - Pre-checks (duplicates, open PRs) **Builder** — from analysis: - Code patterns section → exact templates - Registration/integration pattern - Build/generate commands **Reviewer** — from analysis: - Linter rules - Test conventions - PR checklist - CI requirements **Challenger** — from analysis: - Lead reviewer name - Tiered review patterns with exact quotes - Things NOT to flag - Fix routing to other agents **Submitter** — from ana