Engineering routine templates
Scheduled AI agents for the dev workflow — issue triage, release digests, deployment summaries, standup prep — wired to GitHub, Jira, Linear, Vercel and your other tools over MCP.
Each weekday, triages new, stale, and needs-triage issues across the repos you pick — grouped, prioritized, with a suggested label and owner per issue.
Each weekday morning, a ranked read-only digest of what threatens your active sprint — blocked, stale, past-due, unassigned, and unestimated work — emailed with keys, owners, and links.
A weekday standup digest of overnight Jira activity, posted straight to your team's Slack.
Run Supabase's security and performance advisors every morning and get a digest of new issues.
Find failed Vercel deployments, pull their logs, and surface the likely cause — every morning.
Logs each repo's weekly releases as rows in a Google Sheet, so nothing slips.
Each weekday, turn raw Discord feedback into a deduped, triaged list of issues worth filing in Linear.
Every Friday, scan Cloudflare's developer docs for the Workers, Pages, and security features that matter to your setup — plus recent changelog posts — emailed as a prioritized digest.
A Monday-morning summary of every new release across the repos and dependencies you care about.
Every Thursday, ask DeepWiki what's new in the public GitHub repos you depend on — releases, breaking changes, and migration notes — emailed as a prioritized summary.
Every Monday, check Context7 for the current documented version, API, and migration notes of the libraries your project depends on — emailed as a short upgrade to-do list.
Every Monday, an active-cycle progress digest from Linear grouped by status, with at-risk and carried-over issues called out and linked back.
Auto-create a fresh retrospective board in Miro before each sprint retro — set up and waiting.