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.

plan:adr - Prompt - OpenSmartRoute

Name: plan:adr
Author: helalifaker

Prompt file imported from helalifaker/budfin (.codex/prompts/plan.adr.md). Copyright stays with the author.

Parse the argument:

decision-title: the decision title in quotes (e.g., "Use @react-pdf/renderer instead of Puppeteer")

If the argument is missing, ask the user: "What is the title of the architectural decision you want to record?"

Step 1: Find Next ADR Number

ls docs/adr/ 2>/dev/null | grep -E "^ADR-[0-9]+" | sort | tail -1

Increment the highest number by 1. If no ADRs exist, start at ADR-001.

Format: zero-padded 3 digits (e.g., ADR-018).

Derive the slug: lowercase kebab-case of decision-title. Example: "Use @react-pdf/renderer instead of Puppeteer" → use-react-pdf-renderer-instead-of-puppeteer

Step 2: Gather ADR Content

Ask the user for each section in order. Wait for response before proceeding to the next.

Section 1: Context "Describe the situation that led to this decision — what problem were you solving? (2-5 sentences)"

Section 2: Decision "State the decision clearly. Start with 'We will...' (1-3 sentences)"

Section 3: Consequences — Positive "List the positive outcomes of this decision (bullet points)"

Section 4: Consequences — Negative "List the negative outcomes or trade-offs (bullet points)"

Section 5: Consequences — Neutral "List any neutral observations (bullet points, or press Enter to skip)"

Section 6: Alternatives Considered "List the alternatives you considered and why you rejected them (table format or bullet points)"

After each section, display the content and ask: "Is this correct? (yes to continue / no to redo)"

Step 3: Create the ADR File

mkdir -p docs/adr

Use the template at .claude/workflow/templates/adr.md. Create the file at: docs/adr/ADR-[NNN]-[slug].md

Pre-fill all fields:

ADR number and title from arguments
Date: today's date (YYYY-MM-DD)
Status: Accepted
All sections from user input

Step 4: Link in Decisions Log

Read docs/tdd/09_decisions_log.md. Find the ADR table and add a new row:

| ADR-[NNN] | [Decision title] | Accepted | YYYY-MM-DD |

If the decisions log does not have a table, create a new entry in the existing format.

Step 5: Commit the ADR

git add docs/adr/ADR-[NNN]-[slug].md docs/tdd/09_decisions_log.md
git commit -m "docs(adr): add ADR-[NNN] — [decision title]"

Step 6: Confirm

Display:

ADR recorded: docs/adr/ADR-[NNN]-[slug].md
Linked in: docs/tdd/09_decisions_log.md
Committed: docs(adr): add ADR-[NNN] — [decision title]

Error Handling

If the ADR template is missing at .claude/workflow/templates/adr.md: Create a minimal ADR with the standard sections (Context, Decision, Consequences, Alternatives). Do not fail silently — warn the user that the template was missing.

Install plan:adr 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.

Parse the argument: - `decision-title`: the decision title in quotes (e.g., "Use @react-pdf/renderer instead of Puppeteer") If the argument is missing, ask the user: "What is the title of the architectural decision you want to record?" ## Step 1: Find Next ADR Number ```bash ls docs/adr/ 2>/dev/null | grep -E "^ADR-[0-9]+" | sort | tail -1 ``` Increment the highest number by 1. If no ADRs exist, start at ADR-001. Format: zero-padded 3 digits (e.g., ADR-018). Derive the slug: lowercase kebab-case of decision-title. Example: "Use @react-pdf/renderer instead of Puppeteer" → `use-react-pdf-renderer-instead-of-puppeteer` ## Step 2: Gather ADR Content Ask the user for each section in order. Wait for response before proceeding to the next. **Section 1: Context** "Describe the situation that led to this decision — what problem were you solving? (2-5 sentences)" **Section 2: Decision** "State the decision clearly. Start with 'We will...' (1-3 sentences)" **Section 3: Consequences — Positive** "List the positive outcomes of this decision (bullet points)" **Section 4: Consequences — Negative** "List the negative outcomes or trade-offs (bullet points)" **Section 5: Consequences — Neutral** "List any neutral observations (bullet points, or press Enter to skip)" **Section 6: Alternatives Considered** "List the alternatives you considered and why you rejected them (table format or bullet points)" After each section, display the content and ask: "Is this correct? (yes to continue / no to redo)" ## Step 3: Create the ADR File ```bash mkdir -p docs/adr ``` Use the template at `.claude/workflow/templates/adr.md`. Create the file at: `docs/adr/ADR-[NNN]-[slug].md` Pre-fill all fields: - ADR number and title from arguments - Date: today's date (YYYY-MM-DD) - Status: Accepted - All sections from user input ## Step 4: Link in Decisions Log Read `docs/tdd/09_decisions_log.md`. Find the ADR table and add a new row: ```markdown | ADR-[NNN] | [Decision title] | Accepted | YYYY-MM-DD | ``` If the decisions log does not have a table, create a new entry in the existing format. ## Step 5: Commit the ADR ```bash git add docs/adr/ADR-[NNN]-[slug].md docs/tdd/09_decisions_log.md git commit -m "docs(adr): add ADR-[NNN] — [decision title]" ``` ## Step 6: Confirm Display: ``` ADR recorded: docs/adr/ADR-[NNN]-[slug].md Linked in: docs/tdd/09_decisions_log.md Committed: docs(adr): add ADR-[NNN] — [decision title] ``` ## Error Handling If the ADR template is missing at `.claude/workflow/templates/adr.md`: Create a minimal ADR with the standard sections (Context, Decision, Consequences, Alternatives). Do not fail silently — warn the user that the template was missing.

{ "prompt": "Parse the argument:\n\n- `decision-title`: the decision title in quotes (e.g., \"Use @react-pdf/renderer instead of Puppeteer\")\n\nIf the argument is missing, ask the user: \"What is the title of the architectural decision you want to record?\"\n\n## Step 1: Find Next ADR Number\n\n```bash\nls docs/adr/ 2>/dev/null | grep -E \"^ADR-[0-9]+\" | sort | tail -1\n```\n\nIncrement the highest number by 1. If no ADRs exist, start at ADR-001.\n\nFormat: zero-padded 3 digits (e.g., ADR-018).\n\nDerive the slug: lowercase kebab-case of decision-title.\nExample: \"Use @react-pdf/renderer instead of Puppeteer\" → `use-react-pdf-renderer-instead-of-puppeteer`\n\n## Step 2: Gather ADR Content\n\nAsk the user for each section in order. Wait for response before proceeding to the next.\n\n**Section 1: Context**\n\"Describe the situation that led to this decision — what problem were you solving? (2-5 sentences)\"\n\n**Section 2: Decision**\n\"State the decision clearly. Start with 'We will...' (1-3 sentences)\"\n\n**Section 3: Consequences — Positive**\n\"List the positive outcomes of this decision (bullet points)\"\n\n**Section 4: Consequences — Negative**\n\"List the negative outcomes or trade-offs (bullet points)\"\n\n**Section 5: Consequences — Neutral**\n\"List any neutral observations (bullet points, or press Enter to skip)\"\n\n**Section 6: Alternatives Considered**\n\"List the alternatives you considered and why you rejected them (table format or bullet points)\"\n\nAfter each section, display the content and ask: \"Is this correct? (yes to continue / no to redo)\"\n\n## Step 3: Create the ADR File\n\n```bash\nmkdir -p docs/adr\n```\n\nUse the template at `.claude/workflow/templates/adr.md`. Create the file at:\n`docs/adr/ADR-[NNN]-[slug].md`\n\nPre-fill all fields:\n\n- ADR number and title from arguments\n- Date: today's date (YYYY-MM-DD)\n- Status: Accepted\n- All sections from user input\n\n## Step 4: Link in Decisions Log\n\nRead `docs/tdd/09_decisions_log.md`. Find the ADR table and add a new row:\n\n```markdown\n| ADR-[NNN] | [Decision title] | Accepted | YYYY-MM-DD |\n```\n\nIf the decisions log does not have a table, create a new entry in the existing format.\n\n## Step 5: Commit the ADR\n\n```bash\ngit add docs/adr/ADR-[NNN]-[slug].md docs/tdd/09_decisions_log.md\ngit commit -m \"docs(adr): add ADR-[NNN] — [decision title]\"\n```\n\n## Step 6: Confirm\n\nDisplay:\n\n```\nADR recorded: docs/adr/ADR-[NNN]-[slug].md\nLinked in: docs/tdd/09_decisions_log.md\nCommitted: docs(adr): add ADR-[NNN] — [decision title]\n```\n\n## Error Handling\n\nIf the ADR template is missing at `.claude/workflow/templates/adr.md`:\nCreate a minimal ADR with the standard sections (Context, Decision, Consequences, Alternatives).\nDo not fail silently — warn the user that the template was missing.", "variables": [], "notes": "Record an architectural decision for BudFin. Prompts for context, decision, consequences, and alternatives. Saves to docs/adr/ADR-NNN-<slug>.md and links in docs/tdd/09_decisions_log.md. Commits the ADR. Available in any phase. Usage - /plan:adr \"[decision title]\" Tools: Read, Write, Edit, Bash. Arguments: \"[decision title]\".", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/helalifaker/budfin", "path": ".codex/prompts/plan.adr.md", "ref": "0ae459d12324d9c929baa7b09f783f5bc53911c6", "url": "https://github.com/helalifaker/budfin/blob/0ae459d12324d9c929baa7b09f783f5bc53911c6/.codex/prompts/plan.adr.md", "key": "helalifaker/budfin/.codex/prompts/plan.adr.md" } } }

plan:adr

About

Step 1: Find Next ADR Number

Step 2: Gather ADR Content

Step 3: Create the ADR File

Step 4: Link in Decisions Log

Step 5: Commit the ADR

Step 6: Confirm

Error Handling

Install plan:adr 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