Community integration inspired by Conductor (OpenCode bridge)

Hi Conductor maintainers!

First of all, thank you for the work you’ve done on Conductor.

The Context-Driven / spec-driven approach you introduced is one of the clearest and most pragmatic attempts we’ve seen to make structured development with LLMs actually usable in real projects.

We’ve been using Conductor a lot and really appreciate how opinionated (but practical) the workflow is.

Based on that experience, we built a small open-source community bridge that brings the Conductor CDD workflow into OpenCode (a multi-LLM coding CLI) using native OpenCode custom slash commands.

The intent is not to fork or re-implement Conductor, but to:
• reuse the same methodology and mental model
• preserve references to the upstream Conductor repository
• avoid copy/paste or prompt drift
• let teams use Conductor’s workflow inside OpenCode if that’s their daily driver

Repo + install:
https://github.com/bardusco/opencode-conductor-bridge
npx github:bardusco/opencode-conductor-bridge

This is a community project (not affiliated), and we wanted to share it with you first as a courtesy.
We’re happy to adjust wording, positioning, or documentation if you see anything that could be clearer or more aligned with Conductor’s philosophy.

If it ever makes sense, we’d also be glad to submit a small PR to list it under community resources.

Thanks again for building such a thoughtful and practical tool.

Review the linked community bridge repository and the Conductor repository’s community-resource or documentation entry points, if any. The issue does not name a target file, test, or agreed change; completion would require deciding whether and how to list the OpenCode bridge.