opencode-controller

What This Skill Does

The opencode-controller serves as the primary interface between the user and Opencode, acting as the orchestrator for all development activities within the OpenClaw ecosystem. Its fundamental rule is the strict separation of concerns: Clawdbot facilitates the interaction, while all technical planning and code generation occur exclusively within Opencode. This skill manages the entire development lifecycle, from session initialization and model selection to the iterative execution of tasks through the Plan and Build agent modes. By enforcing a rigorous workflow that mandates a 'Plan first' approach, it ensures that project architecture is validated before a single line of code is written, significantly reducing architectural drift and implementation errors.

Installation

To integrate the Opencode controller into your environment, run the following command in your terminal:

clawhub install openclaw/skills/skills/karatla/opencode-controller

Ensure that you have the necessary permissions to manage skills in your local OpenClaw configuration before proceeding.

Use Cases

This skill is designed for complex software development tasks that require systematic architectural oversight. Use it when you are initiating a new project, migrating existing codebases, or implementing complex features that require deep reasoning before coding. It is particularly effective for teams that want to enforce a standard development lifecycle, ensuring that every feature request goes through an explicit planning phase before the Build agent is triggered. It is also ideal for developers managing multiple project sessions who need to switch context, models, or agent modes seamlessly without leaving the chat interface.

Example Prompts

1. "I want to start a new web scraper project. Please initialize Opencode, help me select a model, and get me into the Plan agent so we can define the requirements."
2. "We have a solid plan now. Please switch to the Build agent and start implementing the database connection logic as discussed."
3. "The current code is failing during execution. Switch back to Plan mode so we can analyze the errors and refine our strategy before moving forward."

Tips & Limitations

To maximize the utility of the opencode-controller, always adhere to the Plan → Build loop. Never attempt to force the Build agent to generate code before a plan has been fully approved by the user. If Opencode requires clarification while in Build mode, you must immediately switch back to the Plan agent; attempting to resolve technical ambiguities inside Build can lead to sub-optimal code generation. Remember that the skill does not write code itself, so ensure that your interactions with Opencode are descriptive and structured. Always authenticate providers carefully as prompted by the slash commands; failure to authenticate correctly will block the session initialization process.