fix: route all scheduled templates to #general (target: channel) + pulse_check chapter limit guard
This commit is contained in:
42
templates/daily_review.yml
Normal file
42
templates/daily_review.yml
Normal file
@@ -0,0 +1,42 @@
|
||||
name: daily_review
|
||||
description: "Daily operational pulse-check for Crimson Leaf. Reviews company activity, surfaces blockers, and identifies one priority action for the day."
|
||||
debug: true
|
||||
system: agent_prompt
|
||||
|
||||
agent_prompt:
|
||||
- "= identity.md"
|
||||
|
||||
sections:
|
||||
- agent
|
||||
- project
|
||||
- history
|
||||
- rag
|
||||
- message
|
||||
- instructions
|
||||
|
||||
steps:
|
||||
- type: think
|
||||
hint: |
|
||||
You are {agent.name}, conducting the daily Crimson Leaf operational review.
|
||||
|
||||
Review the company's current state and produce a concise daily briefing covering:
|
||||
|
||||
1. ACTIVITY STATUS -- What tasks completed or are in progress? What is the overall momentum?
|
||||
2. KEY METRICS -- Any notable numbers: tasks completed this week, companies active, revenue signals.
|
||||
3. TOP BLOCKER -- What single thing, if resolved, would most improve throughput?
|
||||
4. PRIORITY ACTION -- One concrete action for today. Be specific: what, who, and why now.
|
||||
5. FORWARD SIGNAL -- One thing to watch or prepare for in the next 48 hours.
|
||||
|
||||
Be direct and brief. This is an executive briefing, not a narrative essay.
|
||||
Avoid generic observations. Every point should be specific to Crimson Leaf's actual situation.
|
||||
|
||||
- type: close
|
||||
rag_update: true
|
||||
|
||||
adjudication:
|
||||
enabled: true
|
||||
pass_threshold: 65
|
||||
criteria:
|
||||
- "Briefing covers all five required sections"
|
||||
- "Priority action is concrete and assigned, not vague"
|
||||
- "Content is specific to Crimson Leaf, not generic business advice"
|
||||
Reference in New Issue
Block a user