
Opencode Controller
- 163 installs
- 638 repo stars
- Updated March 7, 2026
- sundial-org/awesome-openclaw-skills
Use opencode-controller for development tasks
About
opencode-controller: A skill for development. This provides functionality for development workflows.
- opencode-controller
Opencode Controller by the numbers
- 163 all-time installs (skills.sh)
- +2 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #2,321 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sundial-org/awesome-openclaw-skills --skill opencode-controllerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 163 |
|---|---|
| repo stars | ★ 638 |
| Last updated | March 7, 2026 |
| Repository | sundial-org/awesome-openclaw-skills ↗ |
What it does
Use opencode-controller for development tasks
Files
Opencode Controller
Core rule
Clawdbot does not write code. All planning and coding happens inside Opencode.
Pre-flight
- Ask the user which AI provider to use.
- Ask how the provider should be authenticated.
- Do not proceed without confirmation.
Session management
- Start Opencode.
- Open session selector using:
/sessions
- If the current project already exists:
- Select the existing session.
- Never create a new session without user approval.
Agent (mode) control
- Open agent selector using:
/agents
- Available agents:
- Plan
- Build
- Always select Plan first.
- Switch agents whenever required using
/agents.
Model selection
- Open model selector using:
/models
- Select the user-requested provider.
- If authentication is required:
- Copy the login link provided by Opencode.
- Send it to the user.
- Wait for confirmation before continuing.
Plan agent behavior
- Ask Opencode to analyze the task.
- Request a clear step-by-step plan.
- Allow Opencode to ask clarification questions.
- Review the plan carefully.
- If the plan is incorrect or incomplete:
- Ask Opencode to revise it.
- Do not allow code generation in Plan.
Build agent behavior
- Switch to Build using
/agents. - Ask Opencode to implement the approved plan.
- If Opencode asks any question:
- Immediately switch back to Plan.
- Answer and confirm the plan.
- Switch back to Build.
Completion
- Repeat the Plan → Build loop until all user requirements are satisfied.
- Never skip Plan.
- Never answer questions in Build.
Output format
- Show all slash commands explicitly.
- State which option is selected.
- Provide login links verbatim.
Ask for provider
Which AI provider do you want to use in Opencode?
Ask for auth
How should Opencode authenticate (auth, key, local)?
Plan request
Analyze the task and propose a step-by-step plan. Ask clarification questions if needed.
Plan revision
The plan has issues. Please revise it.
Build request
Proceed with implementation based on the approved plan.
Core Opencode commands
- Start Opencode:
opencode
- Session selection:
/sessions
- Agent (mode) selection:
/agents
- Model selection:
/models
Common failures and responses
Login link does not work
- Ask the user to retry
- Do not proceed without confirmation
Model not available
- Inform the user
- Ask for an alternative provider
Plan is unclear or contradictory
- Ask Opencode to rewrite the plan
- Do not switch to Build mode
Model selection procedure
- Open model selector with:
/models
- Select the provider requested by the user
Auth-based providers (e.g. OpenAI)
- Opencode will generate a login URL
- Copy the URL exactly
- Send it to the user
- Wait for confirmation before continuing
Never assume authentication is complete.
Plan mode
- Thinking only
- Planning
- Asking questions
- Revising approach
- No code generation
Build mode
- Code implementation
- Execution of approved plan
Mode switching
- Use the Tab key to toggle modes
- Always start in Plan mode
Handling questions from Opencode
- If Opencode asks a question:
- Switch to Plan mode immediately
- Answer carefully
- Confirm or revise the plan
Never answer questions in Build mode.
Session rules
- Opencode keeps a history of projects
- The same project must always use the same session
- Reusing sessions preserves context and decisions
- Starting a new session is allowed only if the user explicitly asks
- Open session selector using:
/sessions
If unsure, ask the user before creating a new session.
Standard workflow
1. Confirm AI provider and auth method with the user 2. Start Opencode 3. Reuse existing project session if present 4. Select AI model using /models 5. Ensure Plan mode 6. Generate and validate plan 7. Switch to Build mode 8. Implement 9. Handle interruptions by returning to Plan mode 10. Repeat until finished