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-show-plan - Prompt - OpenSmartRoute

Name: sdp-show-plan
Author: Basio0916

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

SDP Project Plan Generation

Transform a task breakdown into a human-readable project plan.

Input

slug: An existing requirement folder at .sdp/specs/<slug>/ containing tasks.yml
Usage Example: /sdp-show-plan 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

Context Files

Read these for context:

.sdp/specs/{{slug}}/tasks.yml - Task breakdown and estimates
.sdp/specs/{{slug}}/requirement.md - Original requirement
.sdp/product.md - Business context

Pre-Check

Before starting, verify that:

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

Report errors if files are missing.

Plan Structure

Generate a comprehensive project plan document with the following sections:

1. Overview

Purpose: 1 paragraph summarizing the requirement and approach
Scope: Key deliverables and boundaries
Timeline Summary: Total estimated hours, confidence level

2. Task Breakdown

Table format with columns:
- Task ID
- Title
- Estimate (hours)
- Dependencies

3. Project Timeline (Mermaid Gantt)

Generate a Gantt-like Mermaid diagram:

gantt
    title <slug> Project Timeline
    dateFormat YYYY-MM-DD
    section Phase 1
    T-001 Task Title :t001, 2024-01-01, 3d
    T-002 Task Title :t002, after t001, 5d
    ...

Use task IDs and dependencies to show:

Sequential vs. parallel work
Critical path highlighted
Milestone markers

4. Risk Register

List top 3 risks from task breakdown:

Risk description
Probability: Low/Medium/High
Impact: Low/Medium/High
Mitigation strategy

5. Critical Path Analysis

Critical path: List of task IDs (e.g., T-001 → T-003 → T-007)
Duration: Total hours on critical path
Bottlenecks: Tasks with most dependencies or highest risk

6. Buffer Recommendation

Based on confidence level and stddev:

Schedule buffer: Recommended % or hours
Resource buffer: Key areas needing backup capacity
Risk buffer: Contingency for high-risk tasks

Output Format

1. Write Plan File

Create .sdp/specs/{{slug}}/plan.md with sections 1-6 above in the configured language (.sdp/config/language.yml).

Note: Do NOT include "Next Steps" section in the plan.md file. Next steps are only shown in the console output below.

2. Console Output

Print a summary in the same language as the content:

【プロジェクト計画生成完了】
📋 要件: <slug>
📁 ファイル: .sdp/specs/<slug>/plan.md

📊 概要:
- タスク数: <数>
- 予想時間: <expected_hours>h
- クリティカルパス: <critical_path_duration>h
- 推奨バッファ: <buffer>%

⚠️  主要リスク: <top_risk_summary>

💡 次のステップ:
   1. .sdp/config/export.yml を確認・編集してください
      - destination: github または local を選択
      - GitHub使用時: repo を設定
      - ローカル使用時: out_dir を設定
   2. /sdp-export-issues でタスクをエクスポートしてください

Allowed Tools

Read, Write, Edit, File Search, Grep only

Install sdp-show-plan 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 Project Plan Generation Transform a task breakdown into a human-readable project plan. ## Input - **slug**: An existing requirement folder at `.sdp/specs/<slug>/` containing `tasks.yml` - **Usage Example**: `/sdp-show-plan 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** ## Context Files Read these for context: - `.sdp/specs/{{slug}}/tasks.yml` - Task breakdown and estimates - `.sdp/specs/{{slug}}/requirement.md` - Original requirement - `.sdp/product.md` - Business context ## Pre-Check Before starting, verify that: - `.sdp/specs/{{slug}}/` directory exists - `.sdp/specs/{{slug}}/tasks.yml` file exists Report errors if files are missing. ## Plan Structure Generate a comprehensive project plan document with the following sections: ### 1. Overview - **Purpose**: 1 paragraph summarizing the requirement and approach - **Scope**: Key deliverables and boundaries - **Timeline Summary**: Total estimated hours, confidence level ### 2. Task Breakdown - **Table format** with columns: - Task ID - Title - Estimate (hours) - Dependencies ### 3. Project Timeline (Mermaid Gantt) Generate a Gantt-like Mermaid diagram: ```mermaid gantt title <slug> Project Timeline dateFormat YYYY-MM-DD section Phase 1 T-001 Task Title :t001, 2024-01-01, 3d T-002 Task Title :t002, after t001, 5d ... ``` Use task IDs and dependencies to show: - Sequential vs. parallel work - Critical path highlighted - Milestone markers ### 4. Risk Register List **top 3 risks** from task breakdown: - **Risk description** - **Probability**: Low/Medium/High - **Impact**: Low/Medium/High - **Mitigation strategy** ### 5. Critical Path Analysis - **Critical path**: List of task IDs (e.g., T-001 → T-003 → T-007) - **Duration**: Total hours on critical path - **Bottlenecks**: Tasks with most dependencies or highest risk ### 6. Buffer Recommendation Based on confidence level and stddev: - **Schedule buffer**: Recommended % or hours - **Resource buffer**: Key areas needing backup capacity - **Risk buffer**: Contingency for high-risk tasks ## Output Format ### 1. Write Plan File Create `.sdp/specs/{{slug}}/plan.md` with sections 1-6 above in the configured language (`.sdp/config/language.yml`). **Note**: Do NOT include "Next Steps" section in the plan.md file. Next steps are only shown in the console output below. ### 2. Console Output Print a summary in the same language as the content: ``` 【プロジェクト計画生成完了】 📋 要件: <slug> 📁 ファイル: .sdp/specs/<slug>/plan.md 📊 概要: - タスク数: <数> - 予想時間: <expected_hours>h - クリティカルパス: <critical_path_duration>h - 推奨バッファ: <buffer>% ⚠️ 主要リスク: <top_risk_summary> 💡 次のステップ: 1. .sdp/config/export.yml を確認・編集してください - destination: github または local を選択 - GitHub使用時: repo を設定 - ローカル使用時: out_dir を設定 2. /sdp-export-issues でタスクをエクスポートしてください ``` ## Allowed Tools Read, Write, Edit, File Search, Grep only

