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-requirement - Prompt - OpenSmartRoute

Name: sdp-requirement
Author: Basio0916

Prompt file imported from Basio0916/spec-driven-planning (.codex/prompts/sdp-requirement.prompt.md). Copyright stays with the author.

SDP Requirement Refinement

Refine a requirement and normalize it for task generation.

Input

Argument: Either (A) a short natural-language requirement string, or (B) a file path to a markdown requirement.
If a path is given, read it. Otherwise, take the argument string as the base requirement.
Usage Example: /sdp-requirement Add user authentication

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

Use templates from .sdp/templates/<lang>/ directory based on the configured language.

Context Files

Read these for context:

.sdp/product.md - Business context and goals
.sdp/tech.md - Technical stack and constraints
.sdp/structure.md - Code structure and organization

Slug Generation

Generate a slug from the requirement text:
- Convert to lowercase
- Replace spaces and special characters with hyphens
- Remove consecutive hyphens
- Limit to 50 characters
- Examples: "Add user authentication" → "add-user-authentication", "RESTful API for products" → "restful-api-for-products"
Check for duplicate slugs in .sdp/specs/ directory by listing existing folders
If duplicate exists, append -2, -3, etc.
Create .sdp/specs/ directory if it doesn't exist

Deliverable

Create or update a file at .sdp/specs/<slug>/requirement.md with the refined spec.
Create the .sdp/specs/<slug>/ directory if it doesn't exist
The file must follow .sdp/templates/<lang>/requirement.md sections exactly (use the language-specific template).

Refinement Rules

Content Alignment

Product alignment: Align with .sdp/product.md (goals/KPIs)
Technical feasibility: Consider constraints from .sdp/tech.md
Structure awareness: Reference existing modules from .sdp/structure.md

Required Sections (from template)

機能概要 (Feature Overview): Business goal and feature purpose statement
ユーザーストーリー (User Stories): User stories in "Who/What/Why" format
機能要件 (Functional Requirements): Functional requirements with detailed descriptions and acceptance criteria (checklist format)
非機能要件 (Non-Functional Requirements): Non-functional requirements (performance, security, maintainability, etc.) as needed

Scoping Guidelines

MVP focus: Constrain scope to MVP if ambiguous
Clear boundaries: Explicitly state what's in/out of scope
Incremental delivery: Break large features into smaller requirements if needed

Output Format

Generate all content based on the configured language (.sdp/config/language.yml).

After writing the file, print a summary in the same language as the content:

For Japanese:

【要件定義完了】
📋 Slug: <slug>
📝 タイトル: <要件タイトル>
📁 ファイル: .sdp/specs/<slug>/requirement.md

💡 次のステップ:
  - 要件内容を確認し、修正が必要な場合は自然言語で指示してください
  - 要件が確定したら #sdp-pre-design で設計案を評価してください

For English:

【Requirement Definition Completed】
📋 Slug: <slug>
📝 Title: <requirement title>
📁 File: .sdp/specs/<slug>/requirement.md

💡 Next Steps:
  - Review the requirement and provide feedback if changes needed
  - When requirement is finalized: Use #sdp-pre-design to evaluate design options

Allowed Tools

Read, Write, Edit, File Search, Grep only

Install sdp-requirement 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 Requirement Refinement Refine a requirement and normalize it for task generation. ## Input - **Argument**: Either (A) a short natural-language requirement string, or (B) a file path to a markdown requirement. - If a path is given, read it. Otherwise, take the argument string as the base requirement. - **Usage Example**: `/sdp-requirement Add user authentication` ## 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** Use templates from `.sdp/templates/<lang>/` directory based on the configured language. ## Context Files Read these for context: - `.sdp/product.md` - Business context and goals - `.sdp/tech.md` - Technical stack and constraints - `.sdp/structure.md` - Code structure and organization ## Slug Generation - Generate a slug from the requirement text: - Convert to lowercase - Replace spaces and special characters with hyphens - Remove consecutive hyphens - Limit to 50 characters - Examples: "Add user authentication" → "add-user-authentication", "RESTful API for products" → "restful-api-for-products" - Check for duplicate slugs in `.sdp/specs/` directory by listing existing folders - If duplicate exists, append `-2`, `-3`, etc. - Create `.sdp/specs/` directory if it doesn't exist ## Deliverable - Create or update a file at `.sdp/specs/<slug>/requirement.md` with the refined spec. - Create the `.sdp/specs/<slug>/` directory if it doesn't exist - The file must follow `.sdp/templates/<lang>/requirement.md` sections exactly (use the language-specific template). ## Refinement Rules ### Content Alignment - **Product alignment**: Align with `.sdp/product.md` (goals/KPIs) - **Technical feasibility**: Consider constraints from `.sdp/tech.md` - **Structure awareness**: Reference existing modules from `.sdp/structure.md` ### Required Sections (from template) 1. **機能概要** (Feature Overview): Business goal and feature purpose statement 2. **ユーザーストーリー** (User Stories): User stories in "Who/What/Why" format 3. **機能要件** (Functional Requirements): Functional requirements with detailed descriptions and acceptance criteria (checklist format) 4. **非機能要件** (Non-Functional Requirements): Non-functional requirements (performance, security, maintainability, etc.) as needed ### Scoping Guidelines - **MVP focus**: Constrain scope to MVP if ambiguous - **Clear boundaries**: Explicitly state what's in/out of scope - **Incremental delivery**: Break large features into smaller requirements if needed ## Output Format Generate all content based on the configured language (`.sdp/config/language.yml`). After writing the file, print a summary in the same language as the content: For Japanese: ``` 【要件定義完了】 📋 Slug: <slug> 📝 タイトル: <要件タイトル> 📁 ファイル: .sdp/specs/<slug>/requirement.md 💡 次のステップ: - 要件内容を確認し、修正が必要な場合は自然言語で指示してください - 要件が確定したら #sdp-pre-design で設計案を評価してください ``` For English: ``` 【Requirement Definition Completed】 📋 Slug: <slug> 📝 Title: <requirement title> 📁 File: .sdp/specs/<slug>/requirement.md 💡 Next Steps: - Review the requirement and provide feedback if changes needed - When requirement is finalized: Use #sdp-pre-design to evaluate design options ``` ## Allowed Tools Read, Write, Edit, File Search, Grep only

