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.

start-pr - Prompt - OpenSmartRoute

Name: start-pr
Author: Epistemic-Me

Prompt file imported from Epistemic-Me/ai-dlc-workshop (.cursor/commands/start-pr.md). Copyright stays with the author.

/start-pr

Type the arguments after the command, for example /start-pr <TICKET> <short-name>.

Start a PR for one backlog ticket: create the branch and the planning docs, then do the first research pass. Do not write code.

Arguments: the ticket ID and a short name, for example BUG-01 merge-cart-lines.

Steps

Read backlog/<TICKET>.md, AGENTS.md, docs/.context/ARCHITECTURE.md, and docs/SPEC-CHECKLIST.md. If the ticket file does not exist, stop and say so.
Create the branch: git checkout -b feature/pr-<TICKET>-<short-name>.
Create docs/prs/planning/<today's date as YYYY-MM-DD>-PR-<TICKET>-<short-name>/.
Copy the five files from docs/prs/_TEMPLATE/ into that folder. Replace <TICKET>, <short-name>, and the date.
Fill RESEARCH.md: the problem (with evidence from the ticket), the tree node it serves, what exists today (with file paths you read), two options with trade-offs, your recommendation, and the risks.
Commit only the docs folder: git add docs/prs/planning/<folder> && git commit -m "docs: start <TICKET> <short-name>".
Report the branch, the folder, and the open questions. Then ask me what you are missing.

Do not fill TEST-STRATEGY.md or IMPLEMENTATION-PLAN.md until I answer. Do not edit any code.

No commands set up?

Paste this instead:

Create branch feature/pr-<TICKET>-<short-name> and
docs/prs/planning/<today's date>-PR-<TICKET>-<short-name>/. Copy the five
templates from docs/prs/_TEMPLATE/. Read backlog/<TICKET>.md and write
RESEARCH.md: the problem, what exists today (with file references), two
options with trade-offs, your recommendation and the risks. Then ask me
what you're missing. Don't edit code.

Install start-pr 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.

{ "prompt": "# /start-pr <TICKET> <short-name>\n\nType the arguments after the command, for example `/start-pr <TICKET> <short-name>`.\n\nStart a PR for one backlog ticket: create the branch and the planning docs, then do the first research pass. Do not write code.\n\nArguments: the ticket ID and a short name, for example `BUG-01 merge-cart-lines`.\n\n## Steps\n\n1. Read `backlog/<TICKET>.md`, `AGENTS.md`, `docs/.context/ARCHITECTURE.md`, and `docs/SPEC-CHECKLIST.md`. If the ticket file does not exist, stop and say so.\n2. Create the branch: `git checkout -b feature/pr-<TICKET>-<short-name>`.\n3. Create `docs/prs/planning/<today's date as YYYY-MM-DD>-PR-<TICKET>-<short-name>/`.\n4. Copy the five files from `docs/prs/_TEMPLATE/` into that folder. Replace `<TICKET>`, `<short-name>`, and the date.\n5. Fill `RESEARCH.md`: the problem (with evidence from the ticket), the tree node it serves, what exists today (with file paths you read), two options with trade-offs, your recommendation, and the risks.\n6. Commit only the docs folder: `git add docs/prs/planning/<folder> && git commit -m \"docs: start <TICKET> <short-name>\"`.\n7. Report the branch, the folder, and the open questions. Then ask me what you are missing.\n\nDo not fill `TEST-STRATEGY.md` or `IMPLEMENTATION-PLAN.md` until I answer. Do not edit any code.\n\n## No commands set up?\n\nPaste this instead:\n\n```\nCreate branch feature/pr-<TICKET>-<short-name> and\ndocs/prs/planning/<today's date>-PR-<TICKET>-<short-name>/. Copy the five\ntemplates from docs/prs/_TEMPLATE/. Read backlog/<TICKET>.md and write\nRESEARCH.md: the problem, what exists today (with file references), two\noptions with trade-offs, your recommendation and the risks. Then ask me\nwhat you're missing. Don't edit code.\n```", "variables": [], "notes": "Type the arguments after the command, for example `/start-pr <TICKET> <short-name>`.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/Epistemic-Me/ai-dlc-workshop", "path": ".cursor/commands/start-pr.md", "ref": "7f99e53acbde60f908fa2eb07531cdf96f63db75", "url": "https://github.com/Epistemic-Me/ai-dlc-workshop/blob/7f99e53acbde60f908fa2eb07531cdf96f63db75/.cursor/commands/start-pr.md", "key": "Epistemic-Me/ai-dlc-workshop/.cursor/commands/start-pr.md" } } }

start-pr

About

/start-pr

Steps

No commands set up?

Install start-pr 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

Use it

Manifest

Reviews