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.

workflow:status - Prompt - OpenSmartRoute

Name: workflow:status
Author: helalifaker

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

Read .claude/workflow/STATUS.md and .claude/workflow/WORKFLOW.md.

Display the current state in this format:

=== BudFin Workflow ===

>>> NEXT: /workflow:run [N]    (Epic N: [Name] -- [ready for spec | stories needed | implementation | review])

Phase: [N] -- [NAME] | Epics: [done]/13 done
Current Epic: Epic [N] -- [Name] (#[issue-number])

Checklist for Phase [N]:
  [x] Completed item
  [ ] Remaining item

Gate: [Gate requirement text from WORKFLOW.md]

Valid: /workflow:run [N], /plan:spec [N], /fix:all, /plan:adr, /workflow:status, /workflow:advance

The >>> NEXT: line must always appear at the top of the output, prominently showing the single most useful command to run next.

Determining >>> NEXT

Phase 4 with no spec: /plan:spec [epic-N]
Phase 4 with spec but no stories: /plan:stories [epic-N]
Phase 4 with spec and stories: /workflow:run [epic-N]
Phase 5/6: /workflow:run [epic-N] (continues implementation)
Phase 7 with open PRs: /pr:drive --epic [epic-N]
Phase 7 with all PRs merged: /workflow:advance
Between Epics: /workflow:run [next-epic-N]

Valid Commands

After displaying status, show which commands are valid right now:

Phase-to-command mapping:

Phase 4: /workflow:run [epic-N], /plan:spec [epic-N], /plan:adr, /workflow:advance
Phase 5/6: /workflow:run [epic-N], /impl:story [#], /fix:all, /workflow:advance
Phase 7: /pr:drive --epic [epic-N], /pr:drive [story-#], /fix:all, /workflow:advance
Any phase: /workflow:status, /workflow:advance, /fix:all, /plan:adr

Edge Cases

After displaying status, check if all checklist items for the current phase are marked [x]. If yes, say: "All items complete. Run /workflow:advance to gate-check and move to the next phase." If no, count how many items remain and name the first incomplete one.

If .claude/workflow/STATUS.md does not exist, say: "STATUS.md not found at .claude/workflow/STATUS.md. The workflow has not been initialized."

Install workflow:status 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.

Read `.claude/workflow/STATUS.md` and `.claude/workflow/WORKFLOW.md`. Display the current state in this format: ``` === BudFin Workflow === >>> NEXT: /workflow:run [N] (Epic N: [Name] -- [ready for spec | stories needed | implementation | review]) Phase: [N] -- [NAME] | Epics: [done]/13 done Current Epic: Epic [N] -- [Name] (#[issue-number]) Checklist for Phase [N]: [x] Completed item [ ] Remaining item Gate: [Gate requirement text from WORKFLOW.md] Valid: /workflow:run [N], /plan:spec [N], /fix:all, /plan:adr, /workflow:status, /workflow:advance ``` The `>>> NEXT:` line must always appear at the top of the output, prominently showing the single most useful command to run next. ## Determining >>> NEXT - Phase 4 with no spec: `/plan:spec [epic-N]` - Phase 4 with spec but no stories: `/plan:stories [epic-N]` - Phase 4 with spec and stories: `/workflow:run [epic-N]` - Phase 5/6: `/workflow:run [epic-N]` (continues implementation) - Phase 7 with open PRs: `/pr:drive --epic [epic-N]` - Phase 7 with all PRs merged: `/workflow:advance` - Between Epics: `/workflow:run [next-epic-N]` ## Valid Commands After displaying status, show which commands are valid right now: Phase-to-command mapping: - Phase 4: `/workflow:run [epic-N]`, `/plan:spec [epic-N]`, `/plan:adr`, `/workflow:advance` - Phase 5/6: `/workflow:run [epic-N]`, `/impl:story [#]`, `/fix:all`, `/workflow:advance` - Phase 7: `/pr:drive --epic [epic-N]`, `/pr:drive [story-#]`, `/fix:all`, `/workflow:advance` - Any phase: `/workflow:status`, `/workflow:advance`, `/fix:all`, `/plan:adr` ## Edge Cases After displaying status, check if all checklist items for the current phase are marked `[x]`. If yes, say: "All items complete. Run `/workflow:advance` to gate-check and move to the next phase." If no, count how many items remain and name the first incomplete one. If `.claude/workflow/STATUS.md` does not exist, say: "STATUS.md not found at `.claude/workflow/STATUS.md`. The workflow has not been initialized."

{ "prompt": "Read `.claude/workflow/STATUS.md` and `.claude/workflow/WORKFLOW.md`.\n\nDisplay the current state in this format:\n\n```\n=== BudFin Workflow ===\n\n>>> NEXT: /workflow:run [N] (Epic N: [Name] -- [ready for spec | stories needed | implementation | review])\n\nPhase: [N] -- [NAME] | Epics: [done]/13 done\nCurrent Epic: Epic [N] -- [Name] (#[issue-number])\n\nChecklist for Phase [N]:\n [x] Completed item\n [ ] Remaining item\n\nGate: [Gate requirement text from WORKFLOW.md]\n\nValid: /workflow:run [N], /plan:spec [N], /fix:all, /plan:adr, /workflow:status, /workflow:advance\n```\n\nThe `>>> NEXT:` line must always appear at the top of the output, prominently showing the single most useful command to run next.\n\n## Determining >>> NEXT\n\n- Phase 4 with no spec: `/plan:spec [epic-N]`\n- Phase 4 with spec but no stories: `/plan:stories [epic-N]`\n- Phase 4 with spec and stories: `/workflow:run [epic-N]`\n- Phase 5/6: `/workflow:run [epic-N]` (continues implementation)\n- Phase 7 with open PRs: `/pr:drive --epic [epic-N]`\n- Phase 7 with all PRs merged: `/workflow:advance`\n- Between Epics: `/workflow:run [next-epic-N]`\n\n## Valid Commands\n\nAfter displaying status, show which commands are valid right now:\n\nPhase-to-command mapping:\n\n- Phase 4: `/workflow:run [epic-N]`, `/plan:spec [epic-N]`, `/plan:adr`, `/workflow:advance`\n- Phase 5/6: `/workflow:run [epic-N]`, `/impl:story [#]`, `/fix:all`, `/workflow:advance`\n- Phase 7: `/pr:drive --epic [epic-N]`, `/pr:drive [story-#]`, `/fix:all`, `/workflow:advance`\n- Any phase: `/workflow:status`, `/workflow:advance`, `/fix:all`, `/plan:adr`\n\n## Edge Cases\n\nAfter displaying status, check if all checklist items for the current phase are marked `[x]`.\nIf yes, say: \"All items complete. Run `/workflow:advance` to gate-check and move to the next phase.\"\nIf no, count how many items remain and name the first incomplete one.\n\nIf `.claude/workflow/STATUS.md` does not exist, say:\n\"STATUS.md not found at `.claude/workflow/STATUS.md`. The workflow has not been initialized.\"", "variables": [], "notes": "Show the current BudFin workflow phase, checklist progress, and next gate requirement. Tools: Read, Bash.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/helalifaker/budfin", "path": ".codex/prompts/workflow.status.md", "ref": "0ae459d12324d9c929baa7b09f783f5bc53911c6", "url": "https://github.com/helalifaker/budfin/blob/0ae459d12324d9c929baa7b09f783f5bc53911c6/.codex/prompts/workflow.status.md", "key": "helalifaker/budfin/.codex/prompts/workflow.status.md" } } }

workflow:status

About

Determining >>> NEXT

Valid Commands

Edge Cases

Install workflow:status 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