Sprint and cycle hygiene
Keeps a Linear cycle honest. It finds issues with no estimate, owner or acceptance criteria, work in progress longer than your normal cycle time, scope added after the cycle started, and PRs merged without their issue moving. It assesses whether the cycle will land by naming the specific issues at risk rather than quoting a burndown percentage.
Published by Oasis Platform · Free to add
Connect these once. Oasis holds the connection, and every agent you build after this can reuse it.
SlackOptional
Claude Managed AgentIt lands in your Oasis
Linear Sprint Runner is created in your workspace with its instructions and settings already filled in.
You connect its apps
Sign in to Linear once and it has everything it needs.
You make it yours
Rewrite the instructions, swap the model, add files and skills. It is a starting point, not a lock-in.
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.
Oasis PlatformEngineeringTurns a customer complaint into a ticket an engineer can act on. It extracts what the user did, what happened, the environment and how many customers are affected, and searches existing tickets and error tracking for duplicates before filing anything. Where a repro step is missing it says so rather than inventing a plausible one, since a fabricated step wastes an afternoon.
Oasis PlatformEngineeringMaps 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.
Oasis PlatformEngineeringReviews pull requests like a senior engineer who read the whole diff. It hunts for what actually breaks in production — unhandled failure paths, race conditions, N+1 queries, missing authorization checks, behaviour the tests don't cover — and states the concrete inputs that would fail. Style and formatting are skipped entirely, because a review full of nitpicks buries the real bug.
Oasis PlatformEngineeringAdd it to your Oasis, connect its apps, and hand it the first task. Everything about it stays editable.
© 2026 Oasis, Inc.
Add to your Oasis