| name | deepseek-orchestrator |
| description | Use visible app-native DeepSeek V4 Flash Max Codex tasks for independent implementation tracks while one Sol task owns the outcome and integration. Use when the user explicitly asks for DeepSeek orchestration or deliberately assigns independent tracks to DeepSeek. |
Visible DeepSeek task orchestration
Load and follow $outcome-driven-delivery before dispatch. This skill changes
only the execution shape; it does not add deliveries, pull requests, checks,
reviews, permissions, or work.
Keep GPT-5.6 Sol accountable for the requested outcome, scope, dependencies,
approvals, and final integration. Orchestrate only when the user asks or when at
least two independent implementation tracks already exist without shared
unfinished files. Otherwise Sol implements directly.
When orchestration applies and the app can create visible tasks:
- Read the destination host's live app-native
create_thread model catalog.
If it lists deepseek/deepseek-v4-flash with max, create one visible task
per non-overlapping track with that exact model and effort.
- Give every task exact prompt lines:
Ownership: <files or subsystem>,
Check: <one direct command or observable>, and Stop: <after the check or first blocker>. Include the exact workspace or clean worktree and all real
privacy, security, compatibility, and approval boundaries.
- Keep every task in the same user request, delivery, and pull request.
DeepSeek tasks do not create durable outcomes, milestones, reviews, or pull
requests. Sol inspects the exact diff and direct check before accepting it.
- Wait through the app task lifecycle. Do not poll continuously or use fixed
sleeps. Intervene only for scope drift, a dependency handoff, an approval or
blocker, or final integration.
- Continue unfinished work through the same visible task using the app's
send_message_to_thread surface. Preserve its model and effort; never create
a replacement merely to continue the same track.
Treat availability as fail-closed. The hidden subagent model list is not the
app-native catalog. If DeepSeek is absent immediately after install, run
codex-multiprovider doctor, fully quit and reopen Codex, and read the catalog
again. Only an actual absence after that recovery or a failed visible task
creation call activates direct Sol implementation. Never substitute Kimi,
Luna, Opus, Terra, or a hidden worker.
DeepSeek uses the signed Codex core's native task/tool lifecycle through the
configured OpenRouter route. The orchestrator therefore has the same ownership,
continuation, wait, integration, stop, and authority controls as the Opus
orchestrator. This is a system guarantee, not evidence that the models have
equal judgment or reasoning quality.
Task creation never expands filesystem, provider, credential, account,
repository, GitHub, billing, or other external-action authority. Never place an
OpenRouter credential, prompt history, provider response, or private identifier
in a task prompt or Git.
