Introduction
What opencode-onboard is, and what it sets up in your repository.
Most codebases have no AGENTS.md, no architecture documentation that agents can
read, and no defined workflow for picking up tasks. Agents end up improvising,
producing inconsistent results.
opencode-onboard fixes that in a single interactive wizard. It configures OpenCode with OpenSpec for structured change management, native subagent waves for parallel agent execution, codegraph for code intelligence, and agentmemory for shared context across agent sessions. It also installs an agent team, platform skills, and slash commands: everything agents need to plan, implement, and ship.
Install
npx @plainconceptsplatform/opencode-onboard@latestRequires Node.js 18 or higher. See Getting started for prerequisites and per-step commands.
What it wires together
| Tool | Role |
|---|---|
| OpenCode | The agent runtime. Native parallel subagent waves, no external plugins, no git worktrees. |
| OpenSpec | Structured change management: proposals, specs, and tasks. |
| codegraph | Code intelligence and indexing, so agents understand the codebase before touching it. |
| agentmemory | Shared context across agent sessions. |
Supported platforms
Backlog and repository platforms are chosen independently, so mixed setups work: a Jira backlog with a GitHub repository, or a browser backlog with a GitLab repository.
- Backlog: GitHub, Azure DevOps, Jira, browser-based, or None
- Repository: GitHub, Azure DevOps, GitLab, or None
Choosing None for a backlog means no userstory skills are injected; choosing
None for a repository means no pull request skills are injected.
Where to go next
- Getting started: install, prerequisites, and reruns
- The wizard: what each of the 10 steps does
- Commands: the full slash command reference
- The pipeline: how work flows from a URL to a pull request