Delegate a coding task directly to OpenCode without a planning phase. **Trigger this skill whenever the user's request starts with or contains a direct delegation verb** — "delegate to opencode", "delegate this to opencode", "use opencode to X", "have opencode do X", "just use opencode", "run this through opencode", "ask opencode to X", "hand this to opencode" — REGARDLESS of how large or complex the task itself is. The user's explicit instruction to delegate is authoritative; do not second-guess it based on task size, scope, or complexity. Also trigger when the user names a specific OpenCode-supported model (GLM-5.1, GPT-5, Gemini, Kimi, DeepSeek, Claude via opencode, local Ollama) and asks to use it. If the user wants Claude to plan first before delegating ("plan and implement", "plan this and then delegate", "design first then implement", "think through the approach"), use the `opencode-implement` skill instead — but only if the user's phrasing explicitly asks for planning. "Delegate" without "plan" means
Plan a coding task with Claude, then delegate the implementation to OpenCode. **Trigger this skill ONLY when the user's request explicitly asks for a planning phase** — "plan and implement", "plan and delegate", "plan this with Claude then have opencode build it", "design first, then implement", "think through the approach then delegate", "let's plan this together first", or any variant that explicitly mentions planning, designing, or thinking through before delegating. Do NOT trigger this skill just because a task is large or multi-file; if the user said "delegate" without "plan", they want direct delegation via `opencode-delegate`, even for substantial work. Trust the user's literal phrasing — if "plan" or "design" is absent, route to `opencode-delegate` instead. The task being non-trivial doesn't override the user's explicit choice of verb.