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.

plan - Prompt - OpenSmartRoute

Name: plan
Author: dshills

Prompt file imported from dshills/alas (.claude/commands/plan.md). Copyright stays with the author.

We are going to build a file called PLANNING.md which lives in the project's root directory. The objective is to have a document that will give you important context about the project, along with instructions on how to build and test. Start by building a document with the following categories, that we will initially mark as TBD. Then we will discuss each of these points together and fill in the document as we go. - Project Overview - Architecture - Core components (API, Data, Service layers, configuration, etc) - Data Model, if the project has a database component - API endpoints, if the project exposes endpoints to be consumed - Technology stack (Language, frameworks, etc) - Project structure - Testing strategy, if the project uses unit or integration testing - Development commands (to build,Data Model, if the project has a database component - API endpoints, if the project exposes endpoints to be consumed - Technology stack (Language, frameworks, etc) - Project structure - Testing strategy, if the project uses unit or integration tests. - Development commands (for building, running, etc). - Environment setup (how the development environment is currently set up for the project) - Development guidelines (rules to follow when modifying the project) - Security considerations (things to keep in mind that are security-focused when modifying the project) - Future considerations (things that we may not be adding right away but would be candidates for future versions)

We will BUILD a file called TASK.md which lives in the project's root directory. The objective is to give you important context about what tasks have been accomplished, and what work is left to do. READ the PLANNING.md file, then create a list of tasks that you think should be accomplished. Categorize them appropriately (e.g. Setup, Core Functionality, etc). The last category will be "Completed Work" where we will have a log of work that has been completed, although initially this will be empty

Install plan 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": "We are going to build a file called PLANNING.md which lives in the project's root directory. The objective is to have a document that will give you important context about the project, along with instructions on how to build and test. Start by building a document with the following categories, that we will initially mark as TBD. Then we will discuss each of these points together and fill in the document as we go.\n - Project Overview\n - Architecture\n - Core components (API, Data, Service layers, configuration, etc)\n - Data Model, if the project has a database component\n - API endpoints, if the project exposes endpoints to be consumed\n - Technology stack (Language, frameworks, etc)\n - Project structure\n - Testing strategy, if the project uses unit or integration testing\n - Development commands (to build,Data Model, if the project has a database component\n - API endpoints, if the project exposes endpoints to be consumed\n - Technology stack (Language, frameworks, etc)\n - Project structure\n - Testing strategy, if the project uses unit or integration tests.\n - Development commands (for building, running, etc).\n - Environment setup (how the development environment is currently set up for the project)\n - Development guidelines (rules to follow when modifying the project)\n - Security considerations (things to keep in mind that are security-focused when modifying the project)\n - Future considerations (things that we may not be adding right away but would be candidates for future versions)\n\nWe will BUILD a file called TASK.md which lives in the project's root directory. The objective is to give you important context about what tasks have been accomplished, and what work is left to do. READ the PLANNING.md file, then create a list of tasks that you think should be accomplished. Categorize them appropriately (e.g. Setup, Core Functionality, etc). The last category will be \"Completed Work\" where we will have a log of work that has been completed, although initially this will be empty", "variables": [], "notes": "We are going to build a file called PLANNING.md which lives in the project's root directory. The objective is to have a document that will give you important context about the project, along with instructions on how to build and test. Start by building a document with the following categories, that we will initially mark as TBD. Then we will discuss each of these points together and fill in the document as we go. - Project Overview - Architecture - Core components (API, Data, Service layers, configuration, etc) - Data Model, if the project has a database component - API endpoints, if the project exposes endpoints to be consumed - Technology stack (Language, frameworks, etc) - Project structure - Testing strategy, if the project uses unit or integration testing - Development commands (to build,Data Model, if the project has a database component - API endpoints, if the project exposes endpoints to be consumed - Technology stack (Language, frameworks, etc) - Project structure - Testing strategy, if the project u", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/dshills/alas", "path": ".claude/commands/plan.md", "ref": "e81eedeca15bfeff889f65e321181f1dbce0aefb", "url": "https://github.com/dshills/alas/blob/e81eedeca15bfeff889f65e321181f1dbce0aefb/.claude/commands/plan.md", "key": "dshills/alas/.claude/commands/plan.md" } } }

plan

About

Use it

Install plan 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