Implements audit-harness-inspired session lifecycle: audit session creation/end/recover/report-daily with JSONL buffer and graded context recovery (L0-L4). Guideline service for behavioral compliance rules (condition/action model with criticality). Correction service for persistent user correction tracking across agent sessions. 8 supporting skills: audit-start/end/report-daily/recover + command variants for slash-command integration.
2.3 KiB
2.3 KiB
name, description
| name | description |
|---|---|
| audit-report-daily | Generate a daily work report from audit data. Every number traces to a source file. Use when user says "/report-daily", "daily report", "what did I do today". |
/report-daily — Audit-Driven Daily Report
Trigger
/report-daily # today
/report-daily 20260319 # specific date
/report-daily review # with morning self-review
Data Sources
| Section | Source |
|---|---|
| Task overview | .boo/runs/index.json |
| Operation stats | */audit_trail.jsonl tool records |
| Changes | trail entries with edit/create/delete |
| User feedback | user_correction entries in trail |
| Anomalies | */anomalies.json |
| Backlog | previous day's daily report §6 |
Every number must trace to a file. Do not fill from memory.
Steps
1. Collect data
- Read index.json, filter sessions for target date
- Read each session's audit_trail.jsonl
- Read pending (unflushed data)
- Read previous day's report §6 (backlog) if exists
2. Generate report
Write to .boo/runs/daily/{YYYYMMDD}_daily.md:
# Daily Report | <DATE>
> Source: .boo/runs/index.json + audit_trails
## 1. Task Overview
| # | Type | Session | Task | Status | Records |
## 2. Operation Stats
| Metric | Count |
|--------|-------|
| Write/Edit | N |
| Bash | N |
| AUDIT blocks | N |
## 3. Changes
| Time | File | Change |
## 4. User Feedback & Corrections
| Feedback | Persisted To |
## 5. Anomaly Alerts
- <alerts from anomalies.json>
## 6. Backlog
- previous day's todos
- current status
## 7. Integrity
- All sessions have records: ✅/❌
- Corrections persisted: ✅/❌
3. If /report-daily review
After report, additionally:
- Check: yesterday's anomalies all addressed?
- Check: user feedback converted to improvements?
- Check: backlog items completed?
- Write
.boo/runs/daily/{YYYYMMDD}_morning_review.md - Output recommended priorities for today
=== Morning Self-Review ===
Trend: <up/down/flat compared to last 3 days>
Anomalies resolved: N/M
Backlog cleared: N/M
Recommended priorities:
1. <...>
2. <...>
Notes
- If no sessions today, generate empty report with "No activity"
- Report itself should write one [AUDIT] block
- Historical reports are append-only — corrections go in new report
- Every number must cite its source file