Tuskway for OpenCode
OpenCode, open models, one shared spec.
Whatever model you run in OpenCode, it needs the same thing to build the right feature: the decisions, the design and a clear brief. Tuskway serves them over MCP, with the workflow skills installed alongside.
What changes
What OpenCode gets from Tuskway.
Two commands
Install the skills, add the MCP server, sign in. Then say “set up Tuskway” and the setup skill finds your workspace.
Model-agnostic memory of decisions
Switch models between tickets without losing what was decided. The spec lives in Tuskway, not in a session.
Readable by people
Everything an agent writes lands in a clean document your team can comment on, not a transcript.
Setup
Connect OpenCode in a minute.
Then run the workflow from OpenCode, one command per step:
/start-epicCapture the goal, constraints and open questions./write-designDraft the tech design in sections your team reviews./draft-ticketsSplit it into briefs with acceptance checks./tackle-ticketBuild one ticket from its brief and design section.
Tuskway skills and MCP server
OpenCode installs the workflow skills and the MCP server separately, so run both commands. If the server is already connected, keep it and do not add another.
- 1
Install the skills, then add the MCP server.
Installnpx skills add tuskway/plugin --agent opencode opencode mcp add tuskway --url https://tuskway.com/mcp - 2
Sign in.
Sign inopencode mcp auth tuskway - 3
Say “set up Tuskway”. The setup skill checks the connection, finds your workspace and suggests what to do next.
Step-by-step guide: set up Tuskway in OpenCode
FAQ
OpenCode questions.
Why are the skills and server installed separately?
OpenCode installs skills and MCP servers through different commands. If the server is already connected, keep it and do not add another.
Your teammates use something else? Same spec.
Give OpenCode a plan your team agreed on.
Every agent on the team reads the same spec, whatever tool it runs in.