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.

create-adr - Prompt - OpenSmartRoute

Name: create-adr
Author: jabrena

Prompt file imported from jabrena/dvbe26-workshop (.cursor/commands/create-adr.md). Copyright stays with the author.

create-adr

Record an important architectural decision, its context, alternatives, and consequences.

Usage

/create-adr <decision-source>

Accepted Inputs

Approved design exploration, issue, specification, or implementation plan
Existing architecture constraints and related ADRs

Owning Agent

@plinth-architect

Associated Skills

030-architecture-adr-general

Workflow

Confirm the decision scope with 030-architecture-adr-general.
Gather context, constraints, considered alternatives, and consequences.
Draft the ADR using the repository convention.
Check consistency with related issues, designs, specifications, and ADRs.
Present the ADR for approval before finalizing it.

Output

One repository-compliant ADR
Decision status, rationale, alternatives, and consequences
Links to relevant source artifacts

Safeguards

Do not create an ADR for a decision that has not been made.
Do not invent alternatives or constraints.
Do not modify unrelated ADRs.

# create-adr Record an important architectural decision, its context, alternatives, and consequences. ## Usage ```text /create-adr <decision-source> ``` ## Accepted Inputs - Approved design exploration, issue, specification, or implementation plan - Existing architecture constraints and related ADRs ## Owning Agent `@plinth-architect` ## Associated Skills - `030-architecture-adr-general` ## Workflow 1. Confirm the decision scope with `030-architecture-adr-general`. 2. Gather context, constraints, considered alternatives, and consequences. 3. Draft the ADR using the repository convention. 4. Check consistency with related issues, designs, specifications, and ADRs. 5. Present the ADR for approval before finalizing it. ## Output - One repository-compliant ADR - Decision status, rationale, alternatives, and consequences - Links to relevant source artifacts ## Safeguards - Do not create an ADR for a decision that has not been made. - Do not invent alternatives or constraints. - Do not modify unrelated ADRs.

Install create-adr 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": "# create-adr\n\nRecord an important architectural decision, its context, alternatives, and consequences.\n\n## Usage\n\n```text\n/create-adr <decision-source>\n```\n\n## Accepted Inputs\n\n- Approved design exploration, issue, specification, or implementation plan\n- Existing architecture constraints and related ADRs\n\n## Owning Agent\n\n`@plinth-architect`\n\n## Associated Skills\n\n- `030-architecture-adr-general`\n\n## Workflow\n\n1. Confirm the decision scope with `030-architecture-adr-general`.\n2. Gather context, constraints, considered alternatives, and consequences.\n3. Draft the ADR using the repository convention.\n4. Check consistency with related issues, designs, specifications, and ADRs.\n5. Present the ADR for approval before finalizing it.\n\n## Output\n\n- One repository-compliant ADR\n- Decision status, rationale, alternatives, and consequences\n- Links to relevant source artifacts\n\n## Safeguards\n\n- Do not create an ADR for a decision that has not been made.\n- Do not invent alternatives or constraints.\n- Do not modify unrelated ADRs.", "variables": [], "notes": "Create a repository ADR for an approved architectural decision. Tools: Read, Write, Edit. Arguments: [decision-source].", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/jabrena/dvbe26-workshop", "path": ".cursor/commands/create-adr.md", "ref": "6706ee8a69f6ea60e39437ff92c86ddd7045efc7", "url": "https://github.com/jabrena/dvbe26-workshop/blob/6706ee8a69f6ea60e39437ff92c86ddd7045efc7/.cursor/commands/create-adr.md", "key": "jabrena/dvbe26-workshop/.cursor/commands/create-adr.md" } }, "model_hints": [ "inherit" ] }

create-adr

About

create-adr

Usage

Accepted Inputs

Owning Agent

Associated Skills

Workflow

Output

Safeguards

Use it

Install create-adr 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