Use cases
Start from the problem.
Each page here describes one recurring responsibility: the problem, what teams do today, the outcome a routine owns, and exactly what access it needs — including what it deliberately cannot do.
- Engineering · Support
Issue triage done before standup
New issues arrive labeled, deduplicated, and prioritized every weekday morning, so maintainers start from a clean queue instead of a backlog.
2 routines
- Founders · Finance · Customer success
Revenue answers without spreadsheet Fridays
Quarterly revenue narratives and weekly churn-risk briefs assembled from Stripe with read-only access, instead of a day of manual exports.
2 routines
- Founders · Engineering
A weekly security review without a security team
Put codebase review and advisory triage on a weekly schedule with read-only access, so risks surface while they are still small.
2 routines
- Marketing · Growth
SEO upkeep that actually recurs
Weekly search audits that end in a reviewable pull request, plus competitor page monitoring that quotes exactly what changed.
2 routines
Your recurring work is probably here.
And if it is not, the routine library covers more ground — or start from a blank routine and describe the responsibility yourself.