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.

sswa-apply - Prompt - OpenSmartRoute

Name: sswa-apply
Author: Kieransaunders

Prompt file imported from Kieransaunders/sswa (.windsurf/workflows/sswa-apply.md). Copyright stays with the author.

Implement the SSWA change: ${1:-the active change under openspec/changes/}.

Read single-feature-flow, test-driven-development, and openspec-conventions first.

Preflight

Run the single-feature-flow preflight (environment flag + CLAUDE.md symlink). Confirm you are on the change's sswa/<change-name> branch; if not, check it out — or, if propose created a worktree for this change (concurrent-agent case), cd into that worktree directory instead of checking out the branch in the current one.

GREEN — one test at a time

The failing tests already exist (written at propose time). Now make them pass:

Read proposal.md, the delta specs/, design.md (if present), and tasks.md.
Confirm the change's tests currently fail (RED). If they unexpectedly pass, stop and reconcile with the spec before writing code.
Work the tasks in order. For each: write the minimum implementation to turn the relevant failing test green — no speculative features, no unrelated refactoring.
After each test goes green, run the full suite to confirm nothing else broke. Then REFACTOR if useful (keep tests green, add no behavior).
Check off the task in tasks.md (- [x]). Commit in logical increments.

Done when

Every task is checked, every scenario's test passes, the full suite is green, no warnings.
Report status and the next step: /sswa:verify.

Never edit a test to make it pass — fix the implementation. If a test is genuinely wrong, fix the spec and the test together, and re-confirm RED→GREEN.

Install sswa-apply 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": "Implement the SSWA change: ${1:-the active change under openspec/changes/}.\n\nRead `single-feature-flow`, `test-driven-development`, and `openspec-conventions` first.\n\n## Preflight\nRun the single-feature-flow preflight (environment flag + CLAUDE.md symlink). Confirm you\nare on the change's `sswa/<change-name>` branch; if not, check it out — or, if propose\ncreated a worktree for this change (concurrent-agent case), `cd` into that worktree\ndirectory instead of checking out the branch in the current one.\n\n## GREEN — one test at a time\nThe failing tests already exist (written at propose time). Now make them pass:\n\n1. Read `proposal.md`, the delta `specs/`, `design.md` (if present), and `tasks.md`.\n2. Confirm the change's tests currently **fail** (RED). If they unexpectedly pass, stop and\n reconcile with the spec before writing code.\n3. Work the tasks in order. For each: write the **minimum** implementation to turn the\n relevant failing test green — no speculative features, no unrelated refactoring.\n4. After each test goes green, run the **full suite** to confirm nothing else broke. Then\n REFACTOR if useful (keep tests green, add no behavior).\n5. Check off the task in `tasks.md` (`- [x]`). Commit in logical increments.\n\n## Done when\n- Every task is checked, every scenario's test passes, the full suite is green, no warnings.\n- Report status and the next step: `/sswa:verify`.\n\nNever edit a test to make it pass — fix the implementation. If a test is genuinely wrong,\nfix the spec and the test together, and re-confirm RED→GREEN.", "variables": [], "notes": "Implement the active change to GREEN — turn each failing test green one at a time, checking off tasks. (mirrors /opsx:apply) Tools: Bash, Read, Write, Edit, Grep, Glob. Arguments: [change-name].", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/Kieransaunders/sswa", "path": ".windsurf/workflows/sswa-apply.md", "ref": "7b5f40c7c84cf1b6ae66161b3ccc08c9ec9f8e28", "url": "https://github.com/Kieransaunders/sswa/blob/7b5f40c7c84cf1b6ae66161b3ccc08c9ec9f8e28/.windsurf/workflows/sswa-apply.md", "key": "Kieransaunders/sswa/.windsurf/workflows/sswa-apply.md" } } }

sswa-apply

About

Preflight

GREEN — one test at a time

Done when

Use it

Install sswa-apply 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