Autonomy and workflow v2026.9.0 (CalVer) OpenCode v2.0.16 MIT

Compose Next

A spec-to-ship workflow as a skill: grill, spec, workspace, implement, verify, review, finalize, finish, with a read-only reviewer.

#workflow#skill#spec#review#agents

Quick Answer & Overview

Compose Next is an open-source (MIT) OpenCode V2 plugin by @JadMadi. It resolves: Work that jumps straight to code skips design and review; the path from idea to a merged change needs a repeatable order and an independent reviewer.. Installed via opencode plugin add github:jadmadi/opencode-compose-next, it operates locally with 0% telemetry.

Quick Install via OpenCode V2 Git Distribution

opencode plugin add github:jadmadi/opencode-compose-next

Local manual setup:

Copy compose-next.ts into ~/.config/opencode/plugins/ and the skill into ~/.config/opencode/skills/.

View on GitHub Changelog Agent Markdown (.md)

The Problem It Solves

Work that jumps straight to code skips design and review; the path from idea to a merged change needs a repeatable order and an independent reviewer.

Slash Commands

Slash commands registered by Compose Next
Command	Description & Usage
`/compose-next`	Start the spec-to-ship workflow and attach the compose-next skill.

Design Guardrails & Limitations

Needs the compose-next skill installed under ~/.config/opencode/skills/compose-next/SKILL.md.

Technical Specifications

Target Host: OpenCode V2 (CLI & TUI)
Tested Runtime: OpenCode v2.0.16 (builtUnder-2.0.16)
Artifact File: compose-next.ts
Version Scheme: CalVer (YYYY.MM.MICRO) · Current: v2026.9.0
Default Install Path: ~/.config/opencode/plugins/compose-next.ts
Repository: github.com/jadmadi/opencode-compose-next (opens in new tab)
License: MIT (Open Source)
Last Updated: 2026-09-25

Frequently Asked Questions

What problem does Compose Next solve?

Work that jumps straight to code skips design and review; the path from idea to a merged change needs a repeatable order and an independent reviewer.

How do I install Compose Next in OpenCode V2?

Run the terminal command: `opencode plugin add github:jadmadi/opencode-compose-next`. The runtime clones the repository into `~/.config/opencode/plugins/compose-next.ts` and activates it in your next session. Alternatively: Copy compose-next.ts into ~/.config/opencode/plugins/ and the skill into ~/.config/opencode/skills/.

What are the guardrails and limitations for Compose Next?

Needs the compose-next skill installed under ~/.config/opencode/skills/compose-next/SKILL.md.

What slash commands does Compose Next provide?

/compose-next (Start the spec-to-ship workflow and attach the compose-next skill.)