🗂️ Business recipe
Your Jira Standup Summary, Posted to Slack by Routines
Post a daily Jira standup summary to your team Slack channel, so everyone starts the day knowing what moved.
The exact prompt
Paste this into a new routine.
Look at my Jira project and summarize what changed since yesterday. List issues that moved status, anything newly assigned to the team, blockers or flagged tickets, and what is due today. Then post a short, skimmable summary to my team Slack channel, grouped by status, with the blockers called out at the top so nobody has to open the board to know where things stand.
Set the schedule. Keep the default weekday 9:00 AM so the summary lands before standup. cron: 0 9 * * 1-5
Set it up
Step 02Connect Jira and Slack
Connect Atlassian via its remote MCP (choose your Cloud site and read or write scope) and connect your Slack workspace with the channel picker.
Step 03Pick the Daily Jira Summary recipe
Choose Daily Jira Summary to Slack from the library, or paste the example prompt into a new routine.
Sample output
What a run looks like.
Saved to your local output history · stays on your Mac
Jira standup · 9:00 AM
Done
Moved to Done (4): checkout fix, onboarding copy, 2 bugs.
Blocked (1): API rate-limit ticket waiting on infra.
Due today (3): posted to #eng with owners tagged.
- Who it's for
- Team leads and project managers who want the team to start the day knowing what moved in Jira, without opening the board.
- What lands in your morning
- A weekday-morning Slack post that summarizes what changed in your Jira project overnight: issues moved, blockers, and what is due today.
FAQ
Questions about this recipe.
How does Routines read my Jira project?
Through Atlassian's remote MCP, connected with dynamic client registration and PKCE, no shipped client secret. You pick your Cloud site and whether the routine is read-only or read-write.
Which Slack channel does the summary post to?
The channel you name in the prompt, scoped with the Slack channel picker. The Slack connector supports posting, so the digest lands in your team channel automatically.
Can it cover more than one Jira project?
Yes. Name the projects or boards in the prompt and the summary spans them all, grouped however you ask.
Are my Jira and Slack tokens safe?
Yes. OAuth tokens live encrypted in local SQLite on your Mac and refresh silently, and no BinarCode server sits between you and Atlassian or Slack. The issues and messages themselves go to the AI to be summarized, through Routines AI, which stores none of them, or straight to your provider on your own key.
More Business recipes
Keep exploring
Competitor Watch
A Monday-morning intel brief on your competitors: new launches, pricing changes, and notable announcements, with what each move means for you.
Daily CRM Pipeline Summary
A weekday summary of your sales pipeline: which deals advanced, which went quiet, what is forecast to close, and the specific follow-ups worth making today.
Candidate Screening Brief
A weekday brief on new candidates from your hiring inbox: a fit read against the role, strengths and gaps, and tailored questions to ask in the first call.
Weekly Investor Update Draft
A Friday-afternoon investor update drafted from your week, highlights, key metrics, lowlights, and your specific asks, in a clean format ready to review and send.
Morning Briefing
A single written brief waiting for you at 7:30 AM: today's calendar with a prep note on each meeting, your email split into reply now and can wait, and the commitments you made that are still open.
Email Digest
A ranked digest of overnight unread mail, the must-reply messages at the top, the newsletters and noise summarized at the bottom, ready when you sit down.
Run Daily Jira Summary to Slack on your Mac.
Install Routines, paste the prompt, set the schedule. It runs locally and the output stays on your machine.
Step 01 · Install Routines. Download the DMG, drag to Applications, and sign in with Google once.