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:stories - Prompt - OpenSmartRoute

Name: plan:stories
Author: helalifaker

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

Internal command. Called by /workflow:run automatically.

Parse the arguments:

epic-issue-number: the GitHub issue number of the parent Epic (e.g., 5)
--single: optional flag — if present, create only one story interactively

If epic-issue-number is missing, ask the user for it.

Step 1: Phase Guard

Read .claude/workflow/STATUS.md. If not Phase 4 — SPECIFY:

Warning: /plan:stories is a Phase 4 command. Current phase is [N] — [NAME].
Run /workflow:status to see what actions are available.

Then stop.

Step 2: Find the Feature Spec

gh issue view $EPIC_NUMBER --json number,title,body — get Epic details
Derive the spec file path from the Epic title:
- Epic title "Epic N: Feature Name" → docs/specs/epic-N/<feature-slug>.md
Read the spec file entirely

If no spec exists:

No spec found at docs/specs/epic-$EPIC_NUMBER/. Run /plan:spec $EPIC_NUMBER first.

Then stop.

Step 2.5: Extract UI/UX Context from Spec

Read the spec's ## UI/UX Specification section. Extract:

Primary UI/UX spec path: from the > Source: line (e.g., docs/ui-ux-spec/08-master-data.md)
Shell type: PlanningShell or ManagementShell (from ### Shell & Layout)
Key Components table: component name, type, and source reference (from ### Key Components)

If the UI/UX section says "N/A — backend-only epic", set UI/UX context to null and use 'N/A' for all UI/UX fields in the story template below.

Store these values for use in Step 4.

Step 3: Derive Story Breakdown (if not --single)

Use the Agent tool to launch workflow-orchestrator with the spec file and this instruction:

Analyze the feature spec at [spec-path]. Return:
1. A numbered list of stories in dependency order
2. For each story: title, dependency (which story it depends on, if any), and the AC numbers from the spec it covers
3. Flag any AC that does not map to a story (these need to be assigned)
4. For each story: which UI/UX components (from the spec's Key Components table) it involves

Wait for orchestrator to return the story breakdown before proceeding.

Step 4: Create Story Issues

Ensure the story label exists:

gh label create story --color "#0075ca" --description "Story-level task linked to an Epic" 2>/dev/null || true

For each story returned by the orchestrator (in dependency order), create a GitHub issue:

gh issue create \
  --title "Story: $STORY_TITLE" \
  --label "story" \
  --body "## Story: $STORY_TITLE

**Parent Epic**: #$EPIC_NUMBER
**Depends On**: [story title or 'none']

## Acceptance Criteria

[Copy relevant AC from the spec — AC-0N format]

- [ ] AC-0N: [criterion]

## Definition of Done

- [ ] Tests written and RED (Phase 5)
- [ ] Tests GREEN, coverage ≥ 80% (Phase 6)
- [ ] Linter passes — 0 errors, 0 warnings
- [ ] PR open and linked to this issue
- [ ] Reviewer agent: APPROVED
- [ ] QA agent: APPROVED
- [ ] Documentor agent: COMPLETE
- [ ] PR merged, this issue auto-closes

## Notes

[Any implementation constraints or technical notes from the spec relevant to this story]

## UI/UX Context

**Primary UI/UX Spec**: [path from Step 2.5, or 'N/A']
**Shell Type**: [PlanningShell / ManagementShell / N/A]
**Key Components**: [comma-separated list of component names relevant to THIS story, or 'N/A']
**Interaction Patterns**: [relevant patterns from spec for THIS story, or 'N/A']
"

After each story is created:

Display the issue number and URL
Add to the Projects board if project number is known: gh project item-add [project-number] --owner helalifaker --url [issue-url]

Step 5: --single Mode

If --single flag was passed, create only one story interactively:

Ask user for the story title
Ask user which AC from the spec this story covers
Create the issue using the template above
Display issue number and URL

Step 6: Summary

After all stories are created, display:

Stories created for Epic #$EPIC_NUMBER: [Feature Name]

| # | Story | Issue | Depends On |
|---|-------|-------|------------|
| 1 | [title] | #N | none |
| 2 | [title] | #N | Story 1 |
...

Total: [N] stories created

Next: Implement stories in order.
  /impl:story [first-story-number]

Also update .claude/workflow/STATUS.md — add story issue numbers to the feature progress table.

Install plan:stories 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 arguments: - `epic-issue-number`: the GitHub issue number of the parent Epic (e.g., 5) - `--single`: optional flag — if present, create only one story interactively If `epic-issue-number` is missing, ask the user for it. ## Step 1: Phase Guard Read `.claude/workflow/STATUS.md`. If not Phase 4 — SPECIFY: ``` Warning: /plan:stories is a Phase 4 command. Current phase is [N] — [NAME]. Run /workflow:status to see what actions are available. ``` Then stop. ## Step 2: Find the Feature Spec 1. `gh issue view $EPIC_NUMBER --json number,title,body` — get Epic details 2. Derive the spec file path from the Epic title: - Epic title "Epic N: Feature Name" → `docs/specs/epic-N/<feature-slug>.md` 3. Read the spec file entirely If no spec exists: ``` No spec found at docs/specs/epic-$EPIC_NUMBER/. Run /plan:spec $EPIC_NUMBER first. ``` Then stop. ## Step 2.5: Extract UI/UX Context from Spec Read the spec's `## UI/UX Specification` section. Extract: 1. **Primary UI/UX spec path**: from the `> Source:` line (e.g., `docs/ui-ux-spec/08-master-data.md`) 2. **Shell type**: PlanningShell or ManagementShell (from `### Shell & Layout`) 3. **Key Components table**: component name, type, and source reference (from `### Key Components`) If the UI/UX section says "N/A — backend-only epic", set UI/UX context to null and use 'N/A' for all UI/UX fields in the story template below. Store these values for use in Step 4. ## Step 3: Derive Story Breakdown (if not --single) Use the Agent tool to launch `workflow-orchestrator` with the spec file and this instruction: ``` Analyze the feature spec at [spec-path]. Return: 1. A numbered list of stories in dependency order 2. For each story: title, dependency (which story it depends on, if any), and the AC numbers from the spec it covers 3. Flag any AC that does not map to a story (these need to be assigned) 4. For each story: which UI/UX components (from the spec's Key Components table) it involves ``` Wait for orchestrator to return the story breakdown before proceeding. ## Step 4: Create Story Issues Ensure the `story` label exists: ```bash gh label create story --color "#0075ca" --description "Story-level task linked to an Epic" 2>/dev/null || true ``` For each story returned by the orchestrator (in dependency order), create a GitHub issue: ```bash gh issue create \ --title "Story: $STORY_TITLE" \ --label "story" \ --body "## Story: $STORY_TITLE **Parent Epic**: #$EPIC_NUMBER **Depends On**: [story title or 'none'] ## Acceptance Criteria [Copy relevant AC from the spec — AC-0N format] - [ ] AC-0N: [criterion] ## Definition of Done - [ ] Tests written and RED (Phase 5) - [ ] Tests GREEN, coverage ≥ 80% (Phase 6) - [ ] Linter passes — 0 errors, 0 warnings - [ ] PR open and linked to this issue - [ ] Reviewer agent: APPROVED - [ ] QA agent: APPROVED - [ ] Documentor agent: COMPLETE - [ ] PR merged, this issue auto-closes ## Notes [Any implementation constraints or technical notes from the spec relevant to this story] ## UI/UX Context **Primary UI/UX Spec**: [path from Step 2.5, or 'N/A'] **Shell Type**: [PlanningShell / ManagementShell / N/A] **Key Components**: [comma-separated list of component names relevant to THIS story, or 'N/A'] **Interaction Patterns**: [relevant patterns from spec for THIS story, or 'N/A'] " ``` After each story is created: - Display the issue number and URL - Add to the Projects board if project number is known: `gh project item-add [project-number] --owner helalifaker --url [issue-url]` ## Step 5: --single Mode If `--single` flag was passed, create only one story interactively: 1. Ask user for the story title 2. Ask user which AC from the spec this story covers 3. Create the issue using the template above 4. Display issue number and URL ## Step 6: Summary After all stories are created, display: ``` Stories created for Epic #$EPIC_NUMBER: [Feature Name] | # | Story | Issue | Depends On | |---|-------|-------|------------| | 1 | [title] | #N | none | | 2 | [title] | #N | Story 1 | ... Total: [N] stories created Next: Implement stories in order. /impl:story [first-story-number] ``` Also update `.claude/workflow/STATUS.md` — add story issue numbers to the feature progress table.

{ "prompt": "> **Internal command.** Called by `/workflow:run` automatically.\n\nParse the arguments:\n\n- `epic-issue-number`: the GitHub issue number of the parent Epic (e.g., 5)\n- `--single`: optional flag — if present, create only one story interactively\n\nIf `epic-issue-number` is missing, ask the user for it.\n\n## Step 1: Phase Guard\n\nRead `.claude/workflow/STATUS.md`. If not Phase 4 — SPECIFY:\n\n```\nWarning: /plan:stories is a Phase 4 command. Current phase is [N] — [NAME].\nRun /workflow:status to see what actions are available.\n```\n\nThen stop.\n\n## Step 2: Find the Feature Spec\n\n1. `gh issue view $EPIC_NUMBER --json number,title,body` — get Epic details\n2. Derive the spec file path from the Epic title:\n - Epic title \"Epic N: Feature Name\" → `docs/specs/epic-N/<feature-slug>.md`\n3. Read the spec file entirely\n\nIf no spec exists:\n\n```\nNo spec found at docs/specs/epic-$EPIC_NUMBER/. Run /plan:spec $EPIC_NUMBER first.\n```\n\nThen stop.\n\n## Step 2.5: Extract UI/UX Context from Spec\n\nRead the spec's `## UI/UX Specification` section. Extract:\n\n1. **Primary UI/UX spec path**: from the `> Source:` line (e.g., `docs/ui-ux-spec/08-master-data.md`)\n2. **Shell type**: PlanningShell or ManagementShell (from `### Shell & Layout`)\n3. **Key Components table**: component name, type, and source reference (from `### Key Components`)\n\nIf the UI/UX section says \"N/A — backend-only epic\", set UI/UX context to null and use 'N/A'\nfor all UI/UX fields in the story template below.\n\nStore these values for use in Step 4.\n\n## Step 3: Derive Story Breakdown (if not --single)\n\nUse the Agent tool to launch `workflow-orchestrator` with the spec file and this instruction:\n\n```\nAnalyze the feature spec at [spec-path]. Return:\n1. A numbered list of stories in dependency order\n2. For each story: title, dependency (which story it depends on, if any), and the AC numbers from the spec it covers\n3. Flag any AC that does not map to a story (these need to be assigned)\n4. For each story: which UI/UX components (from the spec's Key Components table) it involves\n```\n\nWait for orchestrator to return the story breakdown before proceeding.\n\n## Step 4: Create Story Issues\n\nEnsure the `story` label exists:\n\n```bash\ngh label create story --color \"#0075ca\" --description \"Story-level task linked to an Epic\" 2>/dev/null || true\n```\n\nFor each story returned by the orchestrator (in dependency order), create a GitHub issue:\n\n```bash\ngh issue create \\\n --title \"Story: $STORY_TITLE\" \\\n --label \"story\" \\\n --body \"## Story: $STORY_TITLE\n\n**Parent Epic**: #$EPIC_NUMBER\n**Depends On**: [story title or 'none']\n\n## Acceptance Criteria\n\n[Copy relevant AC from the spec — AC-0N format]\n\n- [ ] AC-0N: [criterion]\n\n## Definition of Done\n\n- [ ] Tests written and RED (Phase 5)\n- [ ] Tests GREEN, coverage ≥ 80% (Phase 6)\n- [ ] Linter passes — 0 errors, 0 warnings\n- [ ] PR open and linked to this issue\n- [ ] Reviewer agent: APPROVED\n- [ ] QA agent: APPROVED\n- [ ] Documentor agent: COMPLETE\n- [ ] PR merged, this issue auto-closes\n\n## Notes\n\n[Any implementation constraints or technical notes from the spec relevant to this story]\n\n## UI/UX Context\n\n**Primary UI/UX Spec**: [path from Step 2.5, or 'N/A']\n**Shell Type**: [PlanningShell / ManagementShell / N/A]\n**Key Components**: [comma-separated list of component names relevant to THIS story, or 'N/A']\n**Interaction Patterns**: [relevant patterns from spec for THIS story, or 'N/A']\n\"\n```\n\nAfter each story is created:\n\n- Display the issue number and URL\n- Add to the Projects board if project number is known:\n `gh project item-add [project-number] --owner helalifaker --url [issue-url]`\n\n## Step 5: --single Mode\n\nIf `--single` flag was passed, create only one story interactively:\n\n1. Ask user for the story title\n2. Ask user which AC from the spec this story covers\n3. Create the issue using the template above\n4. Display issue number and URL\n\n## Step 6: Summary\n\nAfter all stories are created, display:\n\n```\nStories created for Epic #$EPIC_NUMBER: [Feature Name]\n\n| # | Story | Issue | Depends On |\n|---|-------|-------|------------|\n| 1 | [title] | #N | none |\n| 2 | [title] | #N | Story 1 |\n...\n\nTotal: [N] stories created\n\nNext: Implement stories in order.\n /impl:story [first-story-number]\n```\n\nAlso update `.claude/workflow/STATUS.md` — add story issue numbers to the feature progress table.", "variables": [], "notes": "Phase 4 - Read a completed feature spec and batch-create all GitHub Story issues linked to the parent Epic. Derives dependency-ordered story breakdown via workflow-orchestrator agent. Usage - /plan:stories [epic-issue-number] [--single] Tools: Bash, Read, Agent. Arguments: [epic-issue-number] [--single].", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/helalifaker/budfin", "path": ".codex/prompts/plan.stories.md", "ref": "0ae459d12324d9c929baa7b09f783f5bc53911c6", "url": "https://github.com/helalifaker/budfin/blob/0ae459d12324d9c929baa7b09f783f5bc53911c6/.codex/prompts/plan.stories.md", "key": "helalifaker/budfin/.codex/prompts/plan.stories.md" } } }

plan:stories

About

Step 1: Phase Guard

Step 2: Find the Feature Spec

Step 2.5: Extract UI/UX Context from Spec

Step 3: Derive Story Breakdown (if not --single)

Step 4: Create Story Issues

Step 5: --single Mode

Step 6: Summary

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