{ "prompt": "# SDP Project Plan Generation\n\nTransform a task breakdown into a human-readable project plan.\n\n## Input\n\n- **slug**: An existing requirement folder at `.sdp/specs/<slug>/` containing `tasks.yml`\n- **Usage Example**: `/sdp-show-plan 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\n## Context Files\n\nRead these for context:\n- `.sdp/specs/{{slug}}/tasks.yml` - Task breakdown and estimates\n- `.sdp/specs/{{slug}}/requirement.md` - Original requirement\n- `.sdp/product.md` - Business context\n\n## Pre-Check\n\nBefore starting, verify that:\n- `.sdp/specs/{{slug}}/` directory exists\n- `.sdp/specs/{{slug}}/tasks.yml` file exists\n\nReport errors if files are missing.\n\n## Plan Structure\n\nGenerate a comprehensive project plan document with the following sections:\n\n### 1. Overview\n\n- **Purpose**: 1 paragraph summarizing the requirement and approach\n- **Scope**: Key deliverables and boundaries\n- **Timeline Summary**: Total estimated hours, confidence level\n\n### 2. Task Breakdown\n\n- **Table format** with columns:\n - Task ID\n - Title\n - Estimate (hours)\n - Dependencies\n\n### 3. Project Timeline (Mermaid Gantt)\n\nGenerate a Gantt-like Mermaid diagram:\n\n```mermaid\ngantt\n title <slug> Project Timeline\n dateFormat YYYY-MM-DD\n section Phase 1\n T-001 Task Title :t001, 2024-01-01, 3d\n T-002 Task Title :t002, after t001, 5d\n ...\n```\n\nUse task IDs and dependencies to show:\n- Sequential vs. parallel work\n- Critical path highlighted\n- Milestone markers\n\n### 4. Risk Register\n\nList **top 3 risks** from task breakdown:\n- **Risk description**\n- **Probability**: Low/Medium/High\n- **Impact**: Low/Medium/High\n- **Mitigation strategy**\n\n### 5. Critical Path Analysis\n\n- **Critical path**: List of task IDs (e.g., T-001 → T-003 → T-007)\n- **Duration**: Total hours on critical path\n- **Bottlenecks**: Tasks with most dependencies or highest risk\n\n### 6. Buffer Recommendation\n\nBased on confidence level and stddev:\n- **Schedule buffer**: Recommended % or hours\n- **Resource buffer**: Key areas needing backup capacity\n- **Risk buffer**: Contingency for high-risk tasks\n\n## Output Format\n\n### 1. Write Plan File\n\nCreate `.sdp/specs/{{slug}}/plan.md` with sections 1-6 above in the configured language (`.sdp/config/language.yml`).\n\n**Note**: Do NOT include \"Next Steps\" section in the plan.md file. Next steps are only shown in the console output below.\n\n### 2. Console Output\n\nPrint a summary in the same language as the content:\n\n```\n【プロジェクト計画生成完了】\n📋 要件: <slug>\n📁 ファイル: .sdp/specs/<slug>/plan.md\n\n📊 概要:\n- タスク数: <数>\n- 予想時間: <expected_hours>h\n- クリティカルパス: <critical_path_duration>h\n- 推奨バッファ: <buffer>%\n\n⚠️ 主要リスク: <top_risk_summary>\n\n💡 次のステップ:\n 1. .sdp/config/export.yml を確認・編集してください\n - destination: github または local を選択\n - GitHub使用時: repo を設定\n - ローカル使用時: out_dir を設定\n 2. /sdp-export-issues でタスクをエクスポートしてください\n```\n\n## Allowed Tools\n\nRead, Write, Edit, File Search, Grep only", "variables": [ "slug" ], "notes": "Transform a task breakdown into a human-readable project plan Mode: agent.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/Basio0916/spec-driven-planning", "path": ".codex/prompts/sdp-show-plan.prompt.md", "ref": "f07eb62df7be33395bb2db35eba02b0a1271b7f6", "url": "https://github.com/Basio0916/spec-driven-planning/blob/f07eb62df7be33395bb2db35eba02b0a1271b7f6/.codex/prompts/sdp-show-plan.prompt.md", "key": "Basio0916/spec-driven-planning/.codex/prompts/sdp-show-plan.prompt.md" } } }

sdp-show-plan

About