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.

autodev - Prompt - OpenSmartRoute

Name: autodev
Author: hptbee

Prompt file imported from hptbee/b3_tuvi (.cursor/commands/autodev.md). Copyright stays with the author.

autodev

Action now: run autonomous development until PASS, FAIL, INCOMPLETE, or BLOCKED. Do not stop after the plan and wait for /implement. Do not stop after one task while other ready tasks remain — continue in this session (workflow Continue). Do not tell the user to run /autodev resume unless the session ended or the run is blocked.

This file is a thin product-repo pointer. It does not contain the procedure.

Locate B3

Resolve B3_HOME in this order. Stop at the first match that contains workflows/autonomous-development.md:

Environment variable B3_HOME
Product git root file .b3/home (one line, absolute path)
This repository itself, if it contains workflows/autonomous-development.md

If none match → BLOCKED. Do not invent a second procedure. Do not copy B3 skills into this product repository.

Workflow: {B3_HOME}/workflows/autonomous-development.md

Load B3 skills, rules, review-loop, and agents from B3_HOME. Write checkpoints and make Git commits in this product repository.

Argument	Behavior
Story, requirement, bug, refactor, or a path to one	Start or continue the lifecycle
Path to an existing plan	Validate it, then execute
`resume`	Reconcile `.b3/autodev/` with Git, then continue
`status`	Report the checkpoint. Do not implement

You are the orchestrator in this session. Dispatch reviewer and fixer subagents when this host can isolate them. If it cannot, record that limit in .b3/autodev/progress.md.

/plan, /implement, /debug, /review, /verify, and /review-loop stay single-purpose. This command composes them; it does not replace their files.

Install autodev 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": "# autodev\n\n**Action now:** run autonomous development until `PASS`, `FAIL`, `INCOMPLETE`, or `BLOCKED`. Do not stop after the plan and wait for `/implement`. Do not stop after one task while other ready tasks remain — continue in this session (workflow **Continue**). Do not tell the user to run `/autodev resume` unless the session ended or the run is blocked.\n\nThis file is a **thin product-repo pointer**. It does not contain the procedure.\n\n## Locate B3\n\nResolve `B3_HOME` in this order. Stop at the first match that contains `workflows/autonomous-development.md`:\n\n1. Environment variable `B3_HOME`\n2. Product git root file `.b3/home` (one line, absolute path)\n3. This repository itself, if it contains `workflows/autonomous-development.md`\n\nIf none match → `BLOCKED`. Do not invent a second procedure. Do not copy B3 skills into this product repository.\n\n**Workflow:** `{B3_HOME}/workflows/autonomous-development.md`\n\nLoad B3 skills, rules, review-loop, and agents from `B3_HOME`. Write checkpoints and make Git commits in this product repository.\n\n| Argument | Behavior |\n| --- | --- |\n| Story, requirement, bug, refactor, or a path to one | Start or continue the lifecycle |\n| Path to an existing plan | Validate it, then execute |\n| `resume` | Reconcile `.b3/autodev/` with Git, then continue |\n| `status` | Report the checkpoint. Do not implement |\n\nYou are the orchestrator in this session. Dispatch reviewer and fixer subagents when this host can isolate them. If it cannot, record that limit in `.b3/autodev/progress.md`.\n\n`/plan`, `/implement`, `/debug`, `/review`, `/verify`, and `/review-loop` stay single-purpose. This command composes them; it does not replace their files.", "variables": [], "notes": "Run the full development lifecycle from a requirement or plan until completion or a blocker. Use for autonomous implementation, resume, or status. Do not use for plan-only, a single implement, debug, one review, or review-loop-only.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/hptbee/b3_tuvi", "path": ".cursor/commands/autodev.md", "ref": "f0dec74973ef9d07129e19330356f8e6d2040227", "url": "https://github.com/hptbee/b3_tuvi/blob/f0dec74973ef9d07129e19330356f8e6d2040227/.cursor/commands/autodev.md", "key": "hptbee/b3_tuvi/.cursor/commands/autodev.md" } } }

autodev

About

autodev

Locate B3

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