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:map-codebase - Prompt - OpenSmartRoute

Name: gsd:map-codebase
Author: PetriLahdelma

Prompt file imported from PetriLahdelma/digitaltableteur (.claude/commands/gsd/map-codebase.md). Fill in {{arguments}} before use. Copyright stays with the author.

This command spawns multiple Explore agents to analyze different aspects of the codebase in parallel, each with fresh context.

Output: .planning/codebase/ folder with 7 structured documents about the codebase state.

<execution_context> @./.claude/get-shit-done/workflows/map-codebase.md @./.claude/get-shit-done/templates/codebase/stack.md @./.claude/get-shit-done/templates/codebase/architecture.md @./.claude/get-shit-done/templates/codebase/structure.md @./.claude/get-shit-done/templates/codebase/conventions.md @./.claude/get-shit-done/templates/codebase/testing.md @./.claude/get-shit-done/templates/codebase/integrations.md @./.claude/get-shit-done/templates/codebase/concerns.md </execution_context>

Load project state if exists: Check for .planning/STATE.md - loads context if project already initialized

This command can run:

Before /gsd:new-project (brownfield codebases) - creates codebase map first
After /gsd:new-project (greenfield codebases) - updates codebase map as code evolves
Anytime to refresh codebase understanding

<when_to_use> Use map-codebase for:

Brownfield projects before initialization (understand existing code first)
Refreshing codebase map after significant changes
Onboarding to an unfamiliar codebase
Before major refactoring (understand current state)
When STATE.md references outdated codebase info

Skip map-codebase for:

Greenfield projects with no code yet (nothing to map)
Trivial codebases (<5 files) </when_to_use>

<success_criteria>

.planning/codebase/ directory created
All 7 codebase documents written
Documents follow template structure
Parallel agents completed without errors
User knows next steps </success_criteria>

Install gsd:map-codebase 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> Analyze existing codebase using parallel Explore agents to produce structured codebase documents. This command spawns multiple Explore agents to analyze different aspects of the codebase in parallel, each with fresh context. Output: .planning/codebase/ folder with 7 structured documents about the codebase state. </objective> <execution_context> @./.claude/get-shit-done/workflows/map-codebase.md @./.claude/get-shit-done/templates/codebase/stack.md @./.claude/get-shit-done/templates/codebase/architecture.md @./.claude/get-shit-done/templates/codebase/structure.md @./.claude/get-shit-done/templates/codebase/conventions.md @./.claude/get-shit-done/templates/codebase/testing.md @./.claude/get-shit-done/templates/codebase/integrations.md @./.claude/get-shit-done/templates/codebase/concerns.md </execution_context> <context> Focus area: {{arguments}} (optional - if provided, tells agents to focus on specific subsystem) **Load project state if exists:** Check for .planning/STATE.md - loads context if project already initialized **This command can run:** - Before /gsd:new-project (brownfield codebases) - creates codebase map first - After /gsd:new-project (greenfield codebases) - updates codebase map as code evolves - Anytime to refresh codebase understanding </context> <when_to_use> **Use map-codebase for:** - Brownfield projects before initialization (understand existing code first) - Refreshing codebase map after significant changes - Onboarding to an unfamiliar codebase - Before major refactoring (understand current state) - When STATE.md references outdated codebase info **Skip map-codebase for:** - Greenfield projects with no code yet (nothing to map) - Trivial codebases (<5 files) </when_to_use> <process> 1. Check if .planning/codebase/ already exists (offer to refresh or skip) 2. Create .planning/codebase/ directory structure 3. Spawn 4 parallel Explore agents to analyze codebase: - Agent 1: Stack + Integrations (technology focus) - Agent 2: Architecture + Structure (organization focus) - Agent 3: Conventions + Testing (quality focus) - Agent 4: Concerns (issues focus) 4. Wait for all agents to complete, collect findings 5. Write 7 codebase documents using templates: - STACK.md - Languages, frameworks, key dependencies - ARCHITECTURE.md - System design, patterns, data flow - STRUCTURE.md - Directory layout, module organization - CONVENTIONS.md - Code style, naming, patterns - TESTING.md - Test structure, coverage, practices - INTEGRATIONS.md - APIs, databases, external services - CONCERNS.md - Technical debt, risks, issues 6. Offer next steps (typically: /gsd:new-project or /gsd:plan-phase) </process> <success_criteria> - [ ] .planning/codebase/ directory created - [ ] All 7 codebase documents written - [ ] Documents follow template structure - [ ] Parallel agents completed without errors - [ ] User knows next steps </success_criteria>

{ "prompt": "<objective>\nAnalyze existing codebase using parallel Explore agents to produce structured codebase documents.\n\nThis command spawns multiple Explore agents to analyze different aspects of the codebase in parallel, each with fresh context.\n\nOutput: .planning/codebase/ folder with 7 structured documents about the codebase state.\n</objective>\n\n<execution_context>\n@./.claude/get-shit-done/workflows/map-codebase.md\n@./.claude/get-shit-done/templates/codebase/stack.md\n@./.claude/get-shit-done/templates/codebase/architecture.md\n@./.claude/get-shit-done/templates/codebase/structure.md\n@./.claude/get-shit-done/templates/codebase/conventions.md\n@./.claude/get-shit-done/templates/codebase/testing.md\n@./.claude/get-shit-done/templates/codebase/integrations.md\n@./.claude/get-shit-done/templates/codebase/concerns.md\n</execution_context>\n\n<context>\nFocus area: {{arguments}} (optional - if provided, tells agents to focus on specific subsystem)\n\n**Load project state if exists:**\nCheck for .planning/STATE.md - loads context if project already initialized\n\n**This command can run:**\n- Before /gsd:new-project (brownfield codebases) - creates codebase map first\n- After /gsd:new-project (greenfield codebases) - updates codebase map as code evolves\n- Anytime to refresh codebase understanding\n</context>\n\n<when_to_use>\n**Use map-codebase for:**\n- Brownfield projects before initialization (understand existing code first)\n- Refreshing codebase map after significant changes\n- Onboarding to an unfamiliar codebase\n- Before major refactoring (understand current state)\n- When STATE.md references outdated codebase info\n\n**Skip map-codebase for:**\n- Greenfield projects with no code yet (nothing to map)\n- Trivial codebases (<5 files)\n</when_to_use>\n\n<process>\n1. Check if .planning/codebase/ already exists (offer to refresh or skip)\n2. Create .planning/codebase/ directory structure\n3. Spawn 4 parallel Explore agents to analyze codebase:\n - Agent 1: Stack + Integrations (technology focus)\n - Agent 2: Architecture + Structure (organization focus)\n - Agent 3: Conventions + Testing (quality focus)\n - Agent 4: Concerns (issues focus)\n4. Wait for all agents to complete, collect findings\n5. Write 7 codebase documents using templates:\n - STACK.md - Languages, frameworks, key dependencies\n - ARCHITECTURE.md - System design, patterns, data flow\n - STRUCTURE.md - Directory layout, module organization\n - CONVENTIONS.md - Code style, naming, patterns\n - TESTING.md - Test structure, coverage, practices\n - INTEGRATIONS.md - APIs, databases, external services\n - CONCERNS.md - Technical debt, risks, issues\n6. Offer next steps (typically: /gsd:new-project or /gsd:plan-phase)\n</process>\n\n<success_criteria>\n- [ ] .planning/codebase/ directory created\n- [ ] All 7 codebase documents written\n- [ ] Documents follow template structure\n- [ ] Parallel agents completed without errors\n- [ ] User knows next steps\n</success_criteria>", "variables": [ "arguments" ], "notes": "Analyze codebase with parallel Explore agents to produce .planning/codebase/ documents Tools: Read, Bash, Glob, Grep, Write, Task. Arguments: [optional: specific area to map, e.g., 'api' or 'auth'].", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/PetriLahdelma/digitaltableteur", "path": ".claude/commands/gsd/map-codebase.md", "ref": "fa86fd04107591d261f480d40fc5af25b1ee383c", "url": "https://github.com/PetriLahdelma/digitaltableteur/blob/fa86fd04107591d261f480d40fc5af25b1ee383c/.claude/commands/gsd/map-codebase.md", "key": "PetriLahdelma/digitaltableteur/.claude/commands/gsd/map-codebase.md" } } }

gsd:map-codebase

About

Install gsd:map-codebase 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