Jira Sprint Runner
Jira sprint hygiene
The same sprint discipline for Jira. It audits for unestimated stories, missing acceptance criteria, unassigned work, tickets stuck beyond your team's norm, and subtasks out of sync with their parent. Findings are grouped by assignee so each person sees only their own list, and nothing transitions without approval.
Add to your OasisConnects with
Connect these once. Oasis holds the connection, and every agent you build after this can reuse it.
JiraRequired
ConfluenceOptional
SlackOptional- +Custom toolConnect any other tool from thousands of available integrations.
How it runs
- Foundation
Claude Managed Agent
- Model
- Claude Haiku 4.5
- Reasoning
- Low effort
- Per run
- Up to 30 turns
- Memory
- Learns across runs
- Browsing
- Off
- Category
- Engineering
- Jira
- Planning
- Agile
Frequently asked questions
Can Jira Sprint Runner find stories that entered a sprint without estimates?
Yes. It audits Jira for unestimated stories along with missing acceptance criteria, unassigned work, stale tickets and subtasks out of sync with their parent.
How does Jira Sprint Runner expose missing acceptance criteria?
It reports tickets whose acceptance criteria are missing as part of sprint hygiene findings, grouped by assignee so each person sees the work relevant to them.
What does Jira Sprint Runner consider a ticket stuck?
It flags tickets that have remained stuck beyond the team's normal threshold. The threshold comes from the team's norm rather than a universal number.
Will Jira Sprint Runner move a Jira issue after finding a sprint problem?
No. It audits and groups the findings, but no issue transitions without approval.
Agents like this one
Frontend Design Reviewer
Reviews UI changes for what code review misses. It checks the states nobody builds — empty, loading, error, long content, slow network — real breakpoints rather than the one the developer had open, and accessibility properly: keyboard path, focus visibility, contrast, reduced-motion. Findings are ordered by user impact, and subjective taste is left out unless it breaks an established pattern.
Try this Agent
Oasis PlatformEngineeringAPI Docs Writer
Documents endpoints from the code that implements them, not from what the last doc said. Every parameter gets its real type, requiredness, default and constraints, and every error the endpoint can return is documented with what triggers it — the half that's usually missing and the half developers need. Discrepancies between existing docs and current behaviour are listed separately as bugs.
Try this AgentOasis PlatformEngineeringPi Dev Assistant
A general hand in your local checkout. It defaults to reading and explaining, makes small changes when asked, and shows the diff rather than describing it. When a request is ambiguous it asks instead of picking, and it never runs destructive git operations or touches files outside the repo it was pointed at.
Try this AgentOasis PlatformEngineeringMCP Server Builder
Builds MCP servers that agents can actually use well. It designs the tool surface around real workflows rather than wrapping every API endpoint, because the tool list is a prompt and a bloated one degrades every call. Descriptions say when to use a tool and when not to, errors explain what to do differently, and each tool is tested against a realistic task.
Try this AgentOasis PlatformEngineeringRelease Notes Writer
Turns merged pull requests into release notes people actually read. Each user-visible change is translated into what it means for someone using the product, never the PR title or commit message, and internal refactors and dependency bumps are dropped. Breaking changes lead, with the migration step attached.
Try this AgentOasis PlatformEngineeringRelease Scribe
Reads the commits since your last tag and writes the changelog. Each user-visible change is translated into what it means for someone using the software, and internal refactors, dependency bumps and test-only changes are dropped. When a commit message is unclear it reads the diff rather than paraphrasing the subject line.
Try this AgentOasis PlatformEngineeringHermes Repo Agent
Runs long, self-directed jobs across your local repo — a sweep over many files, a dependency upgrade, a cleanup. It scopes the work and gets that agreed first, since a long job with the wrong definition is the most expensive failure here. It reports progress in batches as it goes, because silence for two hundred file edits isn't acceptable output.
Try this AgentOasis PlatformEngineeringError Triage
Reads your error tracker every morning and reports what's new, what's spiking and what's noise. Errors are grouped by underlying cause rather than by stack trace, because one bad deploy usually produces several traces and reporting them separately hides the single fix. Each group comes with the release it appeared in and the most likely culprit commit.
Try this AgentOasis PlatformEngineeringRefactor Planner
Maps out a refactor before anyone touches the code. It traces every caller, every test and every implicit contract the type system doesn't capture, then produces a staged plan where each stage leaves the system working. It names what could break at each stage — and says plainly when stable, rarely-touched code isn't worth refactoring at all.
Try this AgentOasis PlatformEngineeringKilo Feature Scaffolder
Lays down the boring skeleton of a new feature in your repo, in the shape this codebase already uses. It studies two or three comparable features first and copies their structure, naming and test layout, because consistency with the surrounding code matters more than any preferred structure. You start from a running stub with the genuinely undecided logic clearly marked.
Try this AgentOasis PlatformEngineering
Put Jira Sprint Runner to work today
Add it to your Oasis, review its setup, and hand it the first task.