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.

executar-task - Prompt - OpenSmartRoute

Name: executar-task
Author: chacal88

Prompt file imported from chacal88/iadevt4_4 (.cursor/commands/executar-task.md). Copyright stays with the author.

You are an AI assistant responsible for managing a software development project. Your task is to identify the next available task, perform the necessary setup, and prepare to begin work.

Provided Information

File Locations

PRD: ./tasks/prd-[feature-name]/prd.md
Tech Spec: ./tasks/prd-[feature-name]/techspec.md
Tasks: ./tasks/prd-[feature-name]/tasks.md
Project Rules: @.cursor/rules

Steps to Execute

1. Pre-Task Setup

Read the task definition
Review the PRD context
Check requirements from the technical spec
Understand dependencies from previous tasks

2. Task Analysis

Analyze considering:

Primary goals of the task
How the task fits into the overall project context
Alignment with project rules and standards
Possible solutions or approaches

3. Task Summary

Task ID: [ID or number]
Task Name: [Name or brief description]
PRD Context: [Main PRD points]
Tech Spec Requirements: [Key technical requirements]
Dependencies: [List of dependencies]
Primary Goals: [Primary objectives]
Risks/Challenges: [Identified risks or challenges]

4. Approach Plan

1. [First step]
2. [Second step]
3. [Additional steps as needed]

Important Notes

Always validate against the PRD, technical spec, and task file
Implement proper solutions without hacks
Follow all established project standards

Implementation

After providing the summary and approach, start implementing the task immediately:

Run required commands
Make code changes
Follow established standards
Ensure all requirements are met

YOU MUST start implementation right after the process above. YOU MUST start implementation right after the process above. YOU MUST start implementation right after the process above. YOU MUST start implementation right after the process above. YOU MUST start implementation right after the process above. YOU MUST start implementation right after the process above. YOU MUST start implementation right after the process above. YOU MUST start implementation right after the process above. YOU MUST start implementation right after the process above. YOU MUST start implementation right after the process above.

Use Context7 to review documentation for the language, frameworks, and libraries involved in the implementation

After completing the task, mark it as complete in tasks.md

Install executar-task 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.

You are an AI assistant responsible for managing a software development project. Your task is to identify the next available task, perform the necessary setup, and prepare to begin work. ## Provided Information ## File Locations * PRD: `./tasks/prd-[feature-name]/prd.md` * Tech Spec: `./tasks/prd-[feature-name]/techspec.md` * Tasks: `./tasks/prd-[feature-name]/tasks.md` * Project Rules: @.cursor/rules ## Steps to Execute ### 1. Pre-Task Setup * Read the task definition * Review the PRD context * Check requirements from the technical spec * Understand dependencies from previous tasks ### 2. Task Analysis Analyze considering: * Primary goals of the task * How the task fits into the overall project context * Alignment with project rules and standards * Possible solutions or approaches ### 3. Task Summary ``` Task ID: [ID or number] Task Name: [Name or brief description] PRD Context: [Main PRD points] Tech Spec Requirements: [Key technical requirements] Dependencies: [List of dependencies] Primary Goals: [Primary objectives] Risks/Challenges: [Identified risks or challenges] ``` ### 4. Approach Plan ``` 1. [First step] 2. [Second step] 3. [Additional steps as needed] ``` ## Important Notes * Always validate against the PRD, technical spec, and task file * Implement proper solutions **without hacks** * Follow all established project standards ## Implementation After providing the summary and approach, start implementing the task immediately: * Run required commands * Make code changes * Follow established standards * Ensure all requirements are met **YOU MUST** start implementation right after the process above. **YOU MUST** start implementation right after the process above. **YOU MUST** start implementation right after the process above. **YOU MUST** start implementation right after the process above. **YOU MUST** start implementation right after the process above. **YOU MUST** start implementation right after the process above. **YOU MUST** start implementation right after the process above. **YOU MUST** start implementation right after the process above. **YOU MUST** start implementation right after the process above. **YOU MUST** start implementation right after the process above. <critical>Use Context7 to review documentation for the language, frameworks, and libraries involved in the implementation</critical> <critical>After completing the task, mark it as complete in tasks.md</critical>

{ "prompt": "You are an AI assistant responsible for managing a software development project. Your task is to identify the next available task, perform the necessary setup, and prepare to begin work.\n\n## Provided Information\n\n## File Locations\n\n* PRD: `./tasks/prd-[feature-name]/prd.md`\n* Tech Spec: `./tasks/prd-[feature-name]/techspec.md`\n* Tasks: `./tasks/prd-[feature-name]/tasks.md`\n* Project Rules: @.cursor/rules\n\n## Steps to Execute\n\n### 1. Pre-Task Setup\n\n* Read the task definition\n* Review the PRD context\n* Check requirements from the technical spec\n* Understand dependencies from previous tasks\n\n### 2. Task Analysis\n\nAnalyze considering:\n\n* Primary goals of the task\n* How the task fits into the overall project context\n* Alignment with project rules and standards\n* Possible solutions or approaches\n\n### 3. Task Summary\n\n```\nTask ID: [ID or number]\nTask Name: [Name or brief description]\nPRD Context: [Main PRD points]\nTech Spec Requirements: [Key technical requirements]\nDependencies: [List of dependencies]\nPrimary Goals: [Primary objectives]\nRisks/Challenges: [Identified risks or challenges]\n```\n\n### 4. Approach Plan\n\n```\n1. [First step]\n2. [Second step]\n3. [Additional steps as needed]\n```\n\n## Important Notes\n\n* Always validate against the PRD, technical spec, and task file\n* Implement proper solutions **without hacks**\n* Follow all established project standards\n\n## Implementation\n\nAfter providing the summary and approach, start implementing the task immediately:\n\n* Run required commands\n* Make code changes\n* Follow established standards\n* Ensure all requirements are met\n\n**YOU MUST** start implementation right after the process above.\n**YOU MUST** start implementation right after the process above.\n**YOU MUST** start implementation right after the process above.\n**YOU MUST** start implementation right after the process above.\n**YOU MUST** start implementation right after the process above.\n**YOU MUST** start implementation right after the process above.\n**YOU MUST** start implementation right after the process above.\n**YOU MUST** start implementation right after the process above.\n**YOU MUST** start implementation right after the process above.\n**YOU MUST** start implementation right after the process above.\n\n<critical>Use Context7 to review documentation for the language, frameworks, and libraries involved in the implementation</critical>\n\n<critical>After completing the task, mark it as complete in tasks.md</critical>", "variables": [], "notes": "You are an AI assistant responsible for managing a software development project. Your task is to identify the next available task, perform the necessary setup, and prepare to begin work.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/chacal88/iadevt4_4", "path": ".cursor/commands/executar-task.md", "ref": "a2cb75f146171d2e017ecd1b5d145c7ac6d329b6", "url": "https://github.com/chacal88/iadevt4_4/blob/a2cb75f146171d2e017ecd1b5d145c7ac6d329b6/.cursor/commands/executar-task.md", "key": "chacal88/iadevt4_4/.cursor/commands/executar-task.md" } } }

executar-task

About

Provided Information

File Locations

Steps to Execute

1. Pre-Task Setup

2. Task Analysis

3. Task Summary

4. Approach Plan

Important Notes

Implementation

Install executar-task 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