Summary
Add an AI_SETUP_LANES.md guide documenting this repo's two recommended AI coding setups.
Each setup should have exactly:
This is guidance, not a hard rule. Maintainer override is always allowed.
OpenCode is less settled for now, so keep the strategy flexible.
Proposed config
repo: opencode-sdlc-wizard
setup_a:
name: OpenCode Premium / Frontier
planner: GPT-5.5 xhigh or Claude Opus via chosen provider
driver: frontier model selected by maintainer
reviewer: GPT-5.5 xhigh
setup_b:
name: OpenCode Local / Secondary
planner: local model or OpenCode Go Kimi K2.6
driver: local model or OpenCode Go Kimi/Qwen
reviewer: MiMo V2.5 Pro, Kimi K2.6, or human review
Notes
- Setup A is the premium/frontier OpenCode lane.
- Setup A can use Zen, direct provider access, Claude Code, Codex, or whatever frontier setup the maintainer chooses.
- Setup B is the secondary/local/cheaper lane.
- Setup B can use OpenCode Go, local models, Kimi, Qwen, or another lower-cost provider.
- Kimi K2.6 is the simple all-rounder candidate.
- MiMo V2.5 Pro is a reviewer candidate.
- Qwen can be used as a cheaper driver when the task is clear.
- DeepSeek V4 Flash can be used for boxed-in mechanical work, but do not make it a separate setup field.
- Maintainer override is always allowed.
Prefer Setup A for
- generated
.opencode config behavior
- installer behavior
- release-critical changes
- destructive file operations
- package publishing
- CI/release automation
- security-sensitive behavior
- changes that could damage a consumer repo
Prefer Setup B for
- docs
- examples
- normal OpenCode workflow updates
- low-risk config changes
- simple tests
- OpenCode Go validation
- local/cheap experiments
Proposed task
Add AI_SETUP_LANES.md.
It should include:
- Purpose
- Setup A
- Setup B
- When to use Setup A
- When to use Setup B
- OpenCode Go / Zen / local notes
- Final review policy
- Credit-spend warning
- Privacy warning for free/experimental models
- Maintainer override note
If AGENTS.md exists, add a short section linking to AI_SETUP_LANES.md.
Acceptance criteria
AI_SETUP_LANES.md exists.
- It defines Setup A and Setup B only.
- Each setup has only Planner, Driver, and Reviewer.
- It documents Setup A as OpenCode Premium / Frontier.
- It documents Setup B as OpenCode Local / Secondary.
- It says setups are guidance, not hard rules.
- It says maintainer override is allowed.
- It includes escalation guidance.
- It includes credit-spend guidance.
- It includes a privacy warning for free/experimental models.
AGENTS.md links to it if present.
- No source/package code changes are included.
Summary
Add an
AI_SETUP_LANES.mdguide documenting this repo's two recommended AI coding setups.Each setup should have exactly:
This is guidance, not a hard rule. Maintainer override is always allowed.
OpenCode is less settled for now, so keep the strategy flexible.
Proposed config
Notes
Prefer Setup A for
.opencodeconfig behaviorPrefer Setup B for
Proposed task
Add
AI_SETUP_LANES.md.It should include:
If
AGENTS.mdexists, add a short section linking toAI_SETUP_LANES.md.Acceptance criteria
AI_SETUP_LANES.mdexists.AGENTS.mdlinks to it if present.