Sprint health monitor
ActiveReview the active sprint. Find blocked issues and work without an owner. Summarize what needs attention, with a suggested next step.
Daily at 9:00 AM
Last run 7h ago
24 runs
leera AgentsThe follow-through, built in.Your team builds.
Your team builds.
Agents keep it moving.
Put sprint checks, backlog reviews, and project updates on a schedule.
Less chasing the details. More moving the project forward.
Project context built inFlexible schedulesEvery run visible
Workspace automation
Agents
Routine work, handled. More room for what matters.
Backlog reviewer
ActiveReview the project backlog for missing acceptance criteria and unassigned work. List the issues that need a clearer brief before planning.
Weekly at 10:00 AM
SMTWTFS
Last run 6d ago
8 runs
Weekly report writer
PausedSummarize this week’s completed work, open blockers, and next priorities in Leera App. Keep the update focused on the release.
Weekly at 4:00 PM
SMTWTFS
Last run 2d ago
12 runs
Interactive example · Local sample data
For the work around the workYour best work needs focus.
Your best work needs focus.
Give the follow-through a home.
Checking what’s blocked. Finding what’s missing. Pulling together another update. These small jobs keep a project moving—and keep coming back. Give them an agent, so your team can give the next big thing its attention.
A clearer view, on schedule.
Bring blockers, missing owners, and stale work into a focused summary you can review.
Less starting from scratch.
Define the assignment once. Let the next run bring fresh project context to the same useful question.
Something you can act on.
Ask for issue references, open decisions, and suggested next steps. Keep the result with the run.
01 / A clear assignmentYou know what matters.
You know what matters.
Give it an agent.
The sprint check. The backlog review. The update you write every Friday. Start with one specific job, and give it a routine of its own.
ONE CLEAR OBJECTIVE. A REPEATABLE NEXT STEP.A good assignment, in three parts.
01
The context
Review the active sprint in the Leera App project.
02
The focus
Find blocked issues and work without an owner.
03
The useful outcome
Summarize what needs attention, with issue references and a suggested next step.
Start with a template. Make the objective yours.
Keep your attention on the decisions. Give the recurring checks a place in the background.
DEFINE ONCEThe job stays clear.
A focused objective gives each run a purpose.
RETURN REGULARLYThe context keeps moving.
Each execution works with the project as it stands.
KEEP BUILDINGThe result stays in reach.
Review the findings when it’s time to decide.
Start with a job worth repeatingA little help.
A little help.
Across a lot of your week.
Start with an agent template or your own brief. Make the objective specific to your project, your team, and the decision you want to make.
Each morning
Sprint healthSee the friction. Find the next move.
Review blocked work, missing ownership, and changes in sprint scope before your next team check-in.
COME BACK TO
A sprint summary with the issues that need attention.
See an example objective +
Review the active sprint. List blocked and unassigned issues with their issue keys, owners, and suggested next steps. Call out changes in scope. If nothing needs attention, say so briefly.
Before planning
Planning prepArrive ready to make decisions.
Find the gaps in candidate issues while there’s still time to sharpen the brief and discuss priorities.
COME BACK TO
A planning checklist of missing estimates and acceptance criteria.
See an example objective +
Review the highest-priority backlog issues for the next sprint. Identify missing estimates, acceptance criteria, and dependencies. Group the findings by issue and summarize what needs a decision before planning.
Every week
Stakeholder updatesTell the story behind the status.
Bring completed work, open risks, and next priorities together in a readable project update.
COME BACK TO
A draft summary ready for your review.
See an example objective +
Summarize this week’s project activity for stakeholders. Group the update into progress, risks, and next priorities. Reference the relevant issues and keep the summary focused on the release.
A regular review
Backlog hygieneKeep the backlog worth coming back to.
Bring overlooked issues and work without recent updates back into the conversation.
COME BACK TO
A focused list of stale work to revisit.
See an example objective +
Review open backlog issues with no updates in the last 14 days. Include the owner, last activity, and current status. Suggest which issues need clarification or a fresh priority discussion.
At release time
Release notesGive shipped work its moment.
Turn completed issues into a clear draft of what changed, organized for the people who need to know.
COME BACK TO
Release notes grouped into features, fixes, and improvements.
See an example objective +
Draft release notes from the completed issues in this release. Group them into features, fixes, and improvements. Explain each change in plain language and include its issue reference.
Through the sprint
Dependency reviewFind what’s holding things up.
Review the relationships behind blocked work and identify the decisions or tasks that need to move first.
COME BACK TO
A dependency summary with a suggested order of follow-up.
See an example objective +
Review blocked issues and their linked dependencies. Identify the blocking issue, its owner, and the work it affects. Summarize which dependencies need follow-up and why.
02 / Find your rhythmRight work.
Right work.
Right time.
Every time it’s due.
A morning sprint check. A weekly review. A monthly summary. Choose a cadence, set the time and timezone, and let the schedule carry the reminder.
Hourly, daily, weekly, or monthly. You choose.
See what happens next WorkspaceEdit Agent
From project activity to shared perspectiveFriday comes around.
Friday comes around.
The update takes shape.
The team has been building all week. Give an agent the brief for your recurring update: what shipped, what’s at risk, and what comes next.
Return to a draft grounded in the project. Review the details, add your perspective, and bring a clearer story to the next conversation.
- Keep the focus on the audience and the decision.
- Ask for the issue references behind the summary.
- Find the output alongside its execution history.
A USEFUL BRIEF GOES A LONG WAY
“Summarize this week’s progress, open blockers, and next priorities. Keep it focused on the release.”
Every Friday · Ready for your review03 / A visible resultEvery run.
Every run.
There to be understood.
Open an execution to see its status, messages, and output. Follow the work, investigate a failure, and use what you learn to refine the next run.
Activity
Every run, across all your agents.
Sprint health monitorDaily at 9:00 AM
- Agent09:00 AM
Reviewing Sprint 08 and its 24 linked issues.
- Agent09:00 AM
Sprint health summary
18 of 24 issues are complete. Two blockers need attention:
- LE-128 — Fix the invitation flow: Alex is adding an expired-link recovery step.
- LE-132 — Confirm API approval: Maya is following up on the release review.
All active issues have an owner.
- Agent09:00 AM
Reviewing Sprint 08 and its 24 linked issues.
- Agent09:00 AM
Sprint health summary
18 of 24 issues are complete. Two blockers need attention:
- LE-128 — Fix the invitation flow: Alex is adding an expired-link recovery step.
- LE-132 — Confirm API approval: Maya is following up on the release review.
All active issues have an owner.
- Agent09:00 AM
The configured AI provider could not be reached. No summary was generated. Check provider availability before running again.
A record you can return to.Example execution history
04 / Your agent. Your call.A little autonomy.
A little autonomy.
A clear sense of control.
Shape the assignment around the way your team works. Check the result, adjust the details, and change the routine when priorities move.
Give it the right tools.
Match the available tools and model to the job you want the agent to do.
Try it on your terms.
Trigger a manual run to check an objective or get a fresh result before the next scheduled run.
Keep the routine yours.
Refine the objective, adjust the schedule, or deactivate the agent when the work changes.
A small start. A useful routine.Your first agent starts
Your first agent starts
with one good assignment.
01
Pick the work you keep repeating.
Choose a template or write a focused objective. Include the project, the question, and what a useful result should contain.
02
Give it a rhythm. Try a run.
Choose the available tools and model, set the schedule and timezone, then trigger a manual run against work you know.
03
Read the result. Make it yours.
Inspect the messages and output. Refine the objective until the routine produces the kind of detail your team can use.
Start with a conversation.
Explore a question with AI before turning it into a recurring assignment.
Explore leera AIBring people into the picture.
Collect individual team updates in one coordinated report.
Explore coordinationYour intelligence. Your choice.
Choose the AI provider and model behind your workspace.
Bring your own modelThe practical details
A little more clarity.
What are Leera AI Agents?+
Agents carry out a focused project task on a schedule. Give an agent an objective, configure the tools and model available to it, and review each run in its execution history. Start with a template for a sprint check, backlog review, or project report, then adapt the assignment to your team.
Which schedules can we use?+
Choose an hourly, daily, weekly, or monthly schedule. Configure the time and timezone for the task. You can also deactivate an agent when the routine is no longer needed.
How are agents different from chatting with Leera AI?+
A conversation starts when you ask a question. An agent gives a recurring assignment an objective and a schedule, then carries it out when it is due. Use chat to explore a question and agents for the focused checks or summaries you want to repeat.
Do we need to write code to create an agent?+
You can start from a template or write an objective in plain language using the agent configuration screen. Choose the tools and model available to the task, set the schedule, and try a manual run to check the result.
What makes a good first assignment?+
Choose a task you already repeat and can easily evaluate: a morning sprint check, a backlog readiness review, or a weekly project summary. Specify the project, what to look for, and how the output should be organized. Run it once, inspect the findings, and refine the objective as needed.
Can we run an agent without waiting for the schedule?+
Yes. Agents support manual triggering as well as scheduled execution. Use a manual run to check a new objective, investigate an issue, or generate a fresh result when the team needs it.
How do we investigate a failed run?+
Open the agent’s execution history and inspect its status and messages. Check the task configuration, permissions, and provider setup before retrying. Narrow the objective if the agent is attempting too much in a single run.
Are these examples connected to my workspace?+
No. The agent examples, schedule controls, and execution history on this page use illustrative data. Trying them does not create an agent or change your workspace. Open Leera to configure and run your own agent.
leera Agents
Your next big thing needs you.Give the routine an agent.
Start with the check you keep repeating.
Make room for the work you want to be doing.