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.

3_task-implement - Prompt - OpenSmartRoute

Name: 3_task-implement
Author: yukuma236

Prompt file imported from yukuma236/AIAutomateCodingTest (.github/prompts/3_task-implement.prompt.md). Copyright stays with the author.

Implement Task

Implement and validate only the explicitly approved plan.

Entry conditions

Read the approved Research handoff, approved business specifications, approved Plan, and applicable Test Specification/Test Case from the repository or current conversation. Do not rely on chat history that was not handed over.
If approval is missing, required artifacts are unavailable, or an implementation detail would change approved business behavior, stop implementation and return the issue to Research or Plan for resolution and approval.
Reconfirm project requirements and only the relevant shared standards through standards/docs/README.md. If present in the submodule, explicitly read standards/.github/copilot-instructions.md.

Implement and validate

Make the smallest change that fulfills the approved plan. Do not widen scope or reinterpret business behavior.
For Power Automate cloud flow changes, use the available Power Automate skills and FlowAgent MCP tools. Retrieve the current definition again with get_flow before changing an existing flow. Do not hand-edit and upload an exported JSON as an ordinary text file; use edit_flow for surgical changes or update_flow when a full definition is appropriate.
Use src/flows/ for local exports. Run preflight_flow/validate_flow where available before creation or update. If the required tools or synchronization are unavailable, report that limitation and do not make flow changes.
Prefer Developer or Sandbox. Do not use Production without explicit authorization and a documented justification.
Validate every approved Test Case against its approved expected result. Use run_flow for instant/HTTP-triggered flows or get_past_trigger_inputs and resubmit_run for event-triggered flows as appropriate; use get_run_actions, get_run_action_content, and diagnose_run to verify the results.
Do not derive or alter expected results from the implemented flow's observed behavior. Report mismatches as failures and request a specification decision rather than silently changing the expected result.
Record evidence per Test Specification and Case, including pass/fail, actual result, and the full Run URL. Confirm that src/flows/ is synchronized with the resulting Power Platform definition.
If validation requires a business-specification change, stop and return to Research; if the technical approach or scope must change, return to Plan and obtain approval before continuing.

Completion handoff

Report changes, target environment, validation results by case, evidence locations/Run URLs, synchronization status, and any deviations or blockers. Keep the approved specifications and plan as the durable source of truth for a later chat.

Install 3_task-implement 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.

# Implement Task Implement and validate only the explicitly approved plan. ## Entry conditions 1. Read the approved Research handoff, approved business specifications, approved Plan, and applicable Test Specification/Test Case from the repository or current conversation. Do not rely on chat history that was not handed over. 2. If approval is missing, required artifacts are unavailable, or an implementation detail would change approved business behavior, stop implementation and return the issue to Research or Plan for resolution and approval. 3. Reconfirm project requirements and only the relevant shared standards through `standards/docs/README.md`. If present in the submodule, explicitly read `standards/.github/copilot-instructions.md`. ## Implement and validate * Make the smallest change that fulfills the approved plan. Do not widen scope or reinterpret business behavior. * For Power Automate cloud flow changes, use the available Power Automate skills and FlowAgent MCP tools. Retrieve the current definition again with `get_flow` before changing an existing flow. Do not hand-edit and upload an exported JSON as an ordinary text file; use `edit_flow` for surgical changes or `update_flow` when a full definition is appropriate. * Use `src/flows/` for local exports. Run `preflight_flow`/`validate_flow` where available before creation or update. If the required tools or synchronization are unavailable, report that limitation and do not make flow changes. * Prefer Developer or Sandbox. Do not use Production without explicit authorization and a documented justification. * Validate every approved Test Case against its approved expected result. Use `run_flow` for instant/HTTP-triggered flows or `get_past_trigger_inputs` and `resubmit_run` for event-triggered flows as appropriate; use `get_run_actions`, `get_run_action_content`, and `diagnose_run` to verify the results. * Do not derive or alter expected results from the implemented flow's observed behavior. Report mismatches as failures and request a specification decision rather than silently changing the expected result. * Record evidence per Test Specification and Case, including pass/fail, actual result, and the full Run URL. Confirm that `src/flows/` is synchronized with the resulting Power Platform definition. * If validation requires a business-specification change, stop and return to Research; if the technical approach or scope must change, return to Plan and obtain approval before continuing. ## Completion handoff Report changes, target environment, validation results by case, evidence locations/Run URLs, synchronization status, and any deviations or blockers. Keep the approved specifications and plan as the durable source of truth for a later chat.

{ "prompt": "# Implement Task\n\nImplement and validate only the explicitly approved plan.\n\n## Entry conditions\n\n1. Read the approved Research handoff, approved business specifications, approved Plan, and applicable Test Specification/Test Case from the repository or current conversation. Do not rely on chat history that was not handed over.\n2. If approval is missing, required artifacts are unavailable, or an implementation detail would change approved business behavior, stop implementation and return the issue to Research or Plan for resolution and approval.\n3. Reconfirm project requirements and only the relevant shared standards through `standards/docs/README.md`. If present in the submodule, explicitly read `standards/.github/copilot-instructions.md`.\n\n## Implement and validate\n\n* Make the smallest change that fulfills the approved plan. Do not widen scope or reinterpret business behavior.\n* For Power Automate cloud flow changes, use the available Power Automate skills and FlowAgent MCP tools. Retrieve the current definition again with `get_flow` before changing an existing flow. Do not hand-edit and upload an exported JSON as an ordinary text file; use `edit_flow` for surgical changes or `update_flow` when a full definition is appropriate.\n* Use `src/flows/` for local exports. Run `preflight_flow`/`validate_flow` where available before creation or update. If the required tools or synchronization are unavailable, report that limitation and do not make flow changes.\n* Prefer Developer or Sandbox. Do not use Production without explicit authorization and a documented justification.\n* Validate every approved Test Case against its approved expected result. Use `run_flow` for instant/HTTP-triggered flows or `get_past_trigger_inputs` and `resubmit_run` for event-triggered flows as appropriate; use `get_run_actions`, `get_run_action_content`, and `diagnose_run` to verify the results.\n* Do not derive or alter expected results from the implemented flow's observed behavior. Report mismatches as failures and request a specification decision rather than silently changing the expected result.\n* Record evidence per Test Specification and Case, including pass/fail, actual result, and the full Run URL. Confirm that `src/flows/` is synchronized with the resulting Power Platform definition.\n* If validation requires a business-specification change, stop and return to Research; if the technical approach or scope must change, return to Plan and obtain approval before continuing.\n\n## Completion handoff\n\nReport changes, target environment, validation results by case, evidence locations/Run URLs, synchronization status, and any deviations or blockers. Keep the approved specifications and plan as the durable source of truth for a later chat.", "variables": [], "notes": "Implement and validate only the explicitly approved plan.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/yukuma236/AIAutomateCodingTest", "path": ".github/prompts/3_task-implement.prompt.md", "ref": "fb6844515df359f220d474ee0d9ab1b0f53033bb", "url": "https://github.com/yukuma236/AIAutomateCodingTest/blob/fb6844515df359f220d474ee0d9ab1b0f53033bb/.github/prompts/3_task-implement.prompt.md", "key": "yukuma236/AIAutomateCodingTest/.github/prompts/3_task-implement.prompt.md" } } }

3_task-implement

About

Implement Task

Entry conditions

Implement and validate

Completion handoff

Install 3_task-implement 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