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:add-backlog - Prompt - OpenSmartRoute

Name: gsd:add-backlog
Author: salmanwnl44

Prompt file imported from salmanwnl44/Yavin-v1.2.0 (.claude/commands/gsd/add-backlog.md). Fill in {{arguments}}, {{NEXT}}, {{SLUG}}, {{ARGUMENTS}} before use. Copyright stays with the author.

Read ROADMAP.md to find existing backlog entries:
```
cat .planning/ROADMAP.md
```

Find next backlog number:

NEXT=$(node "D:/Projects/Yavin-v1.2.0/Yavin-v1.2.0/Yavin-v1.1.0/.claude/get-shit-done/bin/gsd-tools.cjs" phase next-decimal 999 --raw)

If no 999.x phases exist, start at 999.1.

Create the phase directory:

SLUG=$(node "D:/Projects/Yavin-v1.2.0/Yavin-v1.2.0/Yavin-v1.1.0/.claude/get-shit-done/bin/gsd-tools.cjs" generate-slug "{{arguments}}")
mkdir -p ".planning/phases/{{NEXT}}-{{SLUG}}"
touch ".planning/phases/{{NEXT}}-{{SLUG}}/.gitkeep"

Add to ROADMAP.md under a ## Backlog section. If the section doesn't exist, create it at the end:

## Backlog

### Phase {NEXT}: {description} (BACKLOG)

**Goal:** [Captured for future planning]
**Requirements:** TBD
**Plans:** 0 plans

Plans:
- [ ] TBD (promote with /gsd:review-backlog when ready)

Commit:

node "D:/Projects/Yavin-v1.2.0/Yavin-v1.2.0/Yavin-v1.1.0/.claude/get-shit-done/bin/gsd-tools.cjs" commit "docs: add backlog item {{NEXT}} — {{ARGUMENTS}}" --files .planning/ROADMAP.md ".planning/phases/{{NEXT}}-{{SLUG}}/.gitkeep"

Report:

## 📋 Backlog Item Added

Phase {NEXT}: {description}
Directory: .planning/phases/{NEXT}-{slug}/

This item lives in the backlog parking lot.
Use /gsd:discuss-phase {NEXT} to explore it further.
Use /gsd:review-backlog to promote items to active milestone.

Install gsd:add-backlog 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.

<objective> Add a backlog item to the roadmap using 999.x numbering. Backlog items are unsequenced ideas that aren't ready for active planning — they live outside the normal phase sequence and accumulate context over time. </objective> <process> 1. **Read ROADMAP.md** to find existing backlog entries: ```bash cat .planning/ROADMAP.md ``` 2. **Find next backlog number:** ```bash NEXT=$(node "D:/Projects/Yavin-v1.2.0/Yavin-v1.2.0/Yavin-v1.1.0/.claude/get-shit-done/bin/gsd-tools.cjs" phase next-decimal 999 --raw) ``` If no 999.x phases exist, start at 999.1. 3. **Create the phase directory:** ```bash SLUG=$(node "D:/Projects/Yavin-v1.2.0/Yavin-v1.2.0/Yavin-v1.1.0/.claude/get-shit-done/bin/gsd-tools.cjs" generate-slug "{{arguments}}") mkdir -p ".planning/phases/{{NEXT}}-{{SLUG}}" touch ".planning/phases/{{NEXT}}-{{SLUG}}/.gitkeep" ``` 4. **Add to ROADMAP.md** under a `## Backlog` section. If the section doesn't exist, create it at the end: ```markdown ## Backlog ### Phase {NEXT}: {description} (BACKLOG) **Goal:** [Captured for future planning] **Requirements:** TBD **Plans:** 0 plans Plans: - [ ] TBD (promote with /gsd:review-backlog when ready) ``` 5. **Commit:** ```bash node "D:/Projects/Yavin-v1.2.0/Yavin-v1.2.0/Yavin-v1.1.0/.claude/get-shit-done/bin/gsd-tools.cjs" commit "docs: add backlog item {{NEXT}} — {{ARGUMENTS}}" --files .planning/ROADMAP.md ".planning/phases/{{NEXT}}-{{SLUG}}/.gitkeep" ``` 6. **Report:** ``` ## 📋 Backlog Item Added Phase {NEXT}: {description} Directory: .planning/phases/{NEXT}-{slug}/ This item lives in the backlog parking lot. Use /gsd:discuss-phase {NEXT} to explore it further. Use /gsd:review-backlog to promote items to active milestone. ``` </process> <notes> - 999.x numbering keeps backlog items out of the active phase sequence - Phase directories are created immediately, so /gsd:discuss-phase and /gsd:plan-phase work on them - No `Depends on:` field — backlog items are unsequenced by definition - Sparse numbering is fine (999.1, 999.3) — always uses next-decimal </notes>

