Build a disciplined, delivery-aware OpenCode workflow with a CEO agent, specialist delegation, persistent state, and GitHub handoff.
opencode-ceo is an OpenCode plugin that turns software work into a controlled delivery pipeline. Instead of letting one agent improvise the whole task, it moves work through defined stages, persists decisions and artifacts, and can prepare Git branches and pull requests when the repository is ready.
- CI on
main: enabled and protected - Release workflow: configured in
.github/workflows/release.yml - Dependabot: configured in
.github/dependabot.yml - npm package publication: not published yet
- GitHub release: not created yet
If you are evaluating release readiness, start with the Release Guide.
- Deterministic pipeline ownership instead of one-shot agent output
- SQLite-backed artifacts, gates, and state for long-running sessions
- GitHub-aware delivery helpers for branch and PR preparation
- Configurable autonomy for teams that want review gates before delivery
Start here if you want the full docs map:
- What This Project Does
- Status At A Glance
- Documentation Hub
- Installation Status
- Configuration Example
- Pipeline Overview
- GitHub Delivery
- Local Verification
- Repository Controls
Core guides:
- Usage Guide
- Pull Request Guide
- Model Recommendations
- Release Guide
- Governance and Branch Policy
- Architecture
Repository policies:
The package name is opencode-ceo, but the first public npm release has not been published yet.
Current options:
- local development from this repository
- future npm install after the first release
Planned install command after publication:
npm install opencode-ceo{
"plugins": [
{
"name": "opencode-ceo",
"config": {
"autonomyLevel": "gated",
"gates": {
"approve-plan": "manual",
"approve-review": "auto",
"approve-delivery": "manual"
}
}
}
]
}Minimal full-autonomy setup:
{
"plugins": [
{
"name": "opencode-ceo",
"config": {
"autonomyLevel": "full"
}
}
]
}[intake] -> [decompose] -> [implement] -> [review] -> [test] -> [deliver] -> [completed]
\-> [blocked] \-> [failed]
Stage summary:
intake: capture the task and detect the project stackdecompose: build an implementation planimplement: produce the change setreview: inspect correctness and risktest: validate behavior and regression safetydeliver: prepare branch and PR output
For deeper detail, see Architecture.
You can tune modelPreferences by stage. Suggested defaults and trade-offs live here:
opencode-ceo includes GitHub-aware delivery tools:
ceo_branch_preparecreatesceo/<pipeline-id>/<slug>branchesceo_pr_preparepushes the active branch tooriginand opens a PR withgh pr createceo_repo_fingerprintreports remote, git status, and general repo readiness
Before using PR automation locally:
gh auth loginbun install
bun run ci:verifyUseful individual commands:
bun run buildbun run typecheckbun testbun run pack:check
- protected
mainbranch - required
quality,tests, andpackagechecks - linear history enforced
- force-push disabled on
main - conversations must be resolved before merge
- Dependabot active for npm and GitHub Actions
- CI currently listens to both
mainandmasterfor compatibility, whilemainis the active branch policy target
Details: Governance and Branch Policy
- operational setup: Usage Guide
- contribution flow: Pull Request Guide
- release flow: Release Guide
- repo policy: Governance and Branch Policy
MIT