opencode-controller

Orchestrate Opencode Plan-to-Build workflows with session and auth guardrails.

18|2|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/yuanyuekejiJN/AivoClaw --skill opencode-controller-yuanyuekejijn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-controller
Source: https://github.com/yuanyuekejiJN/AivoClaw/tree/main/extraSkills/opencode-controller-1.0.0
Command: npx skills add https://github.com/yuanyuekejiJN/AivoClaw --skill opencode-controller-yuanyuekejijn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It solves the problem of coordinating Opencode work without technical expertise, by guiding the user and the agent through the correct Plan-to-Build workflow and safe model/auth setup.

Core Features & Use Cases

  • Session management with guardrails: Reuse existing sessions and block creating new sessions without explicit user approval, keeping project context consistent.
  • Agent (mode) switching control: Enforce Plan first, then switch to Build only when the approved plan is ready, preventing accidental code generation during planning.
  • Provider and authentication handling: Select the requested model provider and use Opencode-generated login links, pausing for confirmation to ensure authentication is complete.
  • Workflow orchestration for coding tasks: Repeat the Plan → Build loop until requirements are satisfied, routing Opencode questions back into Plan mode and requiring plan revision when needed.

Quick Start

Ask the skill to control Opencode for a coding task by requesting a step-by-step plan first, selecting the provider and model via /models, and then implementing only after the plan is approved in Plan mode.

Frequently Asked Questions about opencode-controller

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent accidental code generation during the Opencode planning phase?

To prevent accidental code generation during Opencode planning, enforce strict Plan-to-Build mode separation. Always start in Plan mode to block code generation, and switch to Build mode only after the user explicitly approves the step-by-step plan.

How do I manage Opencode sessions without losing project context?

Manage Opencode sessions safely by reusing existing sessions and blocking new session creation without explicit user approval. This guardrail approach maintains consistent project context throughout iterative coding workflows.

What is the correct workflow for provider and model selection in Opencode?

The correct workflow for provider and model selection in Opencode involves using slash commands like /models to select the requested provider. It requires pausing for user confirmation to ensure authentication via login links is fully complete before proceeding.

How do I handle agent questions that arise during an Opencode Build session?

Handle agent questions during an Opencode Build session by routing them back into Plan mode. This workflow orchestration requires a plan revision when needed, ensuring requirements are fully satisfied before resuming code generation.

Can I use slash commands to control agent mode switching in Opencode?

Yes, you can use slash commands to control agent mode switching in Opencode. Slash commands orchestrate the strict transition from Plan mode to Build mode, enforcing safe coding workflows and preventing unauthorized mode changes.