Weekdays · 9:00
Skip the stand-up status
Builds each person's yesterday and today from GitHub and Jira.
Sprint report agentThe recap, drafted for you.
At the end of each sprint it reads the board and the merged work. It drafts a one-page report: what shipped, what carried over and what was added.
Your first signup includes $50 in free credits.
Sprint end
Write the sprint report
- Reads
- Sprint board, merged work
- Grows
- A one-page report
- Lands in
- Google Docs
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
On the last Friday of each sprint, read the sprint board in Jira and the pull requests merged. Write a one-page report: shipped, carried over, added mid-sprint, and why. Put it in Docs.
TulipFarm
I made an agent called Sprint reporter and a schedule for sprint end. It reads Jira and GitHub. Creating the doc asks you first. Activate it?
ActivateEdit first
One sprint end, start to finish.
Every run is saved as an agent task you can open, check and rerun.
- Schedule
Every other Friday at 15:00
Run startedStarted - Reads
The sprint board in Jira
31 tickets - Reads
Merged pull requests in GitHub
22 merged - Writes
A report, using your sprint skill
1 draft - Asks first
Create the report in Google Docs
Approved - Creates
Sprint report doc
Doc readyCompleted
A recap you edit in five minutes.
Counts come from the board. The reasons come from ticket comments.
Google DocsSprint report · this sprint
Shipped
- Share links, first version.
- The date bug fix.
- 23 of 31 tickets done.
Carried over
- 5 tickets. Two wait on a design answer.
Added mid-sprint
- 3 tickets. One was an urgent customer bug.
What gets planted.
Three parts you own and can change at any time.
- Agent
Sprint reporter
Reads the board and writes the recap.
- Skill
Report format
One page, three sections, no blame.
- Workflow
Sprint end
Runs on the day your sprint ends.
Uses
- Jira
- GitHub
- Google Docs
Add if you use it
- Slack
Confluence
MCPLinear
It reads quietly. It asks before it acts.
Reads without asking
- The sprint board in Jira
- Merged pull requests
- Comments on carried-over tickets
Asks you first
- Creating the report doc
- Posting the link to Slack
It uses your own connections, so it never sees more than you can.
Grow it your way.
Share with leaders
Add a step that posts the link to a leadership channel.
Compare sprints
Keep past reports in a folder so the agent can note the trend in words.
Post to Confluence
Create the report as a Confluence page instead.
Questions, answered.
Does it grade the team?
No. It counts and explains. Your skill tells it to stay neutral.
How does it know when a sprint ends?
You set the schedule. TulipFarm does not read sprint dates from Jira on its own.
Can I edit the report?
Yes. It is a normal Google Doc. Nothing is shared until you approve it.
Mondays · 9:00
Keep the roadmap current
Reads ticket status each Monday and drafts the roadmap update.
Fridays · 14:00
Run the weekly ops review
Gathers the week's numbers and open items into one review page.
Close the sprint with a clean page.
Public beta, open to everyone. Your first signup includes $50 in free credits.