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.

bmad-retrospective - Skill

Imported from bmad-code-org/bmad-method (skills/bmad-retrospective/SKILL.md) via skills.sh. Install upstream with npx skills add bmad-code-org/bmad-method --skill bmad-retrospective. Copyright stays with the author.

name: bmad-retrospective description: 'Review a finished epic folder in the ticket tree against the evidence it left behind — the epic file, each ticket's story file and plan, diffs, commits — and produce a retrospective with sourced findings, action items, and an acceptance decision. Use when the user says "run a retrospective" or "lets retro the epic [epic]". Supports -H/--headless'

Run the following command exactly once without changing the current working directory.

Replace {project-root} with the nearest folder containing _bmad/, from the working directory upward. Replace {skill-root} with the absolute path to this skill's directory.

uv run --no-cache "{project-root}/_bmad/scripts/render_skill.py" --project-root "{project-root}" --skill "{skill-root}"

The command prints the skill's workflow: follow it. HALT: <reason>: report the reason and stop.
If the script does not exist, BMad is not set up in this project yet. Offer to set it up using bmad skill, then run the command again. If you do not have the bmad skill, offer to install it first.
On any other output or failure, including uv being unavailable, report the command output and stop. Do not run any workflow source directly.

Install bmad-retrospective 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.

bmad-retrospective

About

Install bmad-retrospective 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