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.

Design Service - Prompt - OpenSmartRoute

Name: Design Service
Author: LazyWorkshopCreate

Prompt file imported from LazyWorkshopCreate/agent-based-workflow (.github/prompts/design-service.prompt.md). Copyright stays with the author.

Design or revise one backend service design document.

Requirements:

Read workspace instructions.
Read service delivery module.
Read the relevant design files under docs/design/, relevant plans under docs/plans/, and outstanding items when relevant.
For a focused revision to one existing service design file, keep the invoking agent as coordinator and delegate the drafting pass to the Design Delta Drafter custom agent when that asset is available.
Use Draft Technical Design instead if the target is platform, infrastructure, shared runtime, or a cross-service concern rather than one backend service.
Ground the design in verified evidence from docs/reference/ and project source code.
Keep the active document in English.
Preserve the current service-document section style already used in the repository.
If evidence is missing, add closure items instead of inventing behavior.

Expected output:

Update the existing service design file, or draft a new one using the repository template at docs/templates/SERVICE_DESIGN_TEMPLATE.md.
Call out the exact source files or evidence families that justify the boundary.

Design or revise one backend service design document. Requirements: - Read [workspace instructions](../copilot-instructions.md). - Read [service delivery module](../skills/design-workflow/modules/service-delivery.md). - Read the relevant design files under `docs/design/`, relevant plans under `docs/plans/`, and [outstanding items](../../docs/status/outstanding-items.md) when relevant. - For a focused revision to one existing service design file, keep the invoking agent as coordinator and delegate the drafting pass to the `Design Delta Drafter` custom agent when that asset is available. - Use [Draft Technical Design](./draft-technical-design.prompt.md) instead if the target is platform, infrastructure, shared runtime, or a cross-service concern rather than one backend service. - Ground the design in verified evidence from `docs/reference/` and project source code. - Keep the active document in English. - Preserve the current service-document section style already used in the repository. - If evidence is missing, add closure items instead of inventing behavior. Expected output: - Update the existing service design file, or draft a new one using the repository template at `docs/templates/SERVICE_DESIGN_TEMPLATE.md`. - Call out the exact source files or evidence families that justify the boundary.

Install Design Service 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": "Design or revise one backend service design document.\n\nRequirements:\n\n- Read [workspace instructions](../copilot-instructions.md).\n- Read [service delivery module](../skills/design-workflow/modules/service-delivery.md).\n- Read the relevant design files under `docs/design/`, relevant plans under `docs/plans/`, and [outstanding items](../../docs/status/outstanding-items.md) when relevant.\n- For a focused revision to one existing service design file, keep the invoking agent as coordinator and delegate the drafting pass to the `Design Delta Drafter` custom agent when that asset is available.\n- Use [Draft Technical Design](./draft-technical-design.prompt.md) instead if the target is platform, infrastructure, shared runtime, or a cross-service concern rather than one backend service.\n- Ground the design in verified evidence from `docs/reference/` and project source code.\n- Keep the active document in English.\n- Preserve the current service-document section style already used in the repository.\n- If evidence is missing, add closure items instead of inventing behavior.\n\nExpected output:\n\n- Update the existing service design file, or draft a new one using the repository template at `docs/templates/SERVICE_DESIGN_TEMPLATE.md`.\n- Call out the exact source files or evidence families that justify the boundary.", "variables": [], "notes": "Use when drafting or revising exactly one backend service design. Keywords: service design, backend design, service boundary. Arguments: Service and goal, e.g.: Inventory write closure, Alerts query design, Media initial service doc.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/LazyWorkshopCreate/agent-based-workflow", "path": ".github/prompts/design-service.prompt.md", "ref": "e8a68deb044a0f070bc9447042a99054b24c411c", "url": "https://github.com/LazyWorkshopCreate/agent-based-workflow/blob/e8a68deb044a0f070bc9447042a99054b24c411c/.github/prompts/design-service.prompt.md", "key": "LazyWorkshopCreate/agent-based-workflow/.github/prompts/design-service.prompt.md" } } }

Design Service

About

Use it

Install Design Service 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