{ "prompt": "# SDP Requirement Refinement\n\nRefine a requirement and normalize it for task generation.\n\n## Input\n\n- **Argument**: Either (A) a short natural-language requirement string, or (B) a file path to a markdown requirement.\n- If a path is given, read it. Otherwise, take the argument string as the base requirement.\n- **Usage Example**: `/sdp-requirement Add user authentication`\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\nUse templates from `.sdp/templates/<lang>/` directory based on the configured language.\n\n## Context Files\n\nRead these for context:\n- `.sdp/product.md` - Business context and goals\n- `.sdp/tech.md` - Technical stack and constraints\n- `.sdp/structure.md` - Code structure and organization\n\n## Slug Generation\n\n- Generate a slug from the requirement text:\n - Convert to lowercase\n - Replace spaces and special characters with hyphens\n - Remove consecutive hyphens\n - Limit to 50 characters\n - Examples: \"Add user authentication\" → \"add-user-authentication\", \"RESTful API for products\" → \"restful-api-for-products\"\n- Check for duplicate slugs in `.sdp/specs/` directory by listing existing folders\n- If duplicate exists, append `-2`, `-3`, etc.\n- Create `.sdp/specs/` directory if it doesn't exist\n\n## Deliverable\n\n- Create or update a file at `.sdp/specs/<slug>/requirement.md` with the refined spec.\n- Create the `.sdp/specs/<slug>/` directory if it doesn't exist\n- The file must follow `.sdp/templates/<lang>/requirement.md` sections exactly (use the language-specific template).\n\n## Refinement Rules\n\n### Content Alignment\n\n- **Product alignment**: Align with `.sdp/product.md` (goals/KPIs)\n- **Technical feasibility**: Consider constraints from `.sdp/tech.md`\n- **Structure awareness**: Reference existing modules from `.sdp/structure.md`\n\n### Required Sections (from template)\n\n1. **機能概要** (Feature Overview): Business goal and feature purpose statement\n2. **ユーザーストーリー** (User Stories): User stories in \"Who/What/Why\" format\n3. **機能要件** (Functional Requirements): Functional requirements with detailed descriptions and acceptance criteria (checklist format)\n4. **非機能要件** (Non-Functional Requirements): Non-functional requirements (performance, security, maintainability, etc.) as needed\n\n### Scoping Guidelines\n\n- **MVP focus**: Constrain scope to MVP if ambiguous\n- **Clear boundaries**: Explicitly state what's in/out of scope\n- **Incremental delivery**: Break large features into smaller requirements if needed\n\n## Output Format\n\nGenerate all content based on the configured language (`.sdp/config/language.yml`).\n\nAfter writing the file, print a summary in the same language as the content:\n\nFor Japanese:\n```\n【要件定義完了】\n📋 Slug: <slug>\n📝 タイトル: <要件タイトル>\n📁 ファイル: .sdp/specs/<slug>/requirement.md\n\n💡 次のステップ:\n - 要件内容を確認し、修正が必要な場合は自然言語で指示してください\n - 要件が確定したら #sdp-pre-design で設計案を評価してください\n```\n\nFor English:\n```\n【Requirement Definition Completed】\n📋 Slug: <slug>\n📝 Title: <requirement title>\n📁 File: .sdp/specs/<slug>/requirement.md\n\n💡 Next Steps:\n - Review the requirement and provide feedback if changes needed\n - When requirement is finalized: Use #sdp-pre-design to evaluate design options\n```\n\n## Allowed Tools\n\nRead, Write, Edit, File Search, Grep only", "variables": [], "notes": "Refine a requirement and normalize it for task generation Mode: agent.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/Basio0916/spec-driven-planning", "path": ".codex/prompts/sdp-requirement.prompt.md", "ref": "f07eb62df7be33395bb2db35eba02b0a1271b7f6", "url": "https://github.com/Basio0916/spec-driven-planning/blob/f07eb62df7be33395bb2db35eba02b0a1271b7f6/.codex/prompts/sdp-requirement.prompt.md", "key": "Basio0916/spec-driven-planning/.codex/prompts/sdp-requirement.prompt.md" } } }

sdp-requirement

About

SDP Requirement Refinement

Input

Language Configuration

Context Files

Slug Generation

Deliverable

Refinement Rules

Content Alignment

Required Sections (from template)

Scoping Guidelines

Output Format

Allowed Tools

Install sdp-requirement 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