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.

gsd-doctor - Prompt - OpenSmartRoute

Name: gsd-doctor
Author: BrianKYildirim

Prompt file imported from BrianKYildirim/strivoai (.codex/prompts/gsd-doctor.md). Fill in {{arguments}} before use. Copyright stays with the author.

Objective

Diagnose whether this project is set up to run GSD prompts in Codex while remaining compatible with Claude workflows on the same .planning/ milestone/phases.

Compatibility

Use .codex/skills/get-shit-done-codex semantics.
Do not modify files (read-only diagnostics).
Prefer PowerShell commands; no jq.

Checks to run

Run these checks and then present a compact table: check | status | details | fix.

Versions

Codex fork installed version (first match wins):
- .codex/gsd/VERSION
- ~/.codex/gsd/VERSION
Claude engine installed version (first match wins):
- .claude/get-shit-done/VERSION
- ~/.claude/get-shit-done/VERSION

Engine presence (required for Codex prompts)

.claude/get-shit-done/bin/gsd-tools.cjs OR .claude/get-shit-done/bin/gsd-tools.js
If only gsd-tools.test.js exists, treat engine as missing/incomplete.

Codex agent roles (recommended for model routing)

Role registrations exist (first match wins):
- .codex/config.toml contains [agents.gsd-planner]
- ~/.codex/config.toml contains [agents.gsd-planner]
Role config layers exist (first match wins):
- .codex/agents/gsd-planner.toml
- ~/.codex/agents/gsd-planner.toml

Project state

.planning/ exists (if missing, user hasn’t initialized a project).

Update check

Best-effort only; do not fail if offline.

Update availability (best-effort)

Latest Codex fork version (do not fail if offline):
- npm view gsd-codex-cli version
If installed Codex fork version is known and differs from latest, surface:
- Update available: {installed} -> {latest}
- Next: /prompts:gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest.

Recommended fixes (use the minimum)

If engine missing: npx gsd-codex-cli@latest --path . (or --global)
If only Claude engine exists and Codex prompts are desired in-project: npx gsd-codex-cli@latest --path .
If .planning/ missing: run /prompts:gsd-new-project (Codex) / /gsd:new-project (Claude)

Completion output

Print the table and a single “Next recommended command”:
- If engine missing: npx gsd-codex-cli@latest --path .
- Else if .planning/ missing: gsd-new-project / /gsd:new-project
- Else: gsd-progress / /gsd:progress

Install gsd-doctor 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.

{{arguments}} ## Objective Diagnose whether this project is set up to run GSD prompts in Codex while remaining compatible with Claude workflows on the same `.planning/` milestone/phases. ## Compatibility - Use .codex/skills/get-shit-done-codex semantics. - Do not modify files (read-only diagnostics). - Prefer PowerShell commands; no jq. ## Checks to run Run these checks and then present a compact table: `check | status | details | fix`. ### Versions - Codex fork installed version (first match wins): - `.codex/gsd/VERSION` - `~/.codex/gsd/VERSION` - Claude engine installed version (first match wins): - `.claude/get-shit-done/VERSION` - `~/.claude/get-shit-done/VERSION` ### Engine presence (required for Codex prompts) - `.claude/get-shit-done/bin/gsd-tools.cjs` OR `.claude/get-shit-done/bin/gsd-tools.js` - If only `gsd-tools.test.js` exists, treat engine as missing/incomplete. ### Codex agent roles (recommended for model routing) - Role registrations exist (first match wins): - `.codex/config.toml` contains `[agents.gsd-planner]` - `~/.codex/config.toml` contains `[agents.gsd-planner]` - Role config layers exist (first match wins): - `.codex/agents/gsd-planner.toml` - `~/.codex/agents/gsd-planner.toml` ### Project state - `.planning/` exists (if missing, user hasn’t initialized a project). ## Update check - Best-effort only; do not fail if offline. ### Update availability (best-effort) - Latest Codex fork version (do not fail if offline): - `npm view gsd-codex-cli version` - If installed Codex fork version is known and differs from latest, surface: - `Update available: {installed} -> {latest}` - Next: `/prompts:gsd-update` (Codex) / `/gsd:update` (Claude) or re-run `npx gsd-codex-cli@latest`. ## Recommended fixes (use the minimum) - If engine missing: `npx gsd-codex-cli@latest --path .` (or `--global`) - If only Claude engine exists and Codex prompts are desired in-project: `npx gsd-codex-cli@latest --path .` - If `.planning/` missing: run `/prompts:gsd-new-project` (Codex) / `/gsd:new-project` (Claude) ## Completion output - Print the table and a single “Next recommended command”: - If engine missing: `npx gsd-codex-cli@latest --path .` - Else if `.planning/` missing: `gsd-new-project` / `/gsd:new-project` - Else: `gsd-progress` / `/gsd:progress`

{ "prompt": "{{arguments}}\n\n## Objective\nDiagnose whether this project is set up to run GSD prompts in Codex while remaining compatible with Claude workflows on the same `.planning/` milestone/phases.\n\n## Compatibility\n- Use .codex/skills/get-shit-done-codex semantics.\n- Do not modify files (read-only diagnostics).\n- Prefer PowerShell commands; no jq.\n\n## Checks to run\nRun these checks and then present a compact table: `check | status | details | fix`.\n\n### Versions\n- Codex fork installed version (first match wins):\n - `.codex/gsd/VERSION`\n - `~/.codex/gsd/VERSION`\n- Claude engine installed version (first match wins):\n - `.claude/get-shit-done/VERSION`\n - `~/.claude/get-shit-done/VERSION`\n\n### Engine presence (required for Codex prompts)\n- `.claude/get-shit-done/bin/gsd-tools.cjs` OR `.claude/get-shit-done/bin/gsd-tools.js`\n- If only `gsd-tools.test.js` exists, treat engine as missing/incomplete.\n\n### Codex agent roles (recommended for model routing)\n- Role registrations exist (first match wins):\n - `.codex/config.toml` contains `[agents.gsd-planner]`\n - `~/.codex/config.toml` contains `[agents.gsd-planner]`\n- Role config layers exist (first match wins):\n - `.codex/agents/gsd-planner.toml`\n - `~/.codex/agents/gsd-planner.toml`\n\n### Project state\n- `.planning/` exists (if missing, user hasn’t initialized a project).\n\n## Update check\n- Best-effort only; do not fail if offline.\n### Update availability (best-effort)\n- Latest Codex fork version (do not fail if offline):\n - `npm view gsd-codex-cli version`\n- If installed Codex fork version is known and differs from latest, surface:\n - `Update available: {installed} -> {latest}`\n - Next: `/prompts:gsd-update` (Codex) / `/gsd:update` (Claude) or re-run `npx gsd-codex-cli@latest`.\n\n## Recommended fixes (use the minimum)\n- If engine missing: `npx gsd-codex-cli@latest --path .` (or `--global`)\n- If only Claude engine exists and Codex prompts are desired in-project: `npx gsd-codex-cli@latest --path .`\n- If `.planning/` missing: run `/prompts:gsd-new-project` (Codex) / `/gsd:new-project` (Claude)\n\n## Completion output\n- Print the table and a single “Next recommended command”:\n - If engine missing: `npx gsd-codex-cli@latest --path .`\n - Else if `.planning/` missing: `gsd-new-project` / `/gsd:new-project`\n - Else: `gsd-progress` / `/gsd:progress`", "variables": [ "arguments" ], "notes": "Diagnose Codex+Claude GSD installation (engine, prompts, versions) Arguments: [none].", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/BrianKYildirim/strivoai", "path": ".codex/prompts/gsd-doctor.md", "ref": "c0fe16a5b927fe492c4e7b150904c734e6c47c17", "url": "https://github.com/BrianKYildirim/strivoai/blob/c0fe16a5b927fe492c4e7b150904c734e6c47c17/.codex/prompts/gsd-doctor.md", "key": "BrianKYildirim/strivoai/.codex/prompts/gsd-doctor.md" } } }

gsd-doctor

About

Objective

Compatibility

Checks to run

Versions

Engine presence (required for Codex prompts)

Codex agent roles (recommended for model routing)

Project state

Update check

Update availability (best-effort)

Recommended fixes (use the minimum)

Completion output

Install gsd-doctor 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