{ "prompt": "<objective>\nAdd a backlog item to the roadmap using 999.x numbering. Backlog items are\nunsequenced ideas that aren't ready for active planning — they live outside\nthe normal phase sequence and accumulate context over time.\n</objective>\n\n<process>\n\n1. **Read ROADMAP.md** to find existing backlog entries:\n ```bash\n cat .planning/ROADMAP.md\n ```\n\n2. **Find next backlog number:**\n ```bash\n NEXT=$(node \"D:/Projects/Yavin-v1.2.0/Yavin-v1.2.0/Yavin-v1.1.0/.claude/get-shit-done/bin/gsd-tools.cjs\" phase next-decimal 999 --raw)\n ```\n If no 999.x phases exist, start at 999.1.\n\n3. **Create the phase directory:**\n ```bash\n SLUG=$(node \"D:/Projects/Yavin-v1.2.0/Yavin-v1.2.0/Yavin-v1.1.0/.claude/get-shit-done/bin/gsd-tools.cjs\" generate-slug \"{{arguments}}\")\n mkdir -p \".planning/phases/{{NEXT}}-{{SLUG}}\"\n touch \".planning/phases/{{NEXT}}-{{SLUG}}/.gitkeep\"\n ```\n\n4. **Add to ROADMAP.md** under a `## Backlog` section. If the section doesn't exist, create it at the end:\n\n ```markdown\n ## Backlog\n\n ### Phase {NEXT}: {description} (BACKLOG)\n\n **Goal:** [Captured for future planning]\n **Requirements:** TBD\n **Plans:** 0 plans\n\n Plans:\n - [ ] TBD (promote with /gsd:review-backlog when ready)\n ```\n\n5. **Commit:**\n ```bash\n node \"D:/Projects/Yavin-v1.2.0/Yavin-v1.2.0/Yavin-v1.1.0/.claude/get-shit-done/bin/gsd-tools.cjs\" commit \"docs: add backlog item {{NEXT}} — {{ARGUMENTS}}\" --files .planning/ROADMAP.md \".planning/phases/{{NEXT}}-{{SLUG}}/.gitkeep\"\n ```\n\n6. **Report:**\n ```\n ## 📋 Backlog Item Added\n\n Phase {NEXT}: {description}\n Directory: .planning/phases/{NEXT}-{slug}/\n\n This item lives in the backlog parking lot.\n Use /gsd:discuss-phase {NEXT} to explore it further.\n Use /gsd:review-backlog to promote items to active milestone.\n ```\n\n</process>\n\n<notes>\n- 999.x numbering keeps backlog items out of the active phase sequence\n- Phase directories are created immediately, so /gsd:discuss-phase and /gsd:plan-phase work on them\n- No `Depends on:` field — backlog items are unsequenced by definition\n- Sparse numbering is fine (999.1, 999.3) — always uses next-decimal\n</notes>", "variables": [ "arguments", "NEXT", "SLUG", "ARGUMENTS" ], "notes": "Add an idea to the backlog parking lot (999.x numbering) Tools: Read, Write, Bash. Arguments: <description>.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/salmanwnl44/Yavin-v1.2.0", "path": ".claude/commands/gsd/add-backlog.md", "ref": "8bc8859b167b9dad0f0c1808eab6049ce8a1b5f9", "url": "https://github.com/salmanwnl44/Yavin-v1.2.0/blob/8bc8859b167b9dad0f0c1808eab6049ce8a1b5f9/.claude/commands/gsd/add-backlog.md", "key": "salmanwnl44/Yavin-v1.2.0/.claude/commands/gsd/add-backlog.md" } } }

gsd:add-backlog

About

Install gsd:add-backlog 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