Agent Event Watch Workflow
Rule
When a significant upcoming event could change strategy or trigger action, create a named watch task documenting what to look for and what to do when the result appears.
Context
Events like trade settlements, deployment completions, PR reviews, or external data arrivals that are time-bounded, appear in a predictable location, and map to a decision or action.
Detection
- An upcoming event produces data that triggers a decision (scale/hold/reduce)
- The result appears at a known location at a predictable time
- Missing the analysis means acting on stale information
- NOT for routine daily monitoring already handled by scheduled sessions
Pattern
Watch task structure (4 sections):
- Context: What the event is, why it matters, baseline metrics
- Trigger: Exact condition that fires the task (file path, PR state, etc.)
- Analysis: What to compute once data is in
- Action: Exactly what to do, in order
Trigger check — built into Phase 1 of every session:
# File-based trigger
[[ -f "path/to/result" ]] && echo "TRIGGERED"
# GitHub trigger
gh pr view 123 --json state -q '.state'
When triggered: Act in the same session. Don't defer. Pre-defined thresholds map outcome to action (scale up / hold / reduce).
Outcome
- Timely analysis — results processed the session they appear
- Full context — baselines pre-captured, no re-research needed
- Clear decisions — pre-defined thresholds prevent post-hoc bias