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.

sdp-export-issues - Prompt

Name: sdp-export-issues
Author: Basio0916

Prompt file imported from Basio0916/spec-driven-planning (.codex/prompts/sdp-export-issues.prompt.md). Fill in {{slug}} before use. Copyright stays with the author.

SDP Export Issues

Export task breakdown to GitHub Issues, Jira Issues, or local markdown files.

Inputs

slug: An existing requirement folder at .sdp/specs/<slug>/ containing tasks.yml
Usage Example: /sdp-export-issues add-user-authentication
Export Config: .sdp/config/export.yml (output destination, repository, labels)

Language Configuration

Read .sdp/config/language.yml to determine the output language:

If language: en, generate all content in English
If language: ja, generate all content in Japanese

Console output should also be in the configured language.

Context Files

Read these for context:

.sdp/specs/{{slug}}/tasks.yml - Task breakdown to export
.sdp/specs/{{slug}}/requirement.md - Original requirement
.sdp/config/export.yml - Export configuration (destination, repo, labels)

Pre-Check

Before starting, verify that:

.sdp/specs/{{slug}}/ directory exists
.sdp/specs/{{slug}}/tasks.yml file exists
.sdp/config/export.yml file exists

Report errors if files are missing.

Important: Configure Before Running

Before running this command, you MUST configure .sdp/config/export.yml:

Set export destination: Choose destination: github or destination: local
Configure GitHub settings (if using GitHub mode):
- Set github.repo to your repository (e.g., "owner/repo")
- Customize github.labels as needed
Configure local settings (if using local mode):
- Set local.out_dir if different from default

User should review and edit .sdp/config/export.yml before proceeding.

Step 1: Load Export Configuration

Read .sdp/config/export.yml to determine:

destination: Export target (github, jira, or local)
Destination-specific settings (repository, project, labels, etc.)
issue_mode: How to organize tasks
- sub_issues / sub_tasks: Create parent-child relationships
- linked_issues: Create separate issues with links
- single_issue: Create one comprehensive issue with all tasks

Step 2: Determine Export Destination

Based on the destination field in export.yml:

github: Export to GitHub Issues (requires gh CLI)
jira: Export to Jira Issues (uses REST API v3)
backlog: Export to Backlog Issues (uses REST API v2)
local: Export to local markdown files (no external tools required)

Implementation Details

For detailed implementation instructions, refer to:

GitHub mode: .sdp/docs/export-github.md
Jira mode: .sdp/docs/export-jira.md
Backlog mode: .sdp/docs/export-backlog.md
Local mode: .sdp/docs/export-local.md

Step 3: Execute Export

GitHub Export

If destination: github, read .sdp/docs/export-github.md for complete implementation details.

Summary:

Check gh CLI availability and authentication
Check gh sub-issue extension if needed
Create main issue using appropriate template
Create task issues if using sub_issues or linked_issues mode
Generate console output with issue URLs

Jira Export

If destination: jira, read .sdp/docs/export-jira.md for complete implementation details.

Summary:

Check Jira configuration (url, email, project, API token)
Load templates and convert Wiki Markup to ADF
Create main issue via REST API
Create task issues if using sub_tasks or linked_issues mode
Generate console output with issue URLs

Backlog Export

If destination: backlog, read .sdp/docs/export-backlog.md for complete implementation details.

Summary:

Check Backlog configuration (space_key, project_key, API key)
Get project ID and issue type IDs via REST API
Create main issue with Markdown description
Create task issues if using sub_tasks or linked_issues mode
Generate console output with issue URLs

Local Export

If destination: local, read .sdp/docs/export-local.md for complete implementation details.

Summary:

Create output directory if needed
Generate markdown file with issue drafts
Generate console output with file path

Issue Templates

Issue Title Format

Main issue: [<slug>] <requirement title>
Task issue: [<slug>][T-xxx] <task.title>

Issue Body Templates

Use templates from .sdp/templates/<lang>/:

issue-single.md - For single issue mode
issue-main.md - For main requirement issue
issue-task.md - For individual task issues

Replace placeholders with actual values from requirement and tasks files.

Console Output Format

After export completes, print a summary:

【エクスポート完了】
📋 要件: <slug>
🎯 エクスポート先: <destination>
📊 作成されたIssue数: <count>

Issue URL:
- メインIssue: <main_issue_url>
- タスクIssue:
  - T-001: <task_issue_url>
  - T-002: <task_issue_url>
  ...

💡 次のステップ:
  - Issueボードで進捗を管理してください
  - 必要に応じてタスクの優先順位を調整してください

Allowed Tools

Read, Write, Terminal, File Search, Grep

Install sdp-export-issues 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.

# SDP Export Issues Export task breakdown to GitHub Issues, Jira Issues, or local markdown files. ## Inputs - **slug**: An existing requirement folder at `.sdp/specs/<slug>/` containing `tasks.yml` - **Usage Example**: `/sdp-export-issues add-user-authentication` - **Export Config**: `.sdp/config/export.yml` (output destination, repository, labels) ## Language Configuration Read `.sdp/config/language.yml` to determine the output language: - If `language: en`, generate all content in **English** - If `language: ja`, generate all content in **Japanese** Console output should also be in the configured language. ## Context Files Read these for context: - `.sdp/specs/{{slug}}/tasks.yml` - Task breakdown to export - `.sdp/specs/{{slug}}/requirement.md` - Original requirement - `.sdp/config/export.yml` - Export configuration (destination, repo, labels) ## Pre-Check Before starting, verify that: - `.sdp/specs/{{slug}}/` directory exists - `.sdp/specs/{{slug}}/tasks.yml` file exists - `.sdp/config/export.yml` file exists Report errors if files are missing. ## Important: Configure Before Running **Before running this command, you MUST configure `.sdp/config/export.yml`**: 1. **Set export destination**: Choose `destination: github` or `destination: local` 2. **Configure GitHub settings** (if using GitHub mode): - Set `github.repo` to your repository (e.g., "owner/repo") - Customize `github.labels` as needed 3. **Configure local settings** (if using local mode): - Set `local.out_dir` if different from default **User should review and edit `.sdp/config/export.yml` before proceeding.** ## Step 1: Load Export Configuration Read `.sdp/config/export.yml` to determine: - `destination`: Export target (`github`, `jira`, or `local`) - Destination-specific settings (repository, project, labels, etc.) - `issue_mode`: How to organize tasks - `sub_issues` / `sub_tasks`: Create parent-child relationships - `linked_issues`: Create separate issues with links - `single_issue`: Create one comprehensive issue with all tasks ## Step 2: Determine Export Destination Based on the `destination` field in export.yml: - **`github`**: Export to GitHub Issues (requires `gh` CLI) - **`jira`**: Export to Jira Issues (uses REST API v3) - **`backlog`**: Export to Backlog Issues (uses REST API v2) - **`local`**: Export to local markdown files (no external tools required) ### Implementation Details For detailed implementation instructions, refer to: - **GitHub mode**: `.sdp/docs/export-github.md` - **Jira mode**: `.sdp/docs/export-jira.md` - **Backlog mode**: `.sdp/docs/export-backlog.md` - **Local mode**: `.sdp/docs/export-local.md` ## Step 3: Execute Export ### GitHub Export If `destination: github`, read `.sdp/docs/export-github.md` for complete implementation details. **Summary**: 1. Check `gh` CLI availability and authentication 2. Check `gh sub-issue` extension if needed 3. Create main issue using appropriate template 4. Create task issues if using sub_issues or linked_issues mode 5. Generate console output with issue URLs ### Jira Export If `destination: jira`, read `.sdp/docs/export-jira.md` for complete implementation details. **Summary**: 1. Check Jira configuration (url, email, project, API token) 2. Load templates and convert Wiki Markup to ADF 3. Create main issue via REST API 4. Create task issues if using sub_tasks or linked_issues mode 5. Generate console output with issue URLs ### Backlog Export If `destination: backlog`, read `.sdp/docs/export-backlog.md` for complete implementation details. **Summary**: 1. Check Backlog configuration (space_key, project_key, API key) 2. Get project ID and issue type IDs via REST API 3. Create main issue with Markdown description 4. Create task issues if using sub_tasks or linked_issues mode 5. Generate console output with issue URLs ### Local Export If `destination: local`, read `.sdp/docs/export-local.md` for complete implementation details. **Summary**: 1. Create output directory if needed 2. Generate markdown file with issue drafts 3. Generate console output with file path ## Issue Templates ### Issue Title Format - Main issue: `[<slug>] <requirement title>` - Task issue: `[<slug>][T-xxx] <task.title>` ### Issue Body Templates Use templates from `.sdp/templates/<lang>/`: - `issue-single.md` - For single issue mode - `issue-main.md` - For main requirement issue - `issue-task.md` - For individual task issues Replace placeholders with actual values from requirement and tasks files. ## Console Output Format After export completes, print a summary: ``` 【エクスポート完了】 📋 要件: <slug> 🎯 エクスポート先: <destination> 📊 作成されたIssue数: <count> Issue URL: - メインIssue: <main_issue_url> - タスクIssue: - T-001: <task_issue_url> - T-002: <task_issue_url> ... 💡 次のステップ: - Issueボードで進捗を管理してください - 必要に応じてタスクの優先順位を調整してください ``` ## Allowed Tools Read, Write, Terminal, File Search, Grep

{ "prompt": "# SDP Export Issues\n\nExport task breakdown to GitHub Issues, Jira Issues, or local markdown files.\n\n## Inputs\n\n- **slug**: An existing requirement folder at `.sdp/specs/<slug>/` containing `tasks.yml`\n- **Usage Example**: `/sdp-export-issues add-user-authentication`\n- **Export Config**: `.sdp/config/export.yml` (output destination, repository, labels)\n\n## Language Configuration\n\nRead `.sdp/config/language.yml` to determine the output language:\n- If `language: en`, generate all content in **English**\n- If `language: ja`, generate all content in **Japanese**\n\nConsole output should also be in the configured language.\n\n## Context Files\n\nRead these for context:\n- `.sdp/specs/{{slug}}/tasks.yml` - Task breakdown to export\n- `.sdp/specs/{{slug}}/requirement.md` - Original requirement\n- `.sdp/config/export.yml` - Export configuration (destination, repo, labels)\n\n## Pre-Check\n\nBefore starting, verify that:\n- `.sdp/specs/{{slug}}/` directory exists\n- `.sdp/specs/{{slug}}/tasks.yml` file exists\n- `.sdp/config/export.yml` file exists\n\nReport errors if files are missing.\n\n## Important: Configure Before Running\n\n**Before running this command, you MUST configure `.sdp/config/export.yml`**:\n\n1. **Set export destination**: Choose `destination: github` or `destination: local`\n2. **Configure GitHub settings** (if using GitHub mode):\n - Set `github.repo` to your repository (e.g., \"owner/repo\")\n - Customize `github.labels` as needed\n3. **Configure local settings** (if using local mode):\n - Set `local.out_dir` if different from default\n\n**User should review and edit `.sdp/config/export.yml` before proceeding.**\n\n## Step 1: Load Export Configuration\n\nRead `.sdp/config/export.yml` to determine:\n- `destination`: Export target (`github`, `jira`, or `local`)\n- Destination-specific settings (repository, project, labels, etc.)\n- `issue_mode`: How to organize tasks\n - `sub_issues` / `sub_tasks`: Create parent-child relationships\n - `linked_issues`: Create separate issues with links\n - `single_issue`: Create one comprehensive issue with all tasks\n\n## Step 2: Determine Export Destination\n\nBased on the `destination` field in export.yml:\n- **`github`**: Export to GitHub Issues (requires `gh` CLI)\n- **`jira`**: Export to Jira Issues (uses REST API v3)\n- **`backlog`**: Export to Backlog Issues (uses REST API v2)\n- **`local`**: Export to local markdown files (no external tools required)\n\n### Implementation Details\n\nFor detailed implementation instructions, refer to:\n- **GitHub mode**: `.sdp/docs/export-github.md`\n- **Jira mode**: `.sdp/docs/export-jira.md`\n- **Backlog mode**: `.sdp/docs/export-backlog.md`\n- **Local mode**: `.sdp/docs/export-local.md`\n\n## Step 3: Execute Export\n\n### GitHub Export\n\nIf `destination: github`, read `.sdp/docs/export-github.md` for complete implementation details.\n\n**Summary**:\n1. Check `gh` CLI availability and authentication\n2. Check `gh sub-issue` extension if needed\n3. Create main issue using appropriate template\n4. Create task issues if using sub_issues or linked_issues mode\n5. Generate console output with issue URLs\n\n### Jira Export\n\nIf `destination: jira`, read `.sdp/docs/export-jira.md` for complete implementation details.\n\n**Summary**:\n1. Check Jira configuration (url, email, project, API token)\n2. Load templates and convert Wiki Markup to ADF\n3. Create main issue via REST API\n4. Create task issues if using sub_tasks or linked_issues mode\n5. Generate console output with issue URLs\n\n### Backlog Export\n\nIf `destination: backlog`, read `.sdp/docs/export-backlog.md` for complete implementation details.\n\n**Summary**:\n1. Check Backlog configuration (space_key, project_key, API key)\n2. Get project ID and issue type IDs via REST API\n3. Create main issue with Markdown description\n4. Create task issues if using sub_tasks or linked_issues mode\n5. Generate console output with issue URLs\n\n### Local Export\n\nIf `destination: local`, read `.sdp/docs/export-local.md` for complete implementation details.\n\n**Summary**:\n1. Create output directory if needed\n2. Generate markdown file with issue drafts\n3. Generate console output with file path\n\n## Issue Templates\n\n### Issue Title Format\n- Main issue: `[<slug>] <requirement title>`\n- Task issue: `[<slug>][T-xxx] <task.title>`\n\n### Issue Body Templates\n\nUse templates from `.sdp/templates/<lang>/`:\n- `issue-single.md` - For single issue mode\n- `issue-main.md` - For main requirement issue\n- `issue-task.md` - For individual task issues\n\nReplace placeholders with actual values from requirement and tasks files.\n\n## Console Output Format\n\nAfter export completes, print a summary:\n\n```\n【エクスポート完了】\n📋 要件: <slug>\n🎯 エクスポート先: <destination>\n📊 作成されたIssue数: <count>\n\nIssue URL:\n- メインIssue: <main_issue_url>\n- タスクIssue:\n - T-001: <task_issue_url>\n - T-002: <task_issue_url>\n ...\n\n💡 次のステップ:\n - Issueボードで進捗を管理してください\n - 必要に応じてタスクの優先順位を調整してください\n```\n\n## Allowed Tools\n\nRead, Write, Terminal, File Search, Grep", "variables": [ "slug" ], "notes": "Export task breakdown to GitHub Issues, Jira Issues, or local markdown files Mode: agent.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/Basio0916/spec-driven-planning", "path": ".codex/prompts/sdp-export-issues.prompt.md", "ref": "f07eb62df7be33395bb2db35eba02b0a1271b7f6", "url": "https://github.com/Basio0916/spec-driven-planning/blob/f07eb62df7be33395bb2db35eba02b0a1271b7f6/.codex/prompts/sdp-export-issues.prompt.md", "key": "Basio0916/spec-driven-planning/.codex/prompts/sdp-export-issues.prompt.md" } } }

sdp-export-issues

About

SDP Export Issues

Inputs

Language Configuration

Context Files

Pre-Check

Important: Configure Before Running

Step 1: Load Export Configuration

Step 2: Determine Export Destination

Implementation Details

Step 3: Execute Export

GitHub Export

Jira Export

Backlog Export

Local Export

Issue Templates

Issue Title Format

Issue Body Templates

Console Output Format

Allowed Tools

Install sdp-export-issues 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