Add aggregator agent, strategy template, research templates; fix ASCII in existing templates
- agents/aggregator/: new Aggregator specialist agent (agent.yml + identity.md) - agents/voss/agent.yml: add aggregator to manages, add research_brief/intelligence_report templates - templates/strategy.yml: new intake routing template for InputFromUser strategy type - templates/research_brief.yml: new research brief output template - templates/intelligence_report.yml: new intelligence report template - skills/: add IntelligenceFormatGuide, ResearchMethodGuide, skills.md - templates/*.yml: fix em-dash Unicode violations -> ASCII double-hyphens Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
81
templates/intelligence_report.yml
Normal file
81
templates/intelligence_report.yml
Normal file
@@ -0,0 +1,81 @@
|
||||
name: intelligence_report
|
||||
description: "Comprehensive intelligence report on a domain, market, or topic. Longer-form than research_brief. Suitable for weekly cadence or high-stakes decision support."
|
||||
debug: true
|
||||
system: agent_prompt
|
||||
|
||||
agent_prompt:
|
||||
- "= identity.md"
|
||||
|
||||
skills:
|
||||
- "guides/ResearchMethodGuide.md"
|
||||
- "guides/IntelligenceFormatGuide.md"
|
||||
|
||||
sections:
|
||||
- agent
|
||||
- project
|
||||
- history
|
||||
- rag
|
||||
- message
|
||||
- skills
|
||||
- instructions
|
||||
|
||||
steps:
|
||||
- type: think
|
||||
hint: |
|
||||
You are {agent.name} at Crimson Leaf Research, producing a weekly intelligence report.
|
||||
|
||||
This is a comprehensive report, not a brief. Apply rigorous analytical discipline.
|
||||
|
||||
REPORT STRUCTURE:
|
||||
|
||||
1. SITUATION OVERVIEW
|
||||
Current state of the domain, market, or topic under review.
|
||||
What has changed since the last cycle? What is stable?
|
||||
|
||||
2. SIGNAL ANALYSIS
|
||||
3-5 significant signals (trends, events, data points, competitive moves).
|
||||
For each signal: what it is, why it matters, confidence level (HIGH/MEDIUM/LOW).
|
||||
|
||||
3. THREAT ASSESSMENT
|
||||
What risks or adverse developments are present or emerging?
|
||||
Rank by probability and impact. Be specific, not generic.
|
||||
|
||||
4. OPPORTUNITY SCAN
|
||||
Where does a clear advantage or untapped position exist?
|
||||
Each opportunity must be specific enough to act on.
|
||||
|
||||
5. COMPETITIVE LANDSCAPE (if applicable)
|
||||
Who else is operating in this space? What are they doing well or poorly?
|
||||
What can Crimson Leaf exploit from their weaknesses?
|
||||
|
||||
6. RECOMMENDED ACTIONS
|
||||
Ordered list of 3-5 concrete actions for Crimson Leaf based on this analysis.
|
||||
Each action: what, who owns it, urgency (immediate/this week/this month).
|
||||
|
||||
7. WATCH LIST
|
||||
2-3 developments to monitor before the next report cycle.
|
||||
|
||||
Tone: intelligence directorate, not consulting firm. Precise, direct, adversarially rigorous.
|
||||
Length: 600-1200 words. Do not pad. Every paragraph must earn its place.
|
||||
|
||||
- type: verify
|
||||
checklist:
|
||||
- "Report covers all seven required sections"
|
||||
- "Signal analysis includes confidence ratings"
|
||||
- "Recommended actions are specific and assigned"
|
||||
- "No vague, generic observations -- every claim is specific to the domain"
|
||||
on_fail: revise
|
||||
max_retries: 1
|
||||
|
||||
- type: close
|
||||
rag_update: true
|
||||
|
||||
adjudication:
|
||||
enabled: true
|
||||
pass_threshold: 72
|
||||
criteria:
|
||||
- "All seven sections present and substantive"
|
||||
- "Signal analysis is specific and confidence-rated"
|
||||
- "Recommended actions are concrete and actionable"
|
||||
- "Report demonstrates analytical rigor, not superficial summary"
|
||||
- "Competitive landscape included where relevant"
|
||||
Reference in New Issue
Block a user