opencode-subagent-driven-developmentlisted

# Bridge: Subagent-Driven Development ↔ OpenCode Implementer **Announce at start:** "I'm using the bridge:opencode-subagent-driven-development skill to run the plan, and I'll ask which implementer to use." Plain `/subagent-driven-development` (Superpowers) always uses a Claude subagent as the implementer. This skill exists because that choice is otherwise silent — it asks up front whether to swap the implementer for `opencode-bridge` instead, while keeping every review gate from `subagent-driven-development` unchanged. ## Step 1: Ask which implementer to use Ask via AskUserQuestion: "For this plan's implementer step, use a Claude subagent (Superpowers default) or delegate implementation to OpenCode via opencode-bridge?" - **Claude subagent** → this skill is a pure passthrough: invoke `superpowers:subagent-driven-development` normally and stop here. Do not duplicate its logic. - **OpenCode via opencode-bridge** → continue to Step 2. ## Step 2: Locate the review prompt templates Find Superpowers' review templates (path is version-suffixed, so search rather than hardcode): ```bash find ~/.claude/plugins -path "*subagent-driven-development/spec-reviewer-prompt.md" 2>/dev/null find ~/.claude/plugins -path "*subagent-driven-development/code-quality-reviewer-prompt.md" 2>/dev/null ``` If either search returns nothing, stop and tell the user the Superpowers plugin isn't installed — this skill requires it for the review stage. If multiple matches, use the most recently modified