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.

orch-change-feature - Skill

Name: orch-change-feature
Author: affaan-m

Imported from affaan-m/ecc (skills/orch-change-feature/SKILL.md) via skills.sh. Install upstream with npx skills add affaan-m/ecc --skill orch-change-feature. Copyright stays with the author.

orch-change-feature

Actor · action · target: orch · change · feature. Thin wrapper over the shared engine in orch-pipeline.

When to Use

An existing feature works, but the desired behavior is different ("change", "adjust", "make it also …", "instead of X do Y").
Distinguish from siblings:
- not broken → not orch-fix-defect (no bug to reproduce).
- not new → not orch-add-feature (the capability already exists).

Operation settings

Default size floor: small — most tweaks are a function or two.
Phase mask: 0 → (1 only if the new behavior needs research) → light 2 → 4 → 5 → 6.
First move (phase 4): update the existing tests to express the new desired behavior, then change the implementation until they pass. Changing the tests first is what separates a tweak from a fix.

How It Works

Run the orch-pipeline engine with the settings above.
Keep the plan light — only standard+ size warrants the full planner pass.
Stop at Gate 1 (plan / changed-test approval) and Gate 2 (pre-commit).
Add security-reviewer if the change touches a security trigger.

Example

orch-change-feature: make nws-poller alert at 2 warnings instead of 3
→ update threshold tests to new spec → change impl to green
→ code-review → commit  [GATE 2: confirm]

Install orch-change-feature 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.

{ "ocm": "1", "id": "affaan-m-ecc-orch-change-feature", "kind": "skill", "name": "orch-change-feature", "description": "Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.", "publisher": "affaan-m", "version": "1.0.0", "capabilities": { "domains": [ "coding", "observability" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/affaan-m/ecc", "path": "skills/orch-change-feature/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/affaan-m/ecc/orch-change-feature", "key": "affaan-m/ecc/skills/orch-change-feature/SKILL.md" } }, "instructions": "# orch-change-feature\n\nActor · action · target: **orch · change · feature**. Thin wrapper over the\nshared engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).\n\n## When to Use\n\n- An existing feature **works**, but the desired behavior is different (\"change\",\n \"adjust\", \"make it also …\", \"instead of X do Y\").\n- Distinguish from siblings:\n - **not** broken → not `orch-fix-defect` (no bug to reproduce).\n - **not** new → not `orch-add-feature` (the capability already exists).\n\n## Operation settings\n\n- **Default size floor:** small — most tweaks are a function or two.\n- **Phase mask:** 0 → (1 ", "cost": { "context_tokens": 343 } }

orch-change-feature

About

orch-change-feature

When to Use

Operation settings

How It Works

Example

Use it

Install orch-change-feature 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