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.

adr-review - Prompt - OpenSmartRoute

Name: adr-review
Author: achimdehnert

Prompt file imported from achimdehnert/platform (.windsurf/workflows/adr-review.md). Copyright stays with the author.

ADR Review Workflow

Trigger

User says: /adr-review ADR-[NNN] or "Review ADR-[NNN]" or "Reviewe ADR-[NNN]"

Step 1: Load the ADR

Read the ADR file from docs/adr/ADR-[NNN]-*.md in the platform repo (or the relevant service repo).

Also load the review checklist: platform/docs/templates/adr-review-checklist.md

Step 2: Run through all 8 checklist categories

Work through each category systematically:

MADR 4.0 Compliance — frontmatter (incl. implementation_status per ADR-138), title, sections, Confirmation
Platform Infrastructure Specifics — server IP, SSH, registry, ports, Nginx
CI/CD & Docker Conventions — Dockerfile location, compose, health checks (NOT in Dockerfile!), pipeline
Database & Migration Safety — Expand-Contract, tenant_id, shared DB risk
Security & Secrets — no hardcoded secrets, SOPS, org-level secrets
Architectural Consistency — service layer, no ADR contradictions, Guardian compatibility
Open Questions & Deferred Decisions — all open questions addressed
Modern Platform Patterns — infra-deploy, Multi-Tenancy, Content Store, catalog-info.yaml, Drift-Detector, Runner labels, Temporal (nur wenn relevant)
ADR-138 Implementation Tracking — implementation_status in frontmatter (required for Accepted ADRs), implementation_evidence if status is partial/implemented/verified, INDEX.md Impl column matches frontmatter
Glossar & Lesbarkeit — Glossar-Abschnitt vorhanden? Alle Abkürzungen/Fachbegriffe erklärt? Alphabetisch sortiert? Erläuterungen kontextbezogen (nicht nur Übersetzung)? Zielgruppe: Fachpersonal ohne IT-Hintergrund.

For each check: mark ✅ Pass, ⚠️ Minor issue, or ❌ Fail with a brief note.

Step 3: Output the review report

## 🔍 ADR Review: ADR-[NNN] — [Title]

### 1. MADR 4.0 Compliance
✅ 1.1 YAML frontmatter present
✅ 1.2 Title is a decision statement
⚠️ 1.5 Only 2 options considered — recommend adding ≥ 1 more
...

### 2. Platform Infrastructure Specifics
✅ 2.1 Server IP correct
❌ 2.3 StrictHostKeyChecking=no found in deploy-service.yml line 42 — replace with ssh-keyscan
...

[Continue for all 8 categories]

---

### 📊 Scoring

| Category | Score | Notes |
|----------|-------|-------|
| MADR 4.0 compliance | 4/5 | Missing Confirmation subsection |
| Platform Infrastructure Specifics | 5/5 | |
| CI/CD & Docker Conventions | 5/5 | |
| Database & Migration Safety | 5/5 | |
| Security & Secrets | 3/5 | StrictHostKeyChecking=no must be fixed |
| Architectural Consistency | 5/5 | |
| Open Questions | 4/5 | |
| Modern Platform Patterns | 5/5 | n/a for this ADR |
| **Overall** | **4.5/5** | |

---

### ✅ Stärken
- [List positives]

### ⚠️ Verbesserungsvorschläge
- [List minor improvements]

### ❌ Kritische Punkte
- [List blockers — must fix before Accept]

---

### 🎯 Empfehlung
[Accept / Accept with changes / Reject]

Soll ich die Änderungen direkt anwenden? [Ja/Nein]

Step 3.5: ADR-138 Compliance Quick-Check

Automatically verify:

Frontmatter field: Does the ADR have implementation_status in its YAML frontmatter?
- If missing and status is Accepted: ❌ BLOCK — add implementation_status: none (or appropriate value)
- If missing and status is Proposed: ⚠️ SUGGEST — add implementation_status: none
- If missing and status is Deprecated/Superseded/Archived: skip (not applicable)
Evidence field: If implementation_status is partial, implemented, or verified, does implementation_evidence exist with at least one entry?
INDEX.md sync: Does the Impl column in INDEX.md match the frontmatter value?
- none → ⬜, partial → 🔶, implemented → ✅, verified → ✅✅

Step 4: Apply fixes (if user confirms)

If user says "Ja" or "apply" or "fix it":

Apply all ❌ critical fixes directly to the ADR file
Apply ⚠️ minor improvements if user confirms
Update ADR frontmatter: amended: [today's date]
If review outcome is Accept: update platform/docs/adr/INDEX.md — Status Proposed → Accepted
If implementation_status was missing: add it to frontmatter and update INDEX.md Impl column
Push to GitHub with commit message: fix(ADR-[NNN]): address review findings — [summary of changes]

Step 5: Update migration tracking (if applicable)

If the ADR has a migration tracking table (§4 or §5 pattern from ADR-021):

Check if any items can be marked as done based on current repo state
Suggest updates to the tracking table

Reference

Checklist: platform/docs/templates/adr-review-checklist.md (v2.0)
ADR Index: platform/docs/adr/INDEX.md
MADR 4.0: https://adr.github.io/madr/
Modern Platform Patterns: ADR-059, ADR-062, ADR-072, ADR-075, ADR-077
Implementation Tracking: ADR-138 (lifecycle: none → partial → implemented → verified)

Install adr-review 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.

# ADR Review Workflow ## Trigger User says: `/adr-review ADR-[NNN]` or "Review ADR-[NNN]" or "Reviewe ADR-[NNN]" --- ## Step 1: Load the ADR Read the ADR file from `docs/adr/ADR-[NNN]-*.md` in the `platform` repo (or the relevant service repo). Also load the review checklist: `platform/docs/templates/adr-review-checklist.md` --- ## Step 2: Run through all 8 checklist categories Work through each category systematically: 1. **MADR 4.0 Compliance** — frontmatter (incl. `implementation_status` per ADR-138), title, sections, Confirmation 2. **Platform Infrastructure Specifics** — server IP, SSH, registry, ports, Nginx 3. **CI/CD & Docker Conventions** — Dockerfile location, compose, health checks (NOT in Dockerfile!), pipeline 4. **Database & Migration Safety** — Expand-Contract, tenant_id, shared DB risk 5. **Security & Secrets** — no hardcoded secrets, SOPS, org-level secrets 6. **Architectural Consistency** — service layer, no ADR contradictions, Guardian compatibility 7. **Open Questions & Deferred Decisions** — all open questions addressed 8. **Modern Platform Patterns** — infra-deploy, Multi-Tenancy, Content Store, catalog-info.yaml, Drift-Detector, Runner labels, Temporal (nur wenn relevant) 9. **ADR-138 Implementation Tracking** — `implementation_status` in frontmatter (required for Accepted ADRs), `implementation_evidence` if status is partial/implemented/verified, INDEX.md Impl column matches frontmatter 10. **Glossar & Lesbarkeit** — Glossar-Abschnitt vorhanden? Alle Abkürzungen/Fachbegriffe erklärt? Alphabetisch sortiert? Erläuterungen kontextbezogen (nicht nur Übersetzung)? Zielgruppe: Fachpersonal ohne IT-Hintergrund. For each check: mark ✅ Pass, ⚠️ Minor issue, or ❌ Fail with a brief note. --- ## Step 3: Output the review report ```text ## 🔍 ADR Review: ADR-[NNN] — [Title] ### 1. MADR 4.0 Compliance ✅ 1.1 YAML frontmatter present ✅ 1.2 Title is a decision statement ⚠️ 1.5 Only 2 options considered — recommend adding ≥ 1 more ... ### 2. Platform Infrastructure Specifics ✅ 2.1 Server IP correct ❌ 2.3 StrictHostKeyChecking=no found in deploy-service.yml line 42 — replace with ssh-keyscan ... [Continue for all 8 categories] --- ### 📊 Scoring | Category | Score | Notes | |----------|-------|-------| | MADR 4.0 compliance | 4/5 | Missing Confirmation subsection | | Platform Infrastructure Specifics | 5/5 | | | CI/CD & Docker Conventions | 5/5 | | | Database & Migration Safety | 5/5 | | | Security & Secrets | 3/5 | StrictHostKeyChecking=no must be fixed | | Architectural Consistency | 5/5 | | | Open Questions | 4/5 | | | Modern Platform Patterns | 5/5 | n/a for this ADR | | **Overall** | **4.5/5** | | --- ### ✅ Stärken - [List positives] ### ⚠️ Verbesserungsvorschläge - [List minor improvements] ### ❌ Kritische Punkte - [List blockers — must fix before Accept] --- ### 🎯 Empfehlung [Accept / Accept with changes / Reject] Soll ich die Änderungen direkt anwenden? [Ja/Nein] ``` --- ## Step 3.5: ADR-138 Compliance Quick-Check Automatically verify: 1. **Frontmatter field**: Does the ADR have `implementation_status` in its YAML frontmatter? - If missing and status is `Accepted`: ❌ BLOCK — add `implementation_status: none` (or appropriate value) - If missing and status is `Proposed`: ⚠️ SUGGEST — add `implementation_status: none` - If missing and status is `Deprecated`/`Superseded`/`Archived`: skip (not applicable) 2. **Evidence field**: If `implementation_status` is `partial`, `implemented`, or `verified`, does `implementation_evidence` exist with at least one entry? 3. **INDEX.md sync**: Does the Impl column in INDEX.md match the frontmatter value? - `none` → ⬜, `partial` → 🔶, `implemented` → ✅, `verified` → ✅✅ --- ## Step 4: Apply fixes (if user confirms) If user says "Ja" or "apply" or "fix it": 1. Apply all ❌ critical fixes directly to the ADR file 2. Apply ⚠️ minor improvements if user confirms 3. Update ADR frontmatter: `amended: [today's date]` 4. If review outcome is **Accept**: update `platform/docs/adr/INDEX.md` — Status `Proposed` → `Accepted` 5. If `implementation_status` was missing: add it to frontmatter and update INDEX.md Impl column 6. Push to GitHub with commit message: `fix(ADR-[NNN]): address review findings — [summary of changes]` --- ## Step 5: Update migration tracking (if applicable) If the ADR has a migration tracking table (§4 or §5 pattern from ADR-021): - Check if any items can be marked as done based on current repo state - Suggest updates to the tracking table --- ## Reference - Checklist: `platform/docs/templates/adr-review-checklist.md` (v2.0) - ADR Index: `platform/docs/adr/INDEX.md` - MADR 4.0: https://adr.github.io/madr/ - Modern Platform Patterns: ADR-059, ADR-062, ADR-072, ADR-075, ADR-077 - Implementation Tracking: ADR-138 (lifecycle: none → partial → implemented → verified)

{ "prompt": "# ADR Review Workflow\n\n## Trigger\n\nUser says: `/adr-review ADR-[NNN]` or \"Review ADR-[NNN]\" or \"Reviewe ADR-[NNN]\"\n\n---\n\n## Step 1: Load the ADR\n\nRead the ADR file from `docs/adr/ADR-[NNN]-*.md` in the `platform` repo (or the relevant service repo).\n\nAlso load the review checklist:\n`platform/docs/templates/adr-review-checklist.md`\n\n---\n\n## Step 2: Run through all 8 checklist categories\n\nWork through each category systematically:\n\n1. **MADR 4.0 Compliance** — frontmatter (incl. `implementation_status` per ADR-138), title, sections, Confirmation\n2. **Platform Infrastructure Specifics** — server IP, SSH, registry, ports, Nginx\n3. **CI/CD & Docker Conventions** — Dockerfile location, compose, health checks (NOT in Dockerfile!), pipeline\n4. **Database & Migration Safety** — Expand-Contract, tenant_id, shared DB risk\n5. **Security & Secrets** — no hardcoded secrets, SOPS, org-level secrets\n6. **Architectural Consistency** — service layer, no ADR contradictions, Guardian compatibility\n7. **Open Questions & Deferred Decisions** — all open questions addressed\n8. **Modern Platform Patterns** — infra-deploy, Multi-Tenancy, Content Store, catalog-info.yaml, Drift-Detector, Runner labels, Temporal (nur wenn relevant)\n9. **ADR-138 Implementation Tracking** — `implementation_status` in frontmatter (required for Accepted ADRs), `implementation_evidence` if status is partial/implemented/verified, INDEX.md Impl column matches frontmatter\n10. **Glossar & Lesbarkeit** — Glossar-Abschnitt vorhanden? Alle Abkürzungen/Fachbegriffe erklärt? Alphabetisch sortiert? Erläuterungen kontextbezogen (nicht nur Übersetzung)? Zielgruppe: Fachpersonal ohne IT-Hintergrund.\n\nFor each check: mark ✅ Pass, ⚠️ Minor issue, or ❌ Fail with a brief note.\n\n---\n\n## Step 3: Output the review report\n\n```text\n## 🔍 ADR Review: ADR-[NNN] — [Title]\n\n### 1. MADR 4.0 Compliance\n✅ 1.1 YAML frontmatter present\n✅ 1.2 Title is a decision statement\n⚠️ 1.5 Only 2 options considered — recommend adding ≥ 1 more\n...\n\n### 2. Platform Infrastructure Specifics\n✅ 2.1 Server IP correct\n❌ 2.3 StrictHostKeyChecking=no found in deploy-service.yml line 42 — replace with ssh-keyscan\n...\n\n[Continue for all 8 categories]\n\n---\n\n### 📊 Scoring\n\n| Category | Score | Notes |\n|----------|-------|-------|\n| MADR 4.0 compliance | 4/5 | Missing Confirmation subsection |\n| Platform Infrastructure Specifics | 5/5 | |\n| CI/CD & Docker Conventions | 5/5 | |\n| Database & Migration Safety | 5/5 | |\n| Security & Secrets | 3/5 | StrictHostKeyChecking=no must be fixed |\n| Architectural Consistency | 5/5 | |\n| Open Questions | 4/5 | |\n| Modern Platform Patterns | 5/5 | n/a for this ADR |\n| **Overall** | **4.5/5** | |\n\n---\n\n### ✅ Stärken\n- [List positives]\n\n### ⚠️ Verbesserungsvorschläge\n- [List minor improvements]\n\n### ❌ Kritische Punkte\n- [List blockers — must fix before Accept]\n\n---\n\n### 🎯 Empfehlung\n[Accept / Accept with changes / Reject]\n\nSoll ich die Änderungen direkt anwenden? [Ja/Nein]\n```\n\n---\n\n## Step 3.5: ADR-138 Compliance Quick-Check\n\nAutomatically verify:\n1. **Frontmatter field**: Does the ADR have `implementation_status` in its YAML frontmatter?\n - If missing and status is `Accepted`: ❌ BLOCK — add `implementation_status: none` (or appropriate value)\n - If missing and status is `Proposed`: ⚠️ SUGGEST — add `implementation_status: none`\n - If missing and status is `Deprecated`/`Superseded`/`Archived`: skip (not applicable)\n2. **Evidence field**: If `implementation_status` is `partial`, `implemented`, or `verified`, does `implementation_evidence` exist with at least one entry?\n3. **INDEX.md sync**: Does the Impl column in INDEX.md match the frontmatter value?\n - `none` → ⬜, `partial` → 🔶, `implemented` → ✅, `verified` → ✅✅\n\n---\n\n## Step 4: Apply fixes (if user confirms)\n\nIf user says \"Ja\" or \"apply\" or \"fix it\":\n\n1. Apply all ❌ critical fixes directly to the ADR file\n2. Apply ⚠️ minor improvements if user confirms\n3. Update ADR frontmatter: `amended: [today's date]`\n4. If review outcome is **Accept**: update `platform/docs/adr/INDEX.md` — Status `Proposed` → `Accepted`\n5. If `implementation_status` was missing: add it to frontmatter and update INDEX.md Impl column\n6. Push to GitHub with commit message:\n `fix(ADR-[NNN]): address review findings — [summary of changes]`\n\n---\n\n## Step 5: Update migration tracking (if applicable)\n\nIf the ADR has a migration tracking table (§4 or §5 pattern from ADR-021):\n- Check if any items can be marked as done based on current repo state\n- Suggest updates to the tracking table\n\n---\n\n## Reference\n\n- Checklist: `platform/docs/templates/adr-review-checklist.md` (v2.0)\n- ADR Index: `platform/docs/adr/INDEX.md`\n- MADR 4.0: https://adr.github.io/madr/\n- Modern Platform Patterns: ADR-059, ADR-062, ADR-072, ADR-075, ADR-077\n- Implementation Tracking: ADR-138 (lifecycle: none → partial → implemented → verified)", "variables": [], "notes": "Review an ADR against the platform-specific checklist (MADR 4.0 + infrastructure conventions + Modern Platform Patterns) Mode: read-only.", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/achimdehnert/platform", "path": ".windsurf/workflows/adr-review.md", "ref": "26ff2649c7a82cb7138376c80dd081b45f760921", "url": "https://github.com/achimdehnert/platform/blob/26ff2649c7a82cb7138376c80dd081b45f760921/.windsurf/workflows/adr-review.md", "key": "achimdehnert/platform/.windsurf/workflows/adr-review.md" } } }

adr-review

About

ADR Review Workflow

Trigger

Step 1: Load the ADR

Step 2: Run through all 8 checklist categories

Step 3: Output the review report

Step 3.5: ADR-138 Compliance Quick-Check

Step 4: Apply fixes (if user confirms)

Step 5: Update migration tracking (if applicable)

Reference

Install adr-review 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