Sprint end
Write the sprint report
Pulls done, carried over and added work into a one-page report.
Standup summary agentThe status, without the status meeting.
Each weekday it reads yesterday's commits, reviews and ticket moves. It posts one line per person: done, next and stuck.
Your first signup includes $50 in free credits.
Weekdays · 9:00
Skip the stand-up status
- Reads
- GitHub and Jira activity
- Grows
- A status per person
- Lands in
- Slack
Ask for it once, in plain words.
No flowchart to draw. Describe the job in chat. TulipFarm sets up the agent and its workflow, and shows you both before anything runs.
You
Every weekday at 9, read yesterday's pull requests and ticket moves for my team. Post a short stand-up in #team: done, next and stuck for each person. Show me first.
TulipFarm
I made an agent called Stand-up summary and a weekday 9:00 schedule. It reads GitHub and Jira. Posting to Slack asks you first. Activate it?
ActivateEdit first
One morning, start to finish.
Every run is saved as an agent task you can open, check and rerun.
- Schedule
Weekdays at 9:00
Run startedStarted - Reads
Yesterday's pull requests and reviews in GitHub
9 items - Reads
Ticket moves in Jira
12 moves - Writes
One status per person, using your stand-up skill
5 statuses - Asks first
Post the stand-up to the team channel
Approved - Posts
Message in Slack
Delivered 9:02Completed
The stand-up at 9:02.
Three short lines per person. Stuck items are first, so the call can focus on them.
#teamStand-up summary APP · 9:02
Stand-up · yesterday and today
Person 1
- Done: merged the share links change.
- Next: tests for expired links.
- Stuck: none.
Person 2
- Done: reviewed 2 pull requests.
- Next: the date bug.
- Stuck: waiting on a design answer.
What gets planted.
Three parts you own and can change at any time.
- Agent
Stand-up summary
Reads activity and writes the status.
- Skill
Stand-up format
Done, next, stuck. Three short lines.
- Workflow
Weekdays 9:00
Runs each weekday with your access.
Uses
- GitHub
- Jira
- Slack
Add if you use it
Google Calendar
MCPLinear
Confluence
It reads quietly. It asks before it acts.
Reads without asking
- Pull requests and reviews
- Ticket moves in Jira
- The list of people on your team
Asks you first
- Posting to Slack
- Commenting on a ticket
It uses your own connections, so it never sees more than you can.
Grow it your way.
Let people add notes
Read replies in the channel and fold them into the next summary.
Only blockers
Post only the stuck items and skip the rest.
Async days
Run it on days without a call, and keep the call for the others.
Questions, answered.
Does it track people?
It reads the same public work your team already sees in GitHub and Jira. It does not read private messages.
What if someone did work outside GitHub?
The summary will miss it. People can reply to the post to add it.
Does it post without me?
No. Posting to Slack asks you first.
Weekdays · 10:00
Chase stale pull requests
Finds reviews stuck for days and nudges the right person.
Weekdays · 7:30
Start the day with a briefing
Meetings, urgent mail and open tasks, in one Slack message each morning.
Start the day without a status call.
Public beta, open to everyone. Your first signup includes $50 in free credits.