adding COE
This commit is contained in:
46
council-of-experts/commands/add-expert.md
Normal file
46
council-of-experts/commands/add-expert.md
Normal file
@@ -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.
|
||||
48
council-of-experts/commands/council.md
Normal file
48
council-of-experts/commands/council.md
Normal file
@@ -0,0 +1,48 @@
|
||||
---
|
||||
name: council
|
||||
description: Convene a council of expert perspectives on a hard question. Selects 2-5 agents that best match the topic, runs them in parallel, then synthesizes their perspectives into a structured briefing.
|
||||
user-invocable: true
|
||||
arguments:
|
||||
- name: question
|
||||
description: The question or problem to present to the council
|
||||
required: true
|
||||
---
|
||||
|
||||
You have been asked to convene a Council of Experts to address the following question:
|
||||
|
||||
$ARGUMENTS
|
||||
|
||||
## Instructions
|
||||
|
||||
1. **Review the question carefully.** Understand the domain, the specific problem, and what kind of expertise would help.
|
||||
|
||||
2. **Select 2-5 expert agents** from the council-of-experts plugin's agents/ directory. Choose agents whose described expertise best matches the question's domain. Read the agent descriptions to understand their specializations. You do not need to use all agents — pick only those whose perspective would be genuinely useful. Prefer agents from the council-of-experts plugin when available. You may also use other available agents if they are a better fit for the specific question.
|
||||
|
||||
3. **Launch all selected agents in parallel** using the Agent tool. Each agent should receive:
|
||||
- The original question exactly as stated
|
||||
- Context about what the user is working on (if apparent from conversation history)
|
||||
- An instruction to provide their expert perspective, concrete suggestions, and specific next steps
|
||||
|
||||
4. **After all agents return**, synthesize their responses into a structured briefing:
|
||||
|
||||
### Council Members Consulted
|
||||
List each agent consulted and why they were selected.
|
||||
|
||||
### Key Perspectives
|
||||
Summarize each agent's unique contribution — what did they see that the others might not?
|
||||
|
||||
### Points of Agreement
|
||||
Where do multiple experts converge on the same conclusion or recommendation?
|
||||
|
||||
### Points of Disagreement
|
||||
Where do experts disagree, and what drives the disagreement?
|
||||
|
||||
### Suggested Next Steps
|
||||
A prioritized, actionable list combining the best recommendations from all experts. Note which expert suggested each step.
|
||||
|
||||
## Important
|
||||
- The Skeptic agent is almost always useful — include it unless the question is purely factual with no interpretation.
|
||||
- Do NOT summarize agents' responses verbatim. Synthesize and cross-reference.
|
||||
- If agents surface the same insight independently, that's a strong signal — highlight it.
|
||||
- If an agent raises a concern no one else did, that's also worth highlighting.
|
||||
- Keep the briefing concise and actionable. The user wants clarity, not volume.
|
||||
Reference in New Issue
Block a user