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.

next-roadmap-item - Prompt

Name: next-roadmap-item
Author: Bassov

Prompt file imported from Bassov/photobooks (.cursor/commands/next-roadmap-item.md). Copyright stays with the author.

Next roadmap item (unattended)

Run ONE roadmap item end to end in this session. This message is the explicit request for planning, apply, manual check, archive, PR and CI — do not stop between stages. Mandates live in openspec/config.yaml (rules + operations), .cursor/rules/git-finish.mdc, .cursor/agents and skill roadmap; follow them, do not restate them.

Preflight: git status clean (else stop), then git fetch origin && git switch main && git pull --ff-only.
Collect slugs with an open PR or remote branch (gh pr list --state open, git branch -r; branch feat/<slug> or fix/<slug>), then pnpm -s roadmap next --skip <slugs>. Its output (slug, tag, milestone goal, title, file, full scope) is the item; do not read docs/roadmap.md. It skips [contingency] items; take one only when its gate has failed (pnpm -s roadmap show <slug>). State item, tag and skips. git switch -c feat/<slug> (fix/ for bug items).
Plan with the OpenSpec CLI, not /opsx-propose (its planning boundary would end this run): openspec new change <slug>; for each ready artifact openspec instructions <id> --change <slug> --json → write it → openspec status --change <slug> --json. Launch the reviewer subagents where rules.proposal / rules.design require and loop to pass. Over budget: grow the roadmap with pnpm roadmap add <new-slug> --after <slug> ..., not the PR.
/opsx-apply through the Verification checklist, including openspec-implementation-reviewer pass and the Manual check.
/opsx-archive : answer "Sync now"; confirm only when every task is checked. Then close the item on this branch: pnpm roadmap done <slug> (--note "..." when the shipped scope deviates; required for a [contingency]). If it reports a milestone review cut, commit the archive move and stop after the PR is green.
pnpm roadmap check, then commit, PR and wait for green per git-finish.mdc.

Stop and ask only for: dirty tree, a milestone review cut, an item whose intent contradicts a spec or open issue, the git-finish CI stop conditions. Security-tagged items continue; run the Security Review sub-agent before archive. Until gate-ratchet/gate-ratchet-ci are merged, a gate-config edit MUST be strictly stricter and listed in the touch-set with a reason; otherwise stop. Until dependency-policy is merged, a new or changed dependency needs pnpm audit:ci evidence and a Security Review pass before archive. Otherwise record assumptions in the artifacts and continue. Final reply in Russian: item, PR URL, check status, reviewer verdicts, skipped survivors, assumptions.

Install next-roadmap-item 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.

# Next roadmap item (unattended) Run ONE roadmap item end to end in this session. This message is the explicit request for planning, apply, manual check, archive, PR and CI — do not stop between stages. Mandates live in openspec/config.yaml (rules + operations), .cursor/rules/git-finish.mdc, .cursor/agents and skill `roadmap`; follow them, do not restate them. 1. Preflight: `git status` clean (else stop), then `git fetch origin && git switch main && git pull --ff-only`. 2. Collect slugs with an open PR or remote branch (`gh pr list --state open`, `git branch -r`; branch `feat/<slug>` or `fix/<slug>`), then `pnpm -s roadmap next --skip <slugs>`. Its output (slug, tag, milestone goal, title, file, full scope) is the item; do not read docs/roadmap.md. It skips [contingency] items; take one only when its gate has failed (`pnpm -s roadmap show <slug>`). State item, tag and skips. `git switch -c feat/<slug>` (fix/ for bug items). 3. Plan with the OpenSpec CLI, not /opsx-propose (its planning boundary would end this run): `openspec new change <slug>`; for each ready artifact `openspec instructions <id> --change <slug> --json` → write it → `openspec status --change <slug> --json`. Launch the reviewer subagents where rules.proposal / rules.design require and loop to pass. Over budget: grow the roadmap with `pnpm roadmap add <new-slug> --after <slug> ...`, not the PR. 4. /opsx-apply <slug> through the Verification checklist, including openspec-implementation-reviewer pass and the Manual check. 5. /opsx-archive <slug>: answer "Sync now"; confirm only when every task is checked. Then close the item on this branch: `pnpm roadmap done <slug>` (`--note "..."` when the shipped scope deviates; required for a [contingency]). If it reports a milestone review cut, commit the archive move and stop after the PR is green. 6. `pnpm roadmap check`, then commit, PR and wait for green per git-finish.mdc. Stop and ask only for: dirty tree, a milestone review cut, an item whose intent contradicts a spec or open issue, the git-finish CI stop conditions. Security-tagged items continue; run the Security Review sub-agent before archive. Until `gate-ratchet`/`gate-ratchet-ci` are merged, a gate-config edit MUST be strictly stricter and listed in the touch-set with a reason; otherwise stop. Until `dependency-policy` is merged, a new or changed dependency needs `pnpm audit:ci` evidence and a Security Review pass before archive. Otherwise record assumptions in the artifacts and continue. Final reply in Russian: item, PR URL, check status, reviewer verdicts, skipped survivors, assumptions.

{ "prompt": "# Next roadmap item (unattended)\n\nRun ONE roadmap item end to end in this session. This message is the\nexplicit request for planning, apply, manual check, archive, PR and CI — do not\nstop between stages. Mandates live in openspec/config.yaml (rules + operations),\n.cursor/rules/git-finish.mdc, .cursor/agents and skill `roadmap`; follow them,\ndo not restate them.\n\n1. Preflight: `git status` clean (else stop), then\n `git fetch origin && git switch main && git pull --ff-only`.\n2. Collect slugs with an open PR or remote branch (`gh pr list --state open`,\n `git branch -r`; branch `feat/<slug>` or `fix/<slug>`), then\n `pnpm -s roadmap next --skip <slugs>`. Its output (slug, tag, milestone goal,\n title, file, full scope) is the item; do not read docs/roadmap.md. It skips\n [contingency] items; take one only when its gate has failed\n (`pnpm -s roadmap show <slug>`). State item, tag and skips.\n `git switch -c feat/<slug>` (fix/ for bug items).\n3. Plan with the OpenSpec CLI, not /opsx-propose (its planning boundary would end\n this run): `openspec new change <slug>`; for each ready artifact\n `openspec instructions <id> --change <slug> --json` → write it →\n `openspec status --change <slug> --json`. Launch the reviewer subagents where\n rules.proposal / rules.design require and loop to pass. Over budget: grow the\n roadmap with `pnpm roadmap add <new-slug> --after <slug> ...`, not the PR.\n4. /opsx-apply <slug> through the Verification checklist, including\n openspec-implementation-reviewer pass and the Manual check.\n5. /opsx-archive <slug>: answer \"Sync now\"; confirm only when every task is\n checked. Then close the item on this branch: `pnpm roadmap done <slug>`\n (`--note \"...\"` when the shipped scope deviates; required for a\n [contingency]). If it reports a milestone review cut, commit the archive\n move and stop after the PR is green.\n6. `pnpm roadmap check`, then commit, PR and wait for green per git-finish.mdc.\n\nStop and ask only for: dirty tree, a milestone review cut, an item whose intent\ncontradicts a spec or open issue, the git-finish CI stop conditions. Security-tagged\nitems continue; run the Security Review sub-agent before archive. Until\n`gate-ratchet`/`gate-ratchet-ci` are merged, a gate-config edit MUST be strictly\nstricter and listed in the touch-set with a reason; otherwise stop. Until\n`dependency-policy` is merged, a new or changed dependency needs `pnpm audit:ci`\nevidence and a Security Review pass before archive. Otherwise record assumptions\nin the artifacts and continue.\nFinal reply in Russian: item, PR URL, check status, reviewer verdicts, skipped\nsurvivors, assumptions.", "variables": [], "notes": "Run ONE roadmap item end to end in this session. This message is the explicit request for planning, apply, manual check, archive, PR and CI — do not stop between stages. Mandates live in openspec/config.yaml (rules + operations), .cursor/rules/git-finish.mdc, .cursor/agents and skill `roadmap`; follow them, do not restate them.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/Bassov/photobooks", "path": ".cursor/commands/next-roadmap-item.md", "ref": "0b9ada12eddc7112ddc21e3e356473dd74807444", "url": "https://github.com/Bassov/photobooks/blob/0b9ada12eddc7112ddc21e3e356473dd74807444/.cursor/commands/next-roadmap-item.md", "key": "Bassov/photobooks/.cursor/commands/next-roadmap-item.md" } } }

next-roadmap-item

About

Next roadmap item (unattended)

Install next-roadmap-item 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