Routine Patterns — What Engineers Actually Use Them For
Four high-value production patterns cover the majority of Routine use cases: deploy verification, nightly backlog triage, documentation drift detection, and dependency security audits. Each pattern has distinct trigger requirements, connector needs, and prompt design characteristics.
Quick Reference
- →Deploy verification: GitHub webhook on CI success, replaces manual post-deploy checklist
- →Nightly backlog triage: scheduled daily, batches 24h of issues into a priority-ranked digest
- →Documentation drift: scheduled weekly, flags outdated docs and opens PRs for stale sections
- →Dependency security audit: scheduled daily, pushes patches to claude/security-patch-* branches
- →Best Routine tasks: well-defined scope, observable output, clear success criteria
- →Avoid Routines for: tasks requiring approval, ambiguous scope, coordination between people
- →Each pattern includes a distinct failure mode to guard against in prompt design
Design Principles for High-Value Routines
Not every engineering task is a good Routine candidate. The patterns that work reliably share a common structure: the task has a well-defined scope, the output is observable, and there are clear success criteria that Claude can verify without asking anyone. When these three conditions are met, Routines produce consistent value at low operational overhead.
| Characteristic | Good Routine Candidate | Poor Routine Candidate |
|---|---|---|
| Scope | Bounded — specific files, directories, or event types | Open-ended — 'check everything', 'review the codebase' |
| Output | Observable — Slack message, PR, issue with defined format | Subjective — 'improve code quality', 'make it better' |
| Success criteria | Claude can verify: did endpoint return 200? Is CVE present? | Requires human judgment: 'does this look right?' |
| Frequency | Recurring — daily, weekly, or event-driven | One-off — better handled interactively |
| Coordination | Single actor — Claude produces the output | Multi-party — requires approval or human input mid-run |
Before building a Routine, ask: 'Can Claude determine on its own whether this run succeeded?' If the answer requires human review to confirm correctness, the task isn't a good Routine candidate yet. Either scope it down to a sub-task that is verifiable, or keep it interactive.