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.

TEST_reviewDesignTestsSkeleton - Prompt

Name: TEST_reviewDesignTestsSkeleton
Author: EnigmaWU

Prompt file imported from EnigmaWU/MyCaTDD (.github/prompts/TEST_reviewDesignTestsSkeleton.prompt.md). Copyright stays with the author.

TEST_reviewDesignTestsSkeleton

You are running a Copilot-native wrapper around a portable CaTDD slash command.

Source Command

Portable command path: slashCommands/commands/P1-DesignTestsFlow/TEST_reviewDesignTestsSkeleton.md
Default workspace link: slashCommands/commands/P1-DesignTestsFlow/TEST_reviewDesignTestsSkeleton.md
Flow or kit: P1-DesignTestsFlow

Method Source of Truth

CaTDD method index: methodPrompts/README.md
Slash command contract: slashCommands/TEST_slashCommandTemplate.md
Flow docs: slashCommands/flows
Kit docs: slashCommands/kits

Execution Rules

Read and follow the portable source command before acting.
Treat this file as a thin Copilot adapter; do not redefine CaTDD method semantics here.
Use methodPrompts for category meaning, priority order, design skeleton rules, and CaTDD constraints.
Use the source command for inputs, outputs, conflict guards, and next-step flow or kit contract.
Ask for missing product intent instead of inventing requirements.
Report the next recommended slash command when the step finishes.

ONE-MORE-THING: ask developer if something not sure

# TEST_reviewDesignTestsSkeleton You are running a Copilot-native wrapper around a portable CaTDD slash command. ## Source Command - Portable command path: slashCommands/commands/P1-DesignTestsFlow/TEST_reviewDesignTestsSkeleton.md - Default workspace link: [slashCommands/commands/P1-DesignTestsFlow/TEST_reviewDesignTestsSkeleton.md](../../slashCommands/commands/P1-DesignTestsFlow/TEST_reviewDesignTestsSkeleton.md) - Flow or kit: P1-DesignTestsFlow ## Method Source of Truth - CaTDD method index: [methodPrompts/README.md](../../methodPrompts/README.md) - Slash command contract: [slashCommands/TEST_slashCommandTemplate.md](../../slashCommands/TEST_slashCommandTemplate.md) - Flow docs: [slashCommands/flows](../../slashCommands/flows) - Kit docs: [slashCommands/kits](../../slashCommands/kits) ## Execution Rules 1. Read and follow the portable source command before acting. 2. Treat this file as a thin Copilot adapter; do not redefine CaTDD method semantics here. 3. Use methodPrompts for category meaning, priority order, design skeleton rules, and CaTDD constraints. 4. Use the source command for inputs, outputs, conflict guards, and next-step flow or kit contract. 5. Ask for missing product intent instead of inventing requirements. 6. Report the next recommended slash command when the step finishes. ONE-MORE-THING: ask developer if something not sure

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

{ "prompt": "# TEST_reviewDesignTestsSkeleton\n\nYou are running a Copilot-native wrapper around a portable CaTDD slash command.\n\n## Source Command\n\n- Portable command path: slashCommands/commands/P1-DesignTestsFlow/TEST_reviewDesignTestsSkeleton.md\n- Default workspace link: [slashCommands/commands/P1-DesignTestsFlow/TEST_reviewDesignTestsSkeleton.md](../../slashCommands/commands/P1-DesignTestsFlow/TEST_reviewDesignTestsSkeleton.md)\n- Flow or kit: P1-DesignTestsFlow\n\n## Method Source of Truth\n\n- CaTDD method index: [methodPrompts/README.md](../../methodPrompts/README.md)\n- Slash command contract: [slashCommands/TEST_slashCommandTemplate.md](../../slashCommands/TEST_slashCommandTemplate.md)\n- Flow docs: [slashCommands/flows](../../slashCommands/flows)\n- Kit docs: [slashCommands/kits](../../slashCommands/kits)\n\n## Execution Rules\n\n1. Read and follow the portable source command before acting.\n2. Treat this file as a thin Copilot adapter; do not redefine CaTDD method semantics here.\n3. Use methodPrompts for category meaning, priority order, design skeleton rules, and CaTDD constraints.\n4. Use the source command for inputs, outputs, conflict guards, and next-step flow or kit contract.\n5. Ask for missing product intent instead of inventing requirements.\n6. Report the next recommended slash command when the step finishes.\n\nONE-MORE-THING: ask developer if something not sure", "variables": [], "notes": "Run CaTDD slash command TEST_reviewDesignTestsSkeleton Arguments: Fill required command inputs, source files, target files, language, and test framework.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/EnigmaWU/MyCaTDD", "path": ".github/prompts/TEST_reviewDesignTestsSkeleton.prompt.md", "ref": "1eb6433f746f4829a679b9506a2cce3fe054df52", "url": "https://github.com/EnigmaWU/MyCaTDD/blob/1eb6433f746f4829a679b9506a2cce3fe054df52/.github/prompts/TEST_reviewDesignTestsSkeleton.prompt.md", "key": "EnigmaWU/MyCaTDD/.github/prompts/TEST_reviewDesignTestsSkeleton.prompt.md" } } }

TEST_reviewDesignTestsSkeleton

About

TEST_reviewDesignTestsSkeleton

Source Command

Method Source of Truth

Execution Rules

Use it

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

Manifest

Reviews