adding COE

council-of-experts/commands/add-expert.md

@@ -0,0 +1,46 @@
+---
+name: add-expert
+description: Instructions for adding a new expert agent to the Council of Experts roster.
+user-invocable: true
+---
+
+## Adding a New Expert to the Council of Experts
+
+To add a new expert agent, create a markdown file in the plugin's agents directory:
+
+**Location:** `~/.claude/plugins/council-of-experts/agents/<agent-name>.md`
+
+**Template:**
+
+```markdown
+---
+description: >-
+  One-paragraph description of this expert's specialization. Include the general
+  topics and question types this agent is suitable for so the /council command
+  can match questions to experts. Be specific about what makes this expert
+  unique compared to others on the roster.
+---
+
+You are [role description — who this expert IS, not what they do].
+
+[2-3 sentences establishing their expertise, perspective, and approach.]
+
+When given a research question or problem:
+- [Specific behavior 1]
+- [Specific behavior 2]
+- [Specific behavior 3]
+
+Be [key quality]. [Final instruction about output style.]
+```
+
+**Guidelines:**
+- **File name** becomes the agent identifier — use kebab-case (e.g., `legal-historian.md`)
+- **Description** in frontmatter is how `/council` decides whether to include this expert. Make it clear what topics match.
+- **System prompt** (body) should establish a persona, not just list tasks. The best agents have a point of view.
+- **Be specific** about what this expert notices that others wouldn't. Generic expertise isn't useful.
+- **Include anti-patterns** — what should this expert NOT do? (e.g., "Don't give legal advice" or "Don't speculate beyond the evidence")
+
+**Current roster:**
+Check `~/.claude/plugins/council-of-experts/agents/` for existing experts. Avoid duplicating perspectives already covered.
+
+**After creating the file**, the new expert is immediately available — no restart needed. The next `/council` invocation will see it in the roster.