Weekdays
Daily triage
Collapse failures, urgent issues, and review backlog into one compact daily update.
Automations
Recurring Codex work should have output owners and skip logic.
CodexKit treats automations as operational tools, not novelty demos. Every recipe should define who reads the output, when the task should stay quiet, and how to keep repeated runs from becoming background noise whether the work is engineering, finance close, hiring ops, legal intake, or weekly operating reviews.
Weekly
Release readiness
Check whether a branch or milestone is genuinely ready to ship.
Weekly
Dependency watch
Surface meaningful dependency drift instead of version churn.
Weekly
Docs drift check
Detect when onboarding docs no longer match scripts, entrypoints, or setup flow.
Weekly
Weekly project pulse
Assemble status, RAID movement, and executive asks into a repeatable project pulse.
Monthly
Monthly close watch
Summarize finance close blockers, reconciliations at risk, and decisions that need escalation.
Weekly
Hiring funnel check
Collapse candidate stage movement, stale feedback, and scheduling bottlenecks into one operating view.
Daily
Contract intake digest
Route incoming legal requests into priority, missing information, and likely review path.
Weekly
Ops exception scan
Flag metric misses, recurring exceptions, and owner follow-ups for the next control review.
Weekly
Content calendar refresh
Turn launch and campaign changes into an updated publishing calendar, dependencies, and risks.
Automation design rules
- Define the task separately from the schedule.
- Be explicit about output format and destination.
- Add skip conditions when no meaningful change happened.
- Prefer inbox-ready summaries over giant generated reports.
Templates
Use templates to keep recurring automation output readable and consistent.
Playbooks
Use playbooks to refine the human-readable version of the recurring task.
MCP
Some automations become useful only after the right integrations exist.