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.

orch-build-mvp - Prompt - OpenSmartRoute

Name: orch-build-mvp
Author: knownassurajit

Prompt file imported from knownassurajit/void (.cursor/commands/orch-build-mvp.md). Fill in {{arguments}} before use. Copyright stays with the author.

/orch-build-mvp

Manually launch the orch-build-mvp orchestrator: turn an SDD/PRD/system-design document into a running vertical slice.

Usage

/orch-build-mvp <path to design/spec doc>

Examples:

/orch-build-mvp civicpulse/docs/SDD-v0.6.md

What It Does

Invoke the orch-build-mvp skill with {{arguments}} as the doc path. The skill (via the shared orch-pipeline engine, full pipeline incl. Scaffold) will:

Read the spec; extract scope, locked decisions, and a feature list ordered as thin vertical slices (one end-to-end path first). → GATE 1 (approve slice plan).
Scaffold the first end-to-end slice.
Reuse the GAN harness: translate the SDD into gan-harness/spec.md + eval-rubric.md, then drive /gan-build "<brief>" --skip-planner (generator → evaluator loop) until the score passes or plateaus.
code-reviewer (+ security-reviewer on any security-trigger slice), then commit the scaffold and each slice as separate feat: commits. → GATE 2.

If {{arguments}} is empty, ask the user for the path to the design/spec doc.

# /orch-build-mvp Manually launch the **orch-build-mvp** orchestrator: turn an SDD/PRD/system-design document into a running vertical slice. ## Usage ``` /orch-build-mvp <path to design/spec doc> ``` Examples: ``` /orch-build-mvp civicpulse/docs/SDD-v0.6.md ``` ## What It Does Invoke the `orch-build-mvp` skill with `{{arguments}}` as the doc path. The skill (via the shared `orch-pipeline` engine, full pipeline incl. Scaffold) will: 1. Read the spec; extract scope, locked decisions, and a feature list ordered as **thin vertical slices** (one end-to-end path first). → **GATE 1** (approve slice plan). 2. Scaffold the first end-to-end slice. 3. Reuse the GAN harness: translate the SDD into `gan-harness/spec.md` + `eval-rubric.md`, then drive `/gan-build "<brief>" --skip-planner` (generator → evaluator loop) until the score passes or plateaus. 4. `code-reviewer` (+ `security-reviewer` on any security-trigger slice), then commit the scaffold and each slice as separate `feat:` commits. → **GATE 2**. If `{{arguments}}` is empty, ask the user for the path to the design/spec doc.

Install orch-build-mvp 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": "# /orch-build-mvp\n\nManually launch the **orch-build-mvp** orchestrator: turn an SDD/PRD/system-design\ndocument into a running vertical slice.\n\n## Usage\n\n```\n/orch-build-mvp <path to design/spec doc>\n```\n\nExamples:\n\n```\n/orch-build-mvp civicpulse/docs/SDD-v0.6.md\n```\n\n## What It Does\n\nInvoke the `orch-build-mvp` skill with `{{arguments}}` as the doc path. The skill\n(via the shared `orch-pipeline` engine, full pipeline incl. Scaffold) will:\n\n1. Read the spec; extract scope, locked decisions, and a feature list ordered as\n**thin vertical slices** (one end-to-end path first). → **GATE 1** (approve slice plan).\n2. Scaffold the first end-to-end slice.\n3. Reuse the GAN harness: translate the SDD into `gan-harness/spec.md` +\n `eval-rubric.md`, then drive `/gan-build \"<brief>\" --skip-planner`\n (generator → evaluator loop) until the score passes or plateaus.\n4. `code-reviewer` (+ `security-reviewer` on any security-trigger slice), then\n commit the scaffold and each slice as separate `feat:` commits. → **GATE 2**.\n\nIf `{{arguments}}` is empty, ask the user for the path to the design/spec doc.", "variables": [ "arguments" ], "notes": "Orchestrate bootstrapping a working MVP from a design/spec doc — ingest, slice, scaffold, TDD, review, gated commit (reuses the GAN harness). Wrapper for the orch-build-mvp skill.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/knownassurajit/void", "path": ".cursor/commands/orch-build-mvp.md", "ref": "a71316519f3ec629704764831bf1ed60f4ca158b", "url": "https://github.com/knownassurajit/void/blob/a71316519f3ec629704764831bf1ed60f4ca158b/.cursor/commands/orch-build-mvp.md", "key": "knownassurajit/void/.cursor/commands/orch-build-mvp.md" } } }

orch-build-mvp

About

/orch-build-mvp

Usage

What It Does

Use it

Install orch-build-mvp 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