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.

build - Prompt - OpenSmartRoute

Name: build
Author: edwardlthompson

Prompt file imported from edwardlthompson/agent-project-bootstrap (.cursor/commands/build.md). Copyright stays with the author.

Autonomous sprint build

Execute BUILD_PLAN without asking. Venue: This Computer = [AGENT][LOCAL] only. Stop only on 3-strike, exit 2, or board complete.

/build and /cleanup run together after a completed sprint/feature block: never end a successful wrap-up without archiving finished ✅ rows.

Loop

python3 scripts/agent-run.py build-sprint-status --json --lane auto

`next_row.action`	Do
`automate_human` / `automate_adb`	`attempt-build-plan-row` → ✅ or backlog
`execute`	Implement → gate → ✅
`parallel_dispatch`	`@scope.md` then `set-parallel-sprint-done`
AUTO	Run scripts → ✅
Every AGENT step:

python3 scripts/agent-run.py watch-agent-gates --once --autofix --scope auto

Gate lock: never skip watch-agent-gates; do not start the next row until gates exit 0. Never skip 1c to chain a second feature.

Push cadence: after each ✅ AGENT row, nudge the human to commit (if dirty) and /push when a remote exists. Never silent git push. Prefer /split-to-prs over one mega-diff.

Do not re-run full validate mid-slice if watch passed.

Wrap-up (sprint complete)

When the active sprint/feature block is all ✅:

smoke-sprint --require --sprint "<title>" — fail → do not cleanup; leave the board and fix.
Scoped gate + hygiene (not full multi unless user said --full):

python3 scripts/agent-run.py watch-agent-gates --once --scope auto
python3 scripts/agent-run.py check-repo-hygiene

Mandatory cleanup (never skip): read and execute @.cursor/commands/cleanup.md fully. Never end /build with this block’s finished ✅ AGENT/AUTO rows still on the active board.
Finish — show slim BUILD_PLAN: print the Now: line, the remaining-tally, and confirm Local/Cloud lanes have no leftover ✅ AGENT/AUTO rows from this sprint (legend-only ✅ in the status key is fine).
Only then chain the next sprint if next_row exists.

If build stops early (3-strike / exit 2), do not archive open 🔲/❌ rows.

Open PRs: sync-open-prs-build-plan -- --check once; --apply only if stale.

Begin now.

Install build 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.

# Autonomous sprint build Execute BUILD_PLAN without asking. Venue: This Computer = `[AGENT][LOCAL]` only. Stop only on 3-strike, exit 2, or board complete. `/build` and `/cleanup` run **together** after a completed sprint/feature block: never end a successful wrap-up without archiving finished ✅ rows. ## Loop ```bash python3 scripts/agent-run.py build-sprint-status --json --lane auto ``` | `next_row.action` | Do | |-------------------|-----| | `automate_human` / `automate_adb` | `attempt-build-plan-row` → ✅ or backlog | | `execute` | Implement → gate → ✅ | | `parallel_dispatch` | `@scope.md` then `set-parallel-sprint-done` | | AUTO | Run scripts → ✅ | Every AGENT step: ```bash python3 scripts/agent-run.py watch-agent-gates --once --autofix --scope auto ``` **Gate lock:** never skip watch-agent-gates; do not start the next row until gates exit 0. Never skip 1c to chain a second feature. **Push cadence:** after each ✅ AGENT row, nudge the human to commit (if dirty) and `/push` when a remote exists. Never silent `git push`. Prefer `/split-to-prs` over one mega-diff. Do not re-run full validate mid-slice if watch passed. ## Wrap-up (sprint complete) When the active sprint/feature block is all ✅: 1. `smoke-sprint --require --sprint "<title>"` — **fail → do not cleanup**; leave the board and fix. 2. Scoped gate + hygiene (not full multi unless user said `--full`): ```bash python3 scripts/agent-run.py watch-agent-gates --once --scope auto python3 scripts/agent-run.py check-repo-hygiene ``` 3. **Mandatory cleanup (never skip):** read and execute @.cursor/commands/cleanup.md fully. Never end `/build` with this block’s finished ✅ AGENT/AUTO rows still on the active board. 4. **Finish — show slim BUILD_PLAN:** print the **Now:** line, the remaining-tally, and confirm Local/Cloud lanes have no leftover ✅ AGENT/AUTO rows from this sprint (legend-only ✅ in the status key is fine). 5. Only then chain the next sprint if `next_row` exists. If build stops early (3-strike / exit 2), do **not** archive open 🔲/❌ rows. Open PRs: `sync-open-prs-build-plan -- --check` once; `--apply` only if stale. Begin now.

{ "prompt": "# Autonomous sprint build\n\nExecute BUILD_PLAN without asking. Venue: This Computer = `[AGENT][LOCAL]` only. Stop only on 3-strike, exit 2, or board complete.\n\n`/build` and `/cleanup` run **together** after a completed sprint/feature block: never end a successful wrap-up without archiving finished ✅ rows.\n\n## Loop\n\n```bash\npython3 scripts/agent-run.py build-sprint-status --json --lane auto\n\n```\n\n| `next_row.action` | Do |\n|-------------------|-----|\n| `automate_human` / `automate_adb` | `attempt-build-plan-row` → ✅ or backlog |\n| `execute` | Implement → gate → ✅ |\n| `parallel_dispatch` | `@scope.md` then `set-parallel-sprint-done` |\n| AUTO | Run scripts → ✅ |\nEvery AGENT step:\n\n```bash\npython3 scripts/agent-run.py watch-agent-gates --once --autofix --scope auto\n\n```\n\n**Gate lock:** never skip watch-agent-gates; do not start the next row until gates exit 0. Never skip 1c to chain a second feature.\n\n**Push cadence:** after each ✅ AGENT row, nudge the human to commit (if dirty) and `/push` when a remote exists. Never silent `git push`. Prefer `/split-to-prs` over one mega-diff.\n\nDo not re-run full validate mid-slice if watch passed.\n\n## Wrap-up (sprint complete)\n\nWhen the active sprint/feature block is all ✅:\n\n1. `smoke-sprint --require --sprint \"<title>\"` — **fail → do not cleanup**; leave the board and fix.\n2. Scoped gate + hygiene (not full multi unless user said `--full`):\n\n```bash\npython3 scripts/agent-run.py watch-agent-gates --once --scope auto\npython3 scripts/agent-run.py check-repo-hygiene\n\n```\n\n3. **Mandatory cleanup (never skip):** read and execute @.cursor/commands/cleanup.md fully. Never end `/build` with this block’s finished ✅ AGENT/AUTO rows still on the active board.\n4. **Finish — show slim BUILD_PLAN:** print the **Now:** line, the remaining-tally, and confirm Local/Cloud lanes have no leftover ✅ AGENT/AUTO rows from this sprint (legend-only ✅ in the status key is fine).\n5. Only then chain the next sprint if `next_row` exists.\n\nIf build stops early (3-strike / exit 2), do **not** archive open 🔲/❌ rows.\n\nOpen PRs: `sync-open-prs-build-plan -- --check` once; `--apply` only if stale.\n\nBegin now.", "variables": [], "notes": "Execute BUILD_PLAN without asking. Venue: This Computer = `[AGENT][LOCAL]` only. Stop only on 3-strike, exit 2, or board complete.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/edwardlthompson/agent-project-bootstrap", "path": ".cursor/commands/build.md", "ref": "1f84eb0c021d91b36c9273e676c59cae30307726", "url": "https://github.com/edwardlthompson/agent-project-bootstrap/blob/1f84eb0c021d91b36c9273e676c59cae30307726/.cursor/commands/build.md", "key": "edwardlthompson/agent-project-bootstrap/.cursor/commands/build.md" } } }

build

About

Autonomous sprint build

Loop

Wrap-up (sprint complete)

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