Example routine
Jira delivery risk review
Review Jira projects for blocked, overdue, and unowned work against the plan.
Tools are not runnable in this preview.
Explore integrationsSuggested rhythm
Weekly
0 9 * * 1
America/Los_Angeles
Expected result
A weekly delivery-risk brief with blocked and overdue work, cited evidence, and proposed owners and next actions.
Built for
Engineering · Product
Works with
- Atlassian
What the routine does
Read the configured Jira project {{jiraProject}}, its boards, sprints, and issues, plus any linked Confluence plan pages. Identify blocked, overdue, or unowned work, compare progress against stated plan dates, and cite the issue or page behind every finding. Propose an owner and next action per risk without inventing status, and never create, transition, edit, or delete any Jira or Confluence content.
Inputs
- Jira project
{{jiraProject}}The Jira project key or name to review.
Example: MKT
Required MCP capabilities
- Read Jira projects, boards, and issues
- Read Confluence pages
Permission boundary
Connections do not grant blanket access. Discover the MCP tools, enable only the capabilities this responsibility needs, and give write-like actions a separate automatic-execution confirmation.
More engineering routines
Every weekday
GitHub issue triage
Keep the issue tracker answerable by triaging every new report before a human looks at the queue.
Weekly
Stale pull request review
Stop finished work from dying in review by naming what blocks each stalled pull request.
Weekly
Weekly error trend review
Notice which errors are actually trending before users report them, without staring at dashboards.
Weekly
Supabase database health review
Turn non-production database diagnostics into a prioritized weekly health brief without exposing customer records or changing state.