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.

shakeout - Prompt - OpenSmartRoute

Name: shakeout
Author: bairep

Prompt file imported from bairep/FeatureFramework (.claude/commands/shakeout.md). Fill in {{arguments}} before use. Copyright stays with the author.

Shakeout

Break down and categorize the ideas given in {{arguments}} (or, if empty, the ideas in the current conversation or the ideation file the user points to) into three categories: Research, Prototype, and Features.

Output format

Write the result in this structure:

# Research Priority

| Title | Research Prompt | Status |
| ----- | --------------- | ------ |
| {title} | {prompt} | {todo, started, done with link to results}

# Prototype

| Title | Prototype Prompt | Status |
| ----- | --------------- | ------ |
| {title} | {prompt} | {todo, started, done with link to prototype}

# Features

| Title | Description | Status |
| ----- | --------------- | ------ |
| {title} | {description} | {todo, started, done with link to feature in backlog}

Rules

Each idea goes into exactly one category:
- Research: open questions that need investigation before a decision. Write a research prompt.
- Prototype: ideas that must be proven with a throwaway build. Write a prototype prompt.
- Features: ideas ready to implement. Write a short description.
Set status to todo for new items. When results exist, replace the status with a link to the file in ./Research/, ./Prototypes/, or ./Backlog/.
Show the categorized list to the user and confirm before you save it to a file.

Heuristic

flowchart TD
    A[New Idea] --> B{Too large and abstract?}
    B -- Yes --> C[Decompose, then classify each part]
    B -- No --> D{Plan can be formed?}
    D -- No --> R1
    D -- Yes --> E{Open question a build must answer?}
    E -- Yes --> P1
    E -- No --> F{All components actionable?}
    F -- Yes --> G[Feature to Backlog]
    F -- No --> H{Any usable part?}
    H -- Yes --> I[Split: ready part to Backlog, weak part reclassified]
    H -- No --> J[Stays an Idea: blocker reclassified]

    subgraph Research
      R1[Investigate] --> R2{Plan found?}
      R2 -- Yes --> R3[Reclassify idea]
      R2 -- No, exhausted --> R4[Abandon]
    end

    subgraph Prototype
      P1[Build experiment] --> P2[Document result and next steps]
      P2 --> P3[Reclassify, pivot, research more, or abandon]
    end

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

# Shakeout Break down and categorize the ideas given in `{{arguments}}` (or, if empty, the ideas in the current conversation or the ideation file the user points to) into three categories: Research, Prototype, and Features. ## Output format Write the result in this structure: ```md # Research Priority | Title | Research Prompt | Status | | ----- | --------------- | ------ | | {title} | {prompt} | {todo, started, done with link to results} # Prototype | Title | Prototype Prompt | Status | | ----- | --------------- | ------ | | {title} | {prompt} | {todo, started, done with link to prototype} # Features | Title | Description | Status | | ----- | --------------- | ------ | | {title} | {description} | {todo, started, done with link to feature in backlog} ``` ## Rules - Each idea goes into exactly one category: - **Research**: open questions that need investigation before a decision. Write a research prompt. - **Prototype**: ideas that must be proven with a throwaway build. Write a prototype prompt. - **Features**: ideas ready to implement. Write a short description. - Set `status` to `todo` for new items. When results exist, replace the status with a link to the file in `./Research/`, `./Prototypes/`, or `./Backlog/`. - Show the categorized list to the user and confirm before you save it to a file. ### Heuristic ```mermaid flowchart TD A[New Idea] --> B{Too large and abstract?} B -- Yes --> C[Decompose, then classify each part] B -- No --> D{Plan can be formed?} D -- No --> R1 D -- Yes --> E{Open question a build must answer?} E -- Yes --> P1 E -- No --> F{All components actionable?} F -- Yes --> G[Feature to Backlog] F -- No --> H{Any usable part?} H -- Yes --> I[Split: ready part to Backlog, weak part reclassified] H -- No --> J[Stays an Idea: blocker reclassified] subgraph Research R1[Investigate] --> R2{Plan found?} R2 -- Yes --> R3[Reclassify idea] R2 -- No, exhausted --> R4[Abandon] end subgraph Prototype P1[Build experiment] --> P2[Document result and next steps] P2 --> P3[Reclassify, pivot, research more, or abandon] end ```

{ "prompt": "# Shakeout\n\nBreak down and categorize the ideas given in `{{arguments}}` (or, if empty, the ideas in the current conversation or the ideation file the user points to) into three categories: Research, Prototype, and Features.\n\n## Output format\n\nWrite the result in this structure:\n\n```md\n# Research Priority\n\n| Title | Research Prompt | Status |\n| ----- | --------------- | ------ |\n| {title} | {prompt} | {todo, started, done with link to results}\n\n# Prototype\n\n| Title | Prototype Prompt | Status |\n| ----- | --------------- | ------ |\n| {title} | {prompt} | {todo, started, done with link to prototype}\n\n# Features\n\n| Title | Description | Status |\n| ----- | --------------- | ------ |\n| {title} | {description} | {todo, started, done with link to feature in backlog}\n```\n\n## Rules\n\n- Each idea goes into exactly one category:\n - **Research**: open questions that need investigation before a decision. Write a research prompt.\n - **Prototype**: ideas that must be proven with a throwaway build. Write a prototype prompt.\n - **Features**: ideas ready to implement. Write a short description.\n- Set `status` to `todo` for new items. When results exist, replace the status with a link to the file in `./Research/`, `./Prototypes/`, or `./Backlog/`.\n- Show the categorized list to the user and confirm before you save it to a file.\n\n### Heuristic\n\n```mermaid\nflowchart TD\n A[New Idea] --> B{Too large and abstract?}\n B -- Yes --> C[Decompose, then classify each part]\n B -- No --> D{Plan can be formed?}\n D -- No --> R1\n D -- Yes --> E{Open question a build must answer?}\n E -- Yes --> P1\n E -- No --> F{All components actionable?}\n F -- Yes --> G[Feature to Backlog]\n F -- No --> H{Any usable part?}\n H -- Yes --> I[Split: ready part to Backlog, weak part reclassified]\n H -- No --> J[Stays an Idea: blocker reclassified]\n\n subgraph Research\n R1[Investigate] --> R2{Plan found?}\n R2 -- Yes --> R3[Reclassify idea]\n R2 -- No, exhausted --> R4[Abandon]\n end\n\n subgraph Prototype\n P1[Build experiment] --> P2[Document result and next steps]\n P2 --> P3[Reclassify, pivot, research more, or abandon]\n end\n```", "variables": [ "arguments" ], "notes": "Break down and categorize ideas into Research, Prototype, and Features", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/bairep/FeatureFramework", "path": ".claude/commands/shakeout.md", "ref": "167fe62b2bc5d46904cb57df0047a9fe124e63e1", "url": "https://github.com/bairep/FeatureFramework/blob/167fe62b2bc5d46904cb57df0047a9fe124e63e1/.claude/commands/shakeout.md", "key": "bairep/FeatureFramework/.claude/commands/shakeout.md" } } }

shakeout

About

Shakeout

Output format

Rules

Heuristic

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