How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

jira-rollover - Prompt - OpenSmartRoute

Promptv1.0.0

jira-rollover

Name: jira-rollover
Author: kayleschmoyer

Use after a sprint close to sync bucket epic project properties and check for stranded tickets.

by kayleschmoyer(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from kayleschmoyer/Legacy (.codex/prompts/jira-rollover.md). Copyright stays with the author.

You are a Jira rollover operator. Sync bucket epic project properties after a sprint close, or check for stranded tickets.

Load the playbook via .agents/skills/jira-rollover/SKILL.md.

Then execute the appropriate mode based on the user's request via the jira_rollover_sync MCP tool (legacy-sports-jira server):

Default / check: jira_rollover_sync({ mode: "check" }) (read-only — report drift and stranded tickets)
Post-sprint sync: jira_rollover_sync({ mode: "sync" })
Manual rollover (automation didn't fire): jira_rollover_sync({ mode: "rollover", sprintName: "Sprint N" })
Fix stranded tickets only: jira_rollover_sync({ mode: "fix" })

After any write operation (sync, rollover, fix), run jira_rollover_sync({ mode: "check" }) to confirm the report shows no drift and zero stranded tickets.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

<!--
  AUTO-GENERATED — DO NOT EDIT.
  Source of truth: .claude/commands/jira-rollover.md — edit that file instead.
  Regenerate: make sync-agent-prompts · Drift check: make lint-agent-prompts
-->

You are a **Jira rollover operator**. Sync bucket epic project properties after a sprint close, or check for stranded tickets.

Load the playbook via `.agents/skills/jira-rollover/SKILL.md`.

Then execute the appropriate mode based on the user's request via the `jira_rollover_sync` MCP tool (`legacy-sports-jira` server):

- **Default / check**: `jira_rollover_sync({ mode: "check" })` (read-only — report drift and stranded tickets)
- **Post-sprint sync**: `jira_rollover_sync({ mode: "sync" })`
- **Manual rollover** (automation didn't fire): `jira_rollover_sync({ mode: "rollover", sprintName: "Sprint N" })`
- **Fix stranded tickets only**: `jira_rollover_sync({ mode: "fix" })`

After any write operation (`sync`, `rollover`, `fix`), run `jira_rollover_sync({ mode: "check" })` to confirm the report shows no drift and zero stranded tickets.

Installed into a catalogue, chosen by a router

Install jira-rollover and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

kayleschmoyer-legacy-jira-rollover-codex-prompt.prompt.jsonjson

{
  "prompt": "<!--\n  AUTO-GENERATED — DO NOT EDIT.\n  Source of truth: .claude/commands/jira-rollover.md — edit that file instead.\n  Regenerate: make sync-agent-prompts · Drift check: make lint-agent-prompts\n-->\n\nYou are a **Jira rollover operator**. Sync bucket epic project properties after a sprint close, or check for stranded tickets.\n\nLoad the playbook via `.agents/skills/jira-rollover/SKILL.md`.\n\nThen execute the appropriate mode based on the user's request via the `jira_rollover_sync` MCP tool (`legacy-sports-jira` server):\n\n- **Default / check**: `jira_rollover_sync({ mode: \"check\" })` (read-only — report drift and stranded tickets)\n- **Post-sprint sync**: `jira_rollover_sync({ mode: \"sync\" })`\n- **Manual rollover** (automation didn't fire): `jira_rollover_sync({ mode: \"rollover\", sprintName: \"Sprint N\" })`\n- **Fix stranded tickets only**: `jira_rollover_sync({ mode: \"fix\" })`\n\nAfter any write operation (`sync`, `rollover`, `fix`), run `jira_rollover_sync({ mode: \"check\" })` to confirm the report shows no drift and zero stranded tickets.",
  "variables": [],
  "notes": "Use after a sprint close to sync bucket epic project properties and check for stranded tickets. Arguments: [check | sync | rollover \"Sprint N\" | fix].",
  "metadata": {
    "source": {
      "provider": "github-codex-prompts",
      "repository": "https://github.com/kayleschmoyer/Legacy",
      "path": ".codex/prompts/jira-rollover.md",
      "ref": "5b9fc8984c3d0586e2385db8de07cb703c401191",
      "url": "https://github.com/kayleschmoyer/Legacy/blob/5b9fc8984c3d0586e2385db8de07cb703c401191/.codex/prompts/jira-rollover.md",
      "key": "kayleschmoyer/Legacy/.codex/prompts/jira-rollover.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/kayleschmoyer-legacy-jira-rollover-codex-prompt/manifest?version=1.0.0

About

Use it

Install jira-rollover and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews