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.

impl:epic - Prompt - OpenSmartRoute

Name: impl:epic
Author: helalifaker

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

Internal command. Called by /workflow:run automatically.

Parse the argument:

epic-issue-number: integer GitHub issue number of the parent Epic (e.g., 5)

If missing, ask the user: "Which Epic issue number should I implement?"

Step 1 — Phase Gate Check

Read .claude/workflow/STATUS.md.

If Phase < 5:

Error: /impl:epic requires Phase 5 (TDD RED) or Phase 6 (IMPLEMENT).
Current phase is [N] — [NAME].

Run /workflow:advance to gate-check your way to Phase 5.
Or run /plan:spec [epic-N] if the spec hasn't been written yet.

Then stop.

Step 2 — Load All Stories

gh issue list --label "story" --json number,title,body --state open

Filter to stories where the body contains **Parent Epic**: #$EPIC_NUMBER.

Sort by dependency order: parse the **Depends On**: field in each story body. Build a dependency graph and topologically sort. Stories with no dependencies come first.

Display the ordered list:

Stories for Epic #$EPIC_NUMBER:
  1. Story #N — [title] (no dependencies)
  2. Story #N — [title] (depends on Story #N)
  3. Story #N — [title] (depends on Story #N)

Ask: "Ready to implement [N] stories in this order? (yes to start / no to abort)"

Step 3 — Implement Stories in Order

For each story in the sorted order:

Announce:

─────────────────────────────────────────
Implementing story [X/N]: #[number] — [title]
─────────────────────────────────────────

Execute the full impl:story workflow inline (not as a slash command call):
- Context gathering (issue + epic + spec)
- Skill invocation (budfin-workflow)
- Spawn story-orchestrator swarm
- TDD RED phase
- TDD GREEN phase
- Parallel review phase
- Outcome determination
On PASS:
- Record: Story #N PASSED — PR #N created
- Immediately continue to next story

On FAIL (any Blocker):

Output the blocker list with suggested fix commands
PAUSE implementation — do NOT continue to the next story automatically

Print:

Story #$STORY_NUMBER BLOCKED — [N] blockers found.

Resolve the blockers above, then either:
  /fix:lint / /fix:types / /fix:tests / /fix:security / /fix:precision

After resolving, resume: /impl:story $STORY_NUMBER
Then continue with the next story manually or re-run: /impl:epic $EPIC_NUMBER

Stop

Step 4 — Epic Completion Summary

When all stories pass, output:

═══════════════════════════════════════════
Epic #$EPIC_NUMBER Implementation Complete
═══════════════════════════════════════════

Stories merged:
  ✓ Story #N — [title] (PR #N)
  ✓ Story #N — [title] (PR #N)
  ...

All [N] stories complete. All PRs open and approved.

Next steps:
  Review each PR and merge in dependency order.
  Then: /workflow:advance

Error Handling

If no stories are found for this Epic:

No open stories found with Parent Epic #$EPIC_NUMBER.

Either stories haven't been created yet (run /plan:stories $EPIC_NUMBER first)
or all stories are already closed (check GitHub Issues).

Install impl:epic 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.

> **Internal command.** Called by `/workflow:run` automatically. Parse the argument: - `epic-issue-number`: integer GitHub issue number of the parent Epic (e.g., 5) If missing, ask the user: "Which Epic issue number should I implement?" ## Step 1 — Phase Gate Check Read `.claude/workflow/STATUS.md`. If Phase < 5: ``` Error: /impl:epic requires Phase 5 (TDD RED) or Phase 6 (IMPLEMENT). Current phase is [N] — [NAME]. Run /workflow:advance to gate-check your way to Phase 5. Or run /plan:spec [epic-N] if the spec hasn't been written yet. ``` Then stop. ## Step 2 — Load All Stories ```bash gh issue list --label "story" --json number,title,body --state open ``` Filter to stories where the body contains `**Parent Epic**: #$EPIC_NUMBER`. Sort by dependency order: parse the `**Depends On**:` field in each story body. Build a dependency graph and topologically sort. Stories with no dependencies come first. Display the ordered list: ``` Stories for Epic #$EPIC_NUMBER: 1. Story #N — [title] (no dependencies) 2. Story #N — [title] (depends on Story #N) 3. Story #N — [title] (depends on Story #N) ``` Ask: "Ready to implement [N] stories in this order? (yes to start / no to abort)" ## Step 3 — Implement Stories in Order For each story in the sorted order: 1. Announce: ``` ───────────────────────────────────────── Implementing story [X/N]: #[number] — [title] ───────────────────────────────────────── ``` 2. Execute the full `impl:story` workflow inline (not as a slash command call): - Context gathering (issue + epic + spec) - Skill invocation (`budfin-workflow`) - Spawn story-orchestrator swarm - TDD RED phase - TDD GREEN phase - Parallel review phase - Outcome determination 3. On PASS: - Record: `Story #N PASSED — PR #N created` - Immediately continue to next story 4. On FAIL (any Blocker): - Output the blocker list with suggested fix commands - PAUSE implementation — do NOT continue to the next story automatically - Print: ``` Story #$STORY_NUMBER BLOCKED — [N] blockers found. Resolve the blockers above, then either: /fix:lint / /fix:types / /fix:tests / /fix:security / /fix:precision After resolving, resume: /impl:story $STORY_NUMBER Then continue with the next story manually or re-run: /impl:epic $EPIC_NUMBER ``` - Stop ## Step 4 — Epic Completion Summary When all stories pass, output: ``` ═══════════════════════════════════════════ Epic #$EPIC_NUMBER Implementation Complete ═══════════════════════════════════════════ Stories merged: ✓ Story #N — [title] (PR #N) ✓ Story #N — [title] (PR #N) ... All [N] stories complete. All PRs open and approved. Next steps: Review each PR and merge in dependency order. Then: /workflow:advance ``` ## Error Handling If no stories are found for this Epic: ``` No open stories found with Parent Epic #$EPIC_NUMBER. Either stories haven't been created yet (run /plan:stories $EPIC_NUMBER first) or all stories are already closed (check GitHub Issues). ```

{ "prompt": "> **Internal command.** Called by `/workflow:run` automatically.\n\nParse the argument:\n\n- `epic-issue-number`: integer GitHub issue number of the parent Epic (e.g., 5)\n\nIf missing, ask the user: \"Which Epic issue number should I implement?\"\n\n## Step 1 — Phase Gate Check\n\nRead `.claude/workflow/STATUS.md`.\n\nIf Phase < 5:\n\n```\nError: /impl:epic requires Phase 5 (TDD RED) or Phase 6 (IMPLEMENT).\nCurrent phase is [N] — [NAME].\n\nRun /workflow:advance to gate-check your way to Phase 5.\nOr run /plan:spec [epic-N] if the spec hasn't been written yet.\n```\n\nThen stop.\n\n## Step 2 — Load All Stories\n\n```bash\ngh issue list --label \"story\" --json number,title,body --state open\n```\n\nFilter to stories where the body contains `**Parent Epic**: #$EPIC_NUMBER`.\n\nSort by dependency order: parse the `**Depends On**:` field in each story body.\nBuild a dependency graph and topologically sort. Stories with no dependencies come first.\n\nDisplay the ordered list:\n\n```\nStories for Epic #$EPIC_NUMBER:\n 1. Story #N — [title] (no dependencies)\n 2. Story #N — [title] (depends on Story #N)\n 3. Story #N — [title] (depends on Story #N)\n```\n\nAsk: \"Ready to implement [N] stories in this order? (yes to start / no to abort)\"\n\n## Step 3 — Implement Stories in Order\n\nFor each story in the sorted order:\n\n1. Announce:\n\n ```\n ─────────────────────────────────────────\n Implementing story [X/N]: #[number] — [title]\n ─────────────────────────────────────────\n ```\n\n2. Execute the full `impl:story` workflow inline (not as a slash command call):\n - Context gathering (issue + epic + spec)\n - Skill invocation (`budfin-workflow`)\n - Spawn story-orchestrator swarm\n - TDD RED phase\n - TDD GREEN phase\n - Parallel review phase\n - Outcome determination\n\n3. On PASS:\n - Record: `Story #N PASSED — PR #N created`\n - Immediately continue to next story\n\n4. On FAIL (any Blocker):\n - Output the blocker list with suggested fix commands\n - PAUSE implementation — do NOT continue to the next story automatically\n - Print:\n\n ```\n Story #$STORY_NUMBER BLOCKED — [N] blockers found.\n\n Resolve the blockers above, then either:\n /fix:lint / /fix:types / /fix:tests / /fix:security / /fix:precision\n\n After resolving, resume: /impl:story $STORY_NUMBER\n Then continue with the next story manually or re-run: /impl:epic $EPIC_NUMBER\n ```\n\n - Stop\n\n## Step 4 — Epic Completion Summary\n\nWhen all stories pass, output:\n\n```\n═══════════════════════════════════════════\nEpic #$EPIC_NUMBER Implementation Complete\n═══════════════════════════════════════════\n\nStories merged:\n ✓ Story #N — [title] (PR #N)\n ✓ Story #N — [title] (PR #N)\n ...\n\nAll [N] stories complete. All PRs open and approved.\n\nNext steps:\n Review each PR and merge in dependency order.\n Then: /workflow:advance\n```\n\n## Error Handling\n\nIf no stories are found for this Epic:\n\n```\nNo open stories found with Parent Epic #$EPIC_NUMBER.\n\nEither stories haven't been created yet (run /plan:stories $EPIC_NUMBER first)\nor all stories are already closed (check GitHub Issues).\n```", "variables": [], "notes": "Implement all stories for a BudFin Epic in dependency order. Runs impl:story logic inline for each story, pausing on blockers. Creates an Epic-level summary after all stories complete. Usage - /impl:epic [epic-issue-number] Tools: Bash, Read, Agent, TeamCreate, TaskCreate, TaskUpdate, TaskList, SendMessage. Arguments: [epic-issue-number].", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/helalifaker/budfin", "path": ".codex/prompts/impl.epic.md", "ref": "0ae459d12324d9c929baa7b09f783f5bc53911c6", "url": "https://github.com/helalifaker/budfin/blob/0ae459d12324d9c929baa7b09f783f5bc53911c6/.codex/prompts/impl.epic.md", "key": "helalifaker/budfin/.codex/prompts/impl.epic.md" } } }

impl:epic

About

Step 1 — Phase Gate Check

Step 2 — Load All Stories

Step 3 — Implement Stories in Order

Step 4 — Epic Completion Summary

Error Handling

Install impl:epic 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