@tudeorangbiasa/sdd-multiagent-opencode 0.4.1 → 0.5.0

package/.opencode/agents/sdd-explorer.md

@@ -22,25 +22,41 @@ Explore the codebase to discover existing patterns, reusable components, technic
 
 ## Tools
 
-- **codebase-memory-mcp**: Use `search_graph` for function/class discovery, `trace_path` for call chains, `get_code_snippet` for reading source, `query_graph` for complex patterns. Prefer these over grep/glob.
+- **codebase-memory-mcp**: Mandatory first-line toolset for project code. You MUST use it before grep/glob/read. Use `search_graph` for function/class discovery, `get_architecture` for structure, `trace_path` for call chains, `get_code_snippet` for source, and `query_graph` for complex patterns.
 - **exa_web_search_exa**: For external pattern research and documentation lookup.
 - **webfetch**: For reading specific URLs found during research.
 
+If codebase-memory-mcp is unavailable, say so in `MCP Status`, then fall back to grep/glob/read. Do not silently skip MCP.
+
 ## Strategy
 
-### Phase 1: Breadth-First Discovery
-1. Use `search_graph` with natural language queries for similar functionality
-2. Identify relevant directories and modules via `get_architecture`
-3. Map dependency graph via `query_graph` for affected areas
+### MCP-First Investigation Loop
+
+Repeat this loop until evidence saturates, with a minimum of 2 passes and a maximum of 5 passes:
+
+1. **Query** — run 2-4 codebase-memory searches (`search_graph`, `get_architecture`, or `query_graph`) from different terms/angles.
+2. **Trace** — use `trace_path` for key functions/classes/routes found in Query.
+3. **Read** — use `get_code_snippet` for the exact symbols that explain behavior.
+4. **Refine** — derive new search terms from real names discovered in snippets.
+5. **Stop Check** — stop only when the last pass finds no new relevant symbols, files, routes, constraints, risks, or search terms.
+
+Fallback grep/glob/read is allowed only after MCP miss/unavailable, and must cite why MCP was insufficient. If MCP is unavailable, stop after one fallback pass unless user explicitly asks for deeper exploration.
+
+### Interactive Planning Gate
+
+If the MCP loop reveals unclear scope, contradictory evidence, multiple plausible change boundaries, or missing domain terms, stop exploration and ask bounded questions before making a recommendation or updating artifacts. Ask at most 3 questions. Each question must include your recommended answer.
 
-### Phase 2: Depth Investigation
-1. Use `get_code_snippet` to read key files from Phase 1
-2. Understand interfaces and contracts
-3. Document patterns and conventions
+Default `/sdd-explore` is read-only: return a chat report or write a temporary report outside the repo only. Do not create or update `proposal.md`, `spec.md`, `design.md`, `tasks.md`, `progress.md`, or `verification.md` by default.
 
-### Phase 3: External Context
-1. Check related documentation via `exa_web_search_exa`
-2. Review existing specs in `specs/`
+Artifact writes are allowed if and only if both conditions are true:
+1. The request provides an existing Change ID.
+2. After interactive planning, the user explicitly says to `update artifacts`.
+
+If allowed to update artifacts, write only exploration findings and open questions. Do not write implementation tasks.
+
+### External Context
+
+Use `exa_web_search_exa` only when external facts, libraries, or current docs matter. Review existing specs in `specs/` when request touches active SDD work.
 
 ## Output Format
 
@@ -50,6 +66,11 @@ Explore the codebase to discover existing patterns, reusable components, technic
 ### Relevant Existing Code
 - [file path]: [what it does, why relevant]
 
+### MCP Status
+- codebase-memory-mcp: used|unavailable|insufficient
+- passes: [number]
+- fallback tools: [none|grep/glob/read with reason]
+
 ### Patterns Discovered
 - [pattern]: [where used, how it works]
 
@@ -64,11 +85,25 @@ Explore the codebase to discover existing patterns, reusable components, technic
 
 ### Open Questions
 [Questions needing human input]
+
+### Interactive Planning
+- asked: yes|no
+- questions: [bounded questions asked, if any]
+- recommended answers: [your recommended answers]
+
+### Artifact Writes
+- allowed: yes|no
+- reason: [read-only by default|Change ID + explicit update artifacts]
+- files changed: [none|paths]
 ```
 
 ## Key Behaviors
 
 - Run multiple parallel searches for coverage
+- Loop until evidence saturates; do not stop after one search pass
+- Always report MCP usage or explicit fallback reason
+- Ask bounded planning questions when scope is unclear; do not guess
+- Treat artifact writes as opt-in only; read-only is the default
 - Focus on understanding, not implementation
 - Flag uncertainties rather than guessing
 - Use the question tool if critical information is missing

package/.opencode/agents/sdd-implementer.md

@@ -29,7 +29,16 @@ Execute approved SDD changes by following `tasks.md` in order and tracking progr
 5. **Use codebase-memory-mcp** — prefer `search_graph` and `get_code_snippet` over grep to understand existing patterns before implementing
 
 ### After Completion
-Spawn `sdd-verifier` as a child subagent to validate the implementation before reporting done.
+Spawn `sdd-verifier` as a child subagent to validate the implementation before reporting done. Treat verifier output as incomplete unless it includes `verified:` or `unverified:` plus exact commands/evidence.
+
+### Child Subagent Liveness Check
+
+If a spawned verifier returns no output, vague output, missing status labels, or no verification evidence:
+
+1. Mark current task `[BLOCKED: verifier stalled or incomplete evidence]` in `tasks.md` or `progress.md`.
+2. Run the most targeted verification command yourself if safe.
+3. Retry verifier once with a smaller scope.
+4. If still incomplete, report `unverified:` with exact missing evidence. Do not claim done.
 
 ## Blocker Handling
 
@@ -39,7 +48,7 @@ Spawn `sdd-verifier` as a child subagent to validate the implementation before r
   - Needs: [what's required to unblock]
 ```
 
-Use the question tool for ambiguous requirements or missing information.
+Do not use the question tool for ambiguous requirements during `/sdd-apply`. Mark the task blocked, state the exact missing artifact detail, and recommend `/sdd-explore` or `/sdd-propose` to resolve it.
 
 ## Output Format
 
@@ -69,3 +78,4 @@ Use the question tool for ambiguous requirements or missing information.
 - Preserve existing patterns in the codebase
 - Surface blockers early rather than getting stuck
 - Spawn `sdd-verifier` after completing implementation
+- Verify child subagent completion evidence before reporting success

package/.opencode/agents/sdd-orchestrator.md

@@ -37,6 +37,25 @@ Coordinate multiple SDD subagents when one change is too large for a single line
 4. Collect results and reconcile conflicts.
 5. Update the change artifacts with status, blockers, and verification evidence.
 
+## Subagent Liveness Contract
+
+Before spawning a subagent, write down expected outputs: task id, touched files, required status label, required verification command or evidence, and timeout/checkpoint expectation.
+
+Treat a subagent as stuck or failed when any of these happen:
+
+- No final response or tool activity is visible when the parent regains control.
+- Final response lacks `changed:`, `verified:`, `unverified:`, or `blocked:` label.
+- Claimed completion has no file paths, artifact updates, test output, or verifier evidence.
+- Expected `tasks.md`/`progress.md` checkpoint was not updated.
+- Verification command was skipped without `unverified:` reason.
+
+Recovery:
+
+1. Mark the task `[BLOCKED: subagent stalled or returned incomplete evidence]` in `tasks.md` or `progress.md`.
+2. Run one focused read-only verification pass yourself.
+3. Retry once with a smaller task payload, or switch to sequential execution.
+4. Report `blocked:` if retry still lacks evidence.
+
 ## Output
 
 Return a concise coordination summary with completed work, blocked work, file conflicts, and recommended next action.

package/.opencode/agents/sdd-planner.md

@@ -21,9 +21,11 @@ Transform a focused change request into reviewable SDD artifacts with requiremen
 ### 1. Understand the Specification
 - Read existing `proposal.md`, `spec.md`, `design.md`, or exploration findings when present
 - Identify functional/non-functional requirements and acceptance criteria
+- If scope is ambiguous, ask at most 3 bounded questions before writing artifacts. Each question must include your recommended answer.
 
 ### 2. Analyze Context
 - Review exploration findings from `sdd-explorer` or `/sdd-explore`
+- Treat `/sdd-explore` findings as advisory unless the user explicitly approved `update artifacts` for a Change ID
 - Use `codebase-memory-mcp` to understand existing architecture constraints via `get_architecture` and `query_graph`
 - Understand integration points
 

package/.opencode/agents/sdd-reviewer.md

@@ -22,7 +22,8 @@ Review code for spec compliance, security vulnerabilities, performance bottlenec
 
 ### 1. Context
 - Read `spec.md` for requirements, `plan.md` for intended approach
-- Identify files changed in implementation
+- Run `git diff --stat` and `git diff` to identify files changed in implementation
+- Confirm every changed file belongs to the intended scope from `tasks.md` and `design.md`
 
 ### 2. Security Review
 Check: input validation, auth/authz, secrets exposure, injection/XSS/CSRF, secure data handling.
@@ -36,6 +37,9 @@ Check: naming conventions, error handling, duplication, complex functions, test
 ### 5. Spec Compliance
 For each requirement: is it implemented, does it meet acceptance criteria, are edge cases handled?
 
+### 6. Diff Scope
+Compare the diff against the accepted artifacts. Report any unrelated file, broad rewrite, missing test, weakened assertion, or changed behavior outside scope before writing `verification.md`.
+
 ## Report Format
 
 ```markdown
@@ -58,6 +62,9 @@ For each requirement: is it implemented, does it meet acceptance criteria, are e
 ### Spec Compliance
 | Requirement | Status | Notes |
 
+### Diff Scope
+| File | In Scope? | Evidence |
+
 ### Positive Observations
 - [good patterns noticed]
 
@@ -68,6 +75,7 @@ For each requirement: is it implemented, does it meet acceptance criteria, are e
 ## Key Behaviors
 
 - Review objectively without personal preference bias
+- Use `git diff` as mandatory evidence before final readiness decision
 - Provide specific, actionable feedback with line references
 - Acknowledge good patterns, not just problems
 - Prioritize issues by impact

package/.opencode/agents/sdd-verifier.md

@@ -19,6 +19,7 @@ Verify that claimed work actually works: implementation exists, tests pass, spec
 
 - **chrome-devtools**: Use `chrome-devtools_navigate_page`, `chrome-devtools_take_screenshot`, `chrome-devtools_take_snapshot`, `chrome-devtools_list_console_messages` for visual/UI verification.
 - **codebase-memory-mcp**: Use `search_graph`, `trace_path`, `get_code_snippet` for structural code verification.
+- **git diff**: Mandatory scope check. Run `git diff --stat` and `git diff` before finalizing verification.
 - **exa_web_search_exa**: For validating external API patterns or library usage.
 
 ## Protocol
@@ -30,6 +31,7 @@ Verify that claimed work actually works: implementation exists, tests pass, spec
 ### 2. Verify Implementation
 For each claimed completion:
 - **File existence** — do expected files exist?
+- **Scope diff** — inspect `git diff --stat` and `git diff`; confirm changed files match `tasks.md` and `design.md`
 - **Code review** — use `codebase-memory-mcp` to verify code structure
 - **Integration** — is it properly connected?
 - **Error handling** — are edge cases covered?
@@ -50,6 +52,9 @@ For UI features:
 ### 5. Compare to Spec
 For each acceptance criterion, find implementing code and verify it meets the criterion.
 
+### 6. Stop Conditions
+Stop verification and report `FAIL` or `PARTIAL` when `git diff` shows unrelated files, tests fail, Test Spec rows are missing, assertions are weakened, mocks differ from the Mock Requirement, or evidence is insufficient.
+
 ## Report Format
 
 ```markdown
@@ -63,6 +68,10 @@ For each acceptance criterion, find implementing code and verify it meets the cr
 ### Verified Items
 | Task | Status | Evidence |
 
+### Diff Scope
+- `git diff --stat`: [summary]
+- Unintended changes: yes|no
+
 ### Spec Compliance
 | Requirement | Status | Notes |
 
@@ -83,6 +92,7 @@ For each acceptance criterion, find implementing code and verify it meets the cr
 ## Key Behaviors
 
 - Be skeptical — don't accept claims at face value
+- Always inspect `git diff` before final verdict
 - Test everything that can be tested
 - Check edge cases, not just happy paths
 - Report honestly even if news is bad

package/.opencode/commands/sdd-apply.md

@@ -15,7 +15,7 @@ Implement an existing change from `specs/active/<change-id>/`.
 
 - `specs/active/<change-id>/tasks.md` must exist.
 - Read `proposal.md`, `spec.md`, `design.md`, `tasks.md`, and `progress.md` if present before editing.
-- If artifacts are missing or contradictory, stop and ask for clarification.
+- If artifacts are missing or contradictory, stop with `blocked:` and state the exact artifact fix needed. Do not ask interactive clarification during `/sdd-apply`.
 
 ## Rules
 
@@ -27,6 +27,7 @@ Implement an existing change from `specs/active/<change-id>/`.
 - If implementation reveals a design issue, update the relevant artifact and explain the deviation.
 - Verify with the commands listed in `design.md` when available.
 - Stop on blockers. Do not silently skip tasks.
+- Remain execution-only. Do not ask planning questions; unresolved ambiguity becomes `blocked:` with a concrete next `/sdd-explore` or `/sdd-propose` recommendation.
 
 ## Test Integrity
 
@@ -51,6 +52,9 @@ Parallelize only when it is safe:
 - Never run parallel tasks that edit shared config, package files, schemas, generated files, migrations, or the same directory boundary unless the design explicitly marks it safe.
 - Spawn at most 3 implementer subagents per batch.
 - Each subagent must receive only its task, relevant artifact paths, expected files, and verification command.
+- Each subagent must return a completion contract: `changed:` or `blocked:`, plus `verified:` or `unverified:`, touched files, artifact updates, and exact test/verifier evidence.
+- After each subagent returns, verify it did not stall: check output labels, touched files, `tasks.md`/`progress.md` checkpoint, and verification evidence before starting the next batch.
+- If a subagent returns no output, vague output, missing labels, no artifact update, or no verification evidence, mark it `[BLOCKED: subagent stalled or incomplete evidence]`, retry once with a smaller payload, then continue sequentially or stop with `blocked:`.
 - Reconcile results before starting the next batch.
 
 If parallel execution is possible, ask once:

package/.opencode/commands/sdd-explore.md

@@ -17,7 +17,13 @@ Explore the request safely before committing to a change.
 - Do not edit source code.
 - Do not implement fixes.
 - Do not create a change unless the user explicitly asks.
-- Use codebase search first for project-specific questions.
+- Default mode is read-only: return a chat report or a temporary report outside the repo. Do not update SDD artifacts by default.
+- Artifact writes are allowed if and only if a Change ID is provided and, after interactive planning, the user explicitly says to `update artifacts`.
+- Use codebase-memory-mcp first for project-specific questions; fallback to grep/glob/read only if MCP is unavailable or insufficient, and report why.
+- Run MCP investigation as a loop: query → trace → read snippets → refine terms → stop only when a pass finds no new relevant evidence.
+- If the MCP loop exposes unclear scope, contradictory evidence, multiple plausible change boundaries, or missing domain terms, stop and ask at most 3 bounded questions before recommending a plan.
+- Each bounded question must include your recommended answer.
+- If artifact writes are allowed, write only exploration findings and open questions. Do not write implementation tasks.
 - Use web research only when external facts, libraries, or current docs matter.
 - If an explicit first token is a slug, treat it as the optional change id. Otherwise derive a short slug only for recommendations.
 - For project-specific exploration, cite real files, functions, routes, commands, or config paths.
@@ -52,11 +58,24 @@ Return a concise investigation report:
 
 [Recommended next step and why]
 
+## Interactive Planning
+
+- asked: yes|no
+- questions: [bounded questions asked, if any]
+- recommended answers: [your recommended answers]
+
 ## Evidence
 
+- MCP Status: used|unavailable|insufficient; passes: [number]; fallback: [none|reason]
 - `[path]`: [what was verified]
 - [source URL] - reliability: high|medium|low
 
+## Artifact Writes
+
+- allowed: yes|no
+- reason: [read-only by default|Change ID + explicit update artifacts]
+- files changed: [none|paths]
+
 ## Next Command
 
 Run `/sdd-propose <change-id> "<focused change>"` when ready.

package/.opencode/commands/sdd-propose.md

@@ -27,6 +27,7 @@ Create a compact, reviewable change plan. Stop before implementation.
 - Do not write implementation code.
 - Do not modify application source files.
 - Ask at most 3 clarifying questions only if the request is too ambiguous to plan safely.
+- Each clarifying question must be bounded and include your recommended answer.
 
 ## Sizing
 

package/.opencode/commands/sdd-ship.md

@@ -16,6 +16,7 @@ Verify a completed change before considering it ready.
 
 - Read `specs/active/<change-id>/proposal.md`, `spec.md`, `design.md`, and `tasks.md`.
 - Inspect the implementation against the artifacts.
+- Run `git diff --stat` and `git diff` before writing `verification.md`; use the diff to prove changed files match intended scope.
 - Run or recommend the project's relevant test, lint, typecheck, build, or browser verification commands.
 - Create or update `specs/active/<change-id>/verification.md`.
 - Do not make product code changes unless the user explicitly asks for fixes.
@@ -36,6 +37,7 @@ Perform a strict audit comparing the "Test Spec" tables in `tasks.md` against th
 - Tasks completed or intentionally deferred
 - Bugs, regressions, security risks, and missing tests
 - Verification evidence
+- Diff scope: no unrelated files, broad rewrites, weakened assertions, or hidden side effects
 - Release readiness
 
 ## Finalize Behavior
@@ -51,6 +53,7 @@ When the request includes `finalize`, `complete`, or `archive`:
 ## Evidence Requirements
 
 - Every finding must include a file path, command output, browser evidence, or explicit `assumption:` label.
+- `verification.md` must include `git diff --stat`, test command results, and any unrelated-change finding.
 - If no findings are found, state `No findings` and list residual risks.
 - Do not mark ready unless verification evidence exists.
 
@@ -67,6 +70,7 @@ Findings first, ordered by severity:
 
 ## Verification
 
+- diff: `git diff --stat` [passed|failed] - [scope notes]
 - passed: `[command]`
 - failed: `[command]` - [reason]
 - not run: `[command]` - [reason]

package/.opencode/plugins/sdd-doctor-checks.js

@@ -0,0 +1,21 @@
+import nodeFs from "node:fs";
+
+export function checkExploreReadonlyContract({ content }) {
+  const hasReadOnly = content.includes("read-only");
+  const hasArtifactGate = content.includes("update artifacts");
+
+  if (hasReadOnly && hasArtifactGate) {
+    return { status: "pass", detail: "Read-only contract and update artifacts gate present" };
+  }
+
+  if (hasReadOnly && !hasArtifactGate) {
+    return { status: "warn", detail: "Read-only contract present but missing update artifacts gate (see ADR-0001)" };
+  }
+
+  return { status: "fail", detail: "Missing read-only-by-default language in explore command" };
+}
+
+export function checkExploreCommandFile(filePath, { fs = nodeFs } = {}) {
+  const content = fs.readFileSync(filePath, "utf-8");
+  return checkExploreReadonlyContract({ content });
+}

package/.opencode/plugins/sdd-migration-symlinks.js

@@ -0,0 +1,82 @@
+import nodeFs from "node:fs";
+import path from "node:path";
+
+const SYMLINK_TARGETS = [
+  { dir: "commands", prefix: "sdd-" },
+  { dir: "agents", prefix: "sdd-" },
+  { dir: "rules", prefix: null },
+];
+
+const MIGRATION_MARKER = ".sdd-migrated-v030";
+
+function isOwnedTarget(linkTarget) {
+  return linkTarget.includes("sdd-multiagent-opencode") || linkTarget.includes("opencode-agent-rules");
+}
+
+export function migrateOldSymlinks({ configDir, now = () => new Date().toISOString(), fs = nodeFs }) {
+  const removed = [];
+  const ignored = [];
+  const errors = [];
+
+  if (fs.existsSync(path.join(configDir, MIGRATION_MARKER))) {
+    return {
+      skipped: true,
+      removed,
+      ignored,
+      errors: [],
+      markerWritten: false,
+    };
+  }
+
+  for (const { dir, prefix } of SYMLINK_TARGETS) {
+    const dirPath = path.join(configDir, dir);
+    if (!fs.existsSync(dirPath)) continue;
+
+    for (const entry of fs.readdirSync(dirPath, { withFileTypes: true })) {
+      const relativePath = path.join(dir, entry.name);
+
+      if (prefix && !entry.name.startsWith(prefix)) {
+        ignored.push(relativePath);
+        continue;
+      }
+
+      const fullPath = path.join(dirPath, entry.name);
+      try {
+        const stat = fs.lstatSync(fullPath);
+        if (!stat.isSymbolicLink()) {
+          ignored.push(relativePath);
+          continue;
+        }
+
+        const linkTarget = fs.readlinkSync(fullPath);
+        if (!isOwnedTarget(linkTarget)) {
+          ignored.push(relativePath);
+          continue;
+        }
+
+        fs.unlinkSync(fullPath);
+        removed.push(relativePath);
+      } catch (err) {
+        errors.push({ path: relativePath, reason: err.message });
+      }
+    }
+  }
+
+  let markerWritten = false;
+  if (removed.length > 0) {
+    try {
+      fs.writeFileSync(path.join(configDir, MIGRATION_MARKER), now());
+      markerWritten = true;
+    } catch (err) {
+      errors.push({ path: MIGRATION_MARKER, reason: err.message });
+    }
+  }
+
+  return {
+    skipped: false,
+    removed,
+    ignored,
+    errors,
+    markerWritten,
+  };
+}

package/.opencode/plugins/sdd-model-router.js

@@ -16,7 +16,7 @@ const DEFAULT_PLUGIN_CONFIG = {
     "sdd-explorer": { model: "opencode/deepseek-v4-flash-free" },
     "sdd-implementer": { model: "opencode/deepseek-v4-flash-free" },
     "sdd-verifier": { model: "opencode/qwen3.6-plus-free" },
-    "sdd-reviewer": { model: "opencode/minimax-m2.5-free" },
+    "sdd-reviewer": { model: "opencode/qwen3.6-plus-free" },
     "sdd-quick": { model: "opencode/qwen3.6-plus-free" },
   },
   reasoning: {

package/.opencode/plugins/sdd-register.js

@@ -1,8 +1,8 @@
-import fs from "node:fs";
 import path from "node:path";
 import { fileURLToPath } from "node:url";
 import sddAutoReasoning from "./sdd-auto-reasoning.js";
 import sddModelRouter from "./sdd-model-router.js";
+import { migrateOldSymlinks } from "./sdd-migration-symlinks.js";
 
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = path.dirname(__filename);
@@ -16,58 +16,17 @@ const globalConfigDir = path.join(
 
 // ─── Auto-Migration: Remove old symlinks from v0.2.x ────────────────────────
 
-function removeOldSymlinks() {
-  const MIGRATION_MARKER = ".sdd-migrated-v030";
-  const markerPath = path.join(globalConfigDir, MIGRATION_MARKER);
-
-  if (fs.existsSync(markerPath)) return;
-
-  const symlinkTargets = [
-    { dir: "commands", prefix: "sdd-" },
-    { dir: "agents", prefix: "sdd-" },
-    { dir: "rules", prefix: null },
-  ];
-
-  let migrated = false;
-
-  for (const { dir, prefix } of symlinkTargets) {
-    const dirPath = path.join(globalConfigDir, dir);
-    if (!fs.existsSync(dirPath)) continue;
-
-    try {
-      const entries = fs.readdirSync(dirPath, { withFileTypes: true });
-      for (const entry of entries) {
-        const fullPath = path.join(dirPath, entry.name);
-        try {
-          const stat = fs.lstatSync(fullPath);
-          if (!stat.isSymbolicLink()) continue;
-
-          if (prefix && !entry.name.startsWith(prefix)) continue;
-
-          const linkTarget = fs.readlinkSync(fullPath);
-          if (linkTarget.includes("sdd-multiagent-opencode") || linkTarget.includes("opencode-agent-rules")) {
-            fs.unlinkSync(fullPath);
-            migrated = true;
-          }
-        } catch {
-          // skip
-        }
-      }
-    } catch {
-      // skip
-    }
-  }
-
-  if (migrated) {
-    try {
-      fs.writeFileSync(markerPath, new Date().toISOString());
-    } catch {
-      // skip
-    }
+export function runSilentMigration(configDir = globalConfigDir) {
+  try {
+    migrateOldSymlinks({ configDir });
+  } catch {
+    // Plugin boot must stay silent and non-fatal.
   }
 }
 
-removeOldSymlinks();
+if (process.env.SDD_REGISTER_SKIP_AUTO_MIGRATION !== "1") {
+  runSilentMigration();
+}
 
 // ─── Agent Definitions (inlined to avoid sync I/O at boot) ───────────────────
 
@@ -111,6 +70,23 @@ Coordinate multiple SDD subagents when one change is too large for a single line
 4. Collect results and reconcile conflicts.
 5. Update the change artifacts with status, blockers, and verification evidence.
 
+## Subagent Liveness Contract
+
+Before spawning a subagent, write down expected outputs: task id, touched files, required status label, required verification command or evidence, and timeout/checkpoint expectation.
+
+Treat a subagent as stuck or failed when any of these happen:
+- No final response or tool activity is visible when the parent regains control.
+- Final response lacks changed:, verified:, unverified:, or blocked: label.
+- Claimed completion has no file paths, artifact updates, test output, or verifier evidence.
+- Expected tasks.md/progress.md checkpoint was not updated.
+- Verification command was skipped without unverified: reason.
+
+Recovery:
+1. Mark the task [BLOCKED: subagent stalled or returned incomplete evidence] in tasks.md or progress.md.
+2. Run one focused read-only verification pass yourself.
+3. Retry once with a smaller task payload, or switch to sequential execution.
+4. Report blocked: if retry still lacks evidence.
+
 ## Output
 
 Return a concise coordination summary with completed work, blocked work, file conflicts, and recommended next action.`,
@@ -140,9 +116,11 @@ Transform a focused change request into reviewable SDD artifacts with requiremen
 ### 1. Understand the Specification
 - Read existing proposal.md, spec.md, design.md, or exploration findings when present
 - Identify functional/non-functional requirements and acceptance criteria
+- If scope is ambiguous, ask at most 3 bounded questions before writing artifacts. Each question must include your recommended answer.
 
 ### 2. Analyze Context
 - Review exploration findings from sdd-explorer or /sdd-explore
+- Treat /sdd-explore findings as advisory unless the user explicitly approved update artifacts for a Change ID
 - Use codebase-memory-mcp to understand existing architecture constraints via get_architecture and query_graph
 - Understand integration points
 
@@ -201,39 +179,61 @@ Explore the codebase to discover existing patterns, reusable components, technic
 
 ## Tools
 
-- codebase-memory-mcp: Use search_graph for function/class discovery, trace_path for call chains, get_code_snippet for reading source, query_graph for complex patterns. Prefer these over grep/glob.
+- codebase-memory-mcp: Mandatory first-line toolset for project code. You MUST use it before grep/glob/read. Use search_graph for function/class discovery, get_architecture for structure, trace_path for call chains, get_code_snippet for source, and query_graph for complex patterns.
 - exa_web_search_exa: For external pattern research and documentation lookup.
 - webfetch: For reading specific URLs found during research.
 
+If codebase-memory-mcp is unavailable, say so in MCP Status, then fall back to grep/glob/read. Do not silently skip MCP.
+
 ## Strategy
 
-### Phase 1: Breadth-First Discovery
-1. Use search_graph with natural language queries for similar functionality
-2. Identify relevant directories and modules via get_architecture
-3. Map dependency graph via query_graph for affected areas
+### MCP-First Investigation Loop
+
+Repeat this loop until evidence saturates, with a minimum of 2 passes and a maximum of 5 passes:
+1. Query — run 2-4 codebase-memory searches (search_graph, get_architecture, or query_graph) from different terms/angles.
+2. Trace — use trace_path for key functions/classes/routes found in Query.
+3. Read — use get_code_snippet for the exact symbols that explain behavior.
+4. Refine — derive new search terms from real names discovered in snippets.
+5. Stop Check — stop only when the last pass finds no new relevant symbols, files, routes, constraints, risks, or search terms.
+
+Fallback grep/glob/read is allowed only after MCP miss/unavailable, and must cite why MCP was insufficient. If MCP is unavailable, stop after one fallback pass unless user explicitly asks for deeper exploration.
 
-### Phase 2: Depth Investigation
-1. Use get_code_snippet to read key files from Phase 1
-2. Understand interfaces and contracts
-3. Document patterns and conventions
+### Interactive Planning Gate
 
-### Phase 3: External Context
-1. Check related documentation via exa_web_search_exa
-2. Review existing specs in specs/
+If the MCP loop reveals unclear scope, contradictory evidence, multiple plausible change boundaries, or missing domain terms, stop exploration and ask bounded questions before making a recommendation or updating artifacts. Ask at most 3 questions. Each question must include your recommended answer.
+
+Default /sdd-explore is read-only: return a chat report or write a temporary report outside the repo only. Do not create or update proposal.md, spec.md, design.md, tasks.md, progress.md, or verification.md by default.
+
+Artifact writes are allowed if and only if both conditions are true:
+1. The request provides an existing Change ID.
+2. After interactive planning, the user explicitly says to update artifacts.
+
+If allowed to update artifacts, write only exploration findings and open questions. Do not write implementation tasks.
+
+### External Context
+
+Use exa_web_search_exa only when external facts, libraries, or current docs matter. Review existing specs in specs/ when request touches active SDD work.
 
 ## Output Format
 
 Return findings as:
 - Relevant Existing Code: [file path]: [what it does, why relevant]
+- MCP Status: codebase-memory-mcp used|unavailable|insufficient; passes: [number]; fallback tools: [none|grep/glob/read with reason]
 - Patterns Discovered: [pattern]: [where used, how it works]
 - Reusable Components: [component]: [how to leverage]
 - Technical Constraints: [constraint]: [impact on approach]
 - Recommended Approach: [Technical direction based on findings]
 - Open Questions: [Questions needing human input]
+- Interactive Planning: asked yes|no; questions; recommended answers
+- Artifact Writes: allowed yes|no; reason; files changed
 
 ## Key Behaviors
 
 - Run multiple parallel searches for coverage
+- Loop until evidence saturates; do not stop after one search pass
+- Always report MCP usage or explicit fallback reason
+- Ask bounded planning questions when scope is unclear; do not guess
+- Treat artifact writes as opt-in only; read-only is the default
 - Focus on understanding, not implementation
 - Flag uncertainties rather than guessing
 - Use the question tool if critical information is missing`,
@@ -271,7 +271,15 @@ Execute approved SDD changes by following tasks.md in order and tracking progres
 5. Use codebase-memory-mcp — prefer search_graph and get_code_snippet over grep to understand existing patterns before implementing
 
 ### After Completion
-Spawn sdd-verifier as a child subagent to validate the implementation before reporting done.
+Spawn sdd-verifier as a child subagent to validate the implementation before reporting done. Treat verifier output as incomplete unless it includes verified: or unverified: plus exact commands/evidence.
+
+### Child Subagent Liveness Check
+
+If a spawned verifier returns no output, vague output, missing status labels, or no verification evidence:
+1. Mark current task [BLOCKED: verifier stalled or incomplete evidence] in tasks.md or progress.md.
+2. Run the most targeted verification command yourself if safe.
+3. Retry verifier once with a smaller scope.
+4. If still incomplete, report unverified: with exact missing evidence. Do not claim done.
 
 ## Blocker Handling
 
@@ -279,7 +287,7 @@ Spawn sdd-verifier as a child subagent to validate the implementation before rep
   - Attempted: [what you tried]
   - Needs: [what's required to unblock]
 
-Use the question tool for ambiguous requirements or missing information.
+Do not use the question tool for ambiguous requirements during /sdd-apply. Mark the task blocked, state the exact missing artifact detail, and recommend /sdd-explore or /sdd-propose to resolve it.
 
 ## Key Behaviors
 
@@ -287,7 +295,8 @@ Use the question tool for ambiguous requirements or missing information.
 - Always update tasks.md checkboxes immediately
 - Preserve existing patterns in the codebase
 - Surface blockers early rather than getting stuck
-- Spawn sdd-verifier after completing implementation`,
+- Spawn sdd-verifier after completing implementation
+- Verify child subagent completion evidence before reporting success`,
   },
 
   "sdd-verifier": {
@@ -311,6 +320,7 @@ Verify that claimed work actually works: implementation exists, tests pass, spec
 
 - chrome-devtools: Use navigate_page, take_screenshot, take_snapshot, list_console_messages for visual/UI verification.
 - codebase-memory-mcp: Use search_graph, trace_path, get_code_snippet for structural code verification.
+- git diff: Mandatory scope check. Run git diff --stat and git diff before finalizing verification.
 - exa_web_search_exa: For validating external API patterns or library usage.
 
 ## Protocol
@@ -322,6 +332,7 @@ Verify that claimed work actually works: implementation exists, tests pass, spec
 ### 2. Verify Implementation
 For each claimed completion:
 - File existence — do expected files exist?
+- Scope diff — inspect git diff --stat and git diff; confirm changed files match tasks.md and design.md
 - Code review — use codebase-memory-mcp to verify code structure
 - Integration — is it properly connected?
 - Error handling — are edge cases covered?
@@ -341,9 +352,13 @@ For UI features:
 ### 5. Compare to Spec
 For each acceptance criterion, find implementing code and verify it meets the criterion.
 
+### 6. Stop Conditions
+Stop verification and report FAIL or PARTIAL when git diff shows unrelated files, tests fail, Test Spec rows are missing, assertions are weakened, mocks differ from the Mock Requirement, or evidence is insufficient.
+
 ## Key Behaviors
 
 - Be skeptical — don't accept claims at face value
+- Always inspect git diff before final verdict
 - Test everything that can be tested
 - Check edge cases, not just happy paths
 - Report honestly even if news is bad
@@ -375,7 +390,8 @@ Review code for spec compliance, security vulnerabilities, performance bottlenec
 
 ### 1. Context
 - Read spec.md for requirements, plan.md for intended approach
-- Identify files changed in implementation
+- Run git diff --stat and git diff to identify files changed in implementation
+- Confirm every changed file belongs to the intended scope from tasks.md and design.md
 
 ### 2. Security Review
 Check: input validation, auth/authz, secrets exposure, injection/XSS/CSRF, secure data handling.
@@ -389,9 +405,13 @@ Check: naming conventions, error handling, duplication, complex functions, test
 ### 5. Spec Compliance
 For each requirement: is it implemented, does it meet acceptance criteria, are edge cases handled?
 
+### 6. Diff Scope
+Compare the diff against the accepted artifacts. Report any unrelated file, broad rewrite, missing test, weakened assertion, or changed behavior outside scope before writing verification.md.
+
 ## Key Behaviors
 
 - Review objectively without personal preference bias
+- Use git diff as mandatory evidence before final readiness decision
 - Provide specific, actionable feedback with line references
 - Acknowledge good patterns, not just problems
 - Prioritize issues by impact`,
@@ -549,7 +569,13 @@ Next: run /sdd-propose "<your first feature>" to start building.`,
 - Do not edit source code.
 - Do not implement fixes.
 - Do not create a change unless the user explicitly asks.
-- Use codebase search first for project-specific questions.
+- Default mode is read-only: return a chat report or a temporary report outside the repo. Do not update SDD artifacts by default.
+- Artifact writes are allowed if and only if a Change ID is provided and, after interactive planning, the user explicitly says to update artifacts.
+- Use codebase-memory-mcp first for project-specific questions; fallback to grep/glob/read only if MCP is unavailable or insufficient, and report why.
+- Run MCP investigation as a loop: query -> trace -> read snippets -> refine terms -> stop only when a pass finds no new relevant evidence.
+- If the MCP loop exposes unclear scope, contradictory evidence, multiple plausible change boundaries, or missing domain terms, stop and ask at most 3 bounded questions before recommending a plan.
+- Each bounded question must include your recommended answer.
+- If artifact writes are allowed, write only exploration findings and open questions. Do not write implementation tasks.
 - Use web research only when external facts, libraries, or current docs matter.
 - If an explicit first token is a slug, treat it as the optional change id.
 - For project-specific exploration, cite real files, functions, routes, commands, or config paths.
@@ -569,7 +595,9 @@ Return a concise investigation report:
 - Findings with real file paths
 - Options with tradeoffs
 - Recommendation
-- Evidence (file paths + source URLs)
+- Interactive Planning status with bounded questions and recommended answers
+- Evidence (MCP Status + file paths + source URLs)
+- Artifact Writes status with reason and changed paths
 - Next Command: /sdd-propose <change-id> "<focused change>"`,
   },
 
@@ -590,7 +618,7 @@ Return a concise investigation report:
 - Create artifacts in specs/active/<change-id>/.
 - Generate: proposal.md, spec.md, design.md, tasks.md (and progress.md for large changes).
 - Do not write implementation code.
-- Ask at most 3 clarifying questions only if too ambiguous.
+- Ask at most 3 clarifying questions only if too ambiguous. Each clarifying question must be bounded and include your recommended answer.
 
 ## Sizing
 
@@ -641,7 +669,7 @@ Next: review the artifacts, then run /sdd-apply <change-id>.`,
 
 - specs/active/<change-id>/tasks.md must exist.
 - Read proposal.md, spec.md, design.md, tasks.md, and progress.md if present.
-- If artifacts are missing or contradictory, stop and ask.
+- If artifacts are missing or contradictory, stop with blocked: and state the exact artifact fix needed. Do not ask interactive clarification during /sdd-apply.
 
 ## Rules
 
@@ -650,6 +678,7 @@ Next: review the artifacts, then run /sdd-apply <change-id>.`,
 - Do not broaden scope beyond accepted artifacts.
 - Update tasks.md checkboxes as work completes.
 - Stop on blockers. Do not silently skip tasks.
+- Remain execution-only. Do not ask planning questions; unresolved ambiguity becomes blocked: with a concrete next /sdd-explore or /sdd-propose recommendation.
 
 ## Test Integrity
 
@@ -667,6 +696,12 @@ Next: review the artifacts, then run /sdd-apply <change-id>.`,
 
 Parallelize only when touched files do not overlap. Spawn at most 3 implementer subagents per batch.
 
+Each subagent must return a completion contract: changed: or blocked:, plus verified: or unverified:, touched files, artifact updates, and exact test/verifier evidence.
+
+After each subagent returns, verify it did not stall: check output labels, touched files, tasks.md/progress.md checkpoint, and verification evidence before starting the next batch.
+
+If a subagent returns no output, vague output, missing labels, no artifact update, or no verification evidence, mark it [BLOCKED: subagent stalled or incomplete evidence], retry once with a smaller payload, then continue sequentially or stop with blocked:.
+
 ## Workflow
 
 1. Summarize scope in 3-6 bullets.
@@ -699,6 +734,7 @@ Next: run /sdd-ship <change-id> for final review.`,
 
 - Read specs/active/<change-id>/ artifacts.
 - Inspect implementation against artifacts.
+- Run git diff --stat and git diff before writing verification.md; use the diff to prove changed files match intended scope.
 - Run or recommend relevant test, lint, typecheck, build commands.
 - Create or update verification.md.
 - Do not make product code changes unless explicitly asked.
@@ -717,6 +753,7 @@ Strict audit comparing Test Spec tables in tasks.md against actual test files:
 - Tasks completed or intentionally deferred
 - Bugs, regressions, security risks, missing tests
 - Verification evidence
+- Diff scope: no unrelated files, broad rewrites, weakened assertions, or hidden side effects
 - Release readiness
 
 ## Finalize Behavior
@@ -728,10 +765,11 @@ When request includes "finalize", "complete", or "archive":
 ## Evidence Requirements
 
 - Every finding must include file path, command output, browser evidence, or "assumption:" label.
+- verification.md must include git diff --stat, test command results, and any unrelated-change finding.
 
 ## Output
 
-Findings first (critical, major, minor), Verification results, Decision (ready: yes|no).`,
+Findings first (critical, major, minor), Verification results including git diff --stat and test commands, Decision (ready: yes|no).`,
   },
 
   "sdd-quick": {

package/README.md

@@ -216,9 +216,9 @@ Models available at no cost via OpenCode Zen. Run `opencode models opencode | gr
 | Model | ID | Best For | Notes |
 |-------|----|----------|-------|
 | DeepSeek V4 Flash Free | `opencode/deepseek-v4-flash-free` | Explorer, Implementer | Code generation |
-| MiniMax M2.5 Free | `opencode/minimax-m2.5-free` | Reviewer, Compaction | Structured output |
-| Nemotron 3 Super Free | `opencode/nemotron-3-super-free` | Explorer | NVIDIA model, 1M context |
-| Qwen3.6 Plus Free | `opencode/qwen3.6-plus-free` | Verifier, General, Quick fix | Multimodal support |
+| MiniMax M2.5 Free | `opencode/minimax-m2.5-free` | Fallback only | Currently unavailable in some regions/accounts |
+| Nemotron 3 Super Free | `opencode/nemotron-3-super-free` | Explorer, Compaction | NVIDIA model, 1M context |
+| Qwen3.6 Plus Free | `opencode/qwen3.6-plus-free` | Reviewer, Verifier, General, Quick fix | Multimodal support |
 
 ⚠️ Free models are limited-time offers and may be removed or rotated without notice. Not recommended for production SDD workflows. Use `opencode models opencode | grep "free"` to verify what's currently available.
 
@@ -241,7 +241,7 @@ Recommended starting configuration (orchestrator/planner use OpenAI GPT 5.5, oth
     "sdd-explorer": { "model": "opencode/deepseek-v4-flash-free" },
     "sdd-implementer": { "model": "opencode/deepseek-v4-flash-free" },
     "sdd-verifier": { "model": "opencode/qwen3.6-plus-free" },
-    "sdd-reviewer": { "model": "opencode/minimax-m2.5-free" },
+    "sdd-reviewer": { "model": "opencode/qwen3.6-plus-free" },
     "sdd-quick": { "model": "opencode/qwen3.6-plus-free" }
   },
   "reasoning": {
@@ -280,7 +280,7 @@ Recommended starting configuration (orchestrator/planner use OpenAI GPT 5.5, oth
     "sdd-explorer": { "model": "opencode/deepseek-v4-flash-free" },
     "sdd-implementer": { "model": "opencode/deepseek-v4-flash-free" },
     "sdd-verifier": { "model": "opencode-go/kimi-k2.6" },
-    "sdd-reviewer": { "model": "opencode/minimax-m2.5-free" },
+    "sdd-reviewer": { "model": "opencode/qwen3.6-plus-free" },
     "sdd-quick": { "model": "opencode-go/qwen3.6-plus" }
   }
 }
@@ -292,7 +292,7 @@ Recommended starting configuration (orchestrator/planner use OpenAI GPT 5.5, oth
 - **Explorer** → DeepSeek free: fast readonly exploration, token-efficient
 - **Implementer** → DeepSeek free: code generation, handles high token usage
 - **Verifier** → Qwen3.6 Plus free: multimodal for Chrome DevTools screenshots
-- **Reviewer** → MiniMax M2.5 free: structured code review output
+- **Reviewer** → Qwen3.6 Plus free: available free-tier review model
 - **Quick** → Qwen3.6 Plus free: minimal prompt for small cosmetic/config edits (~200 tokens)
 
 `.opencode/plugins/sdd-model-router.js` reads `~/.config/opencode/sdd-multiagent-opencode.json` at OpenCode startup and applies the model settings. **Restart OpenCode after editing it.**

package/bin/sdd-opencode.js

@@ -2,8 +2,10 @@
 
 import fs from "node:fs";
 import path from "node:path";
-import { fileURLToPath } from "node:url";
+import { fileURLToPath, pathToFileURL } from "node:url";
 import { execSync } from "node:child_process";
+import { migrateOldSymlinks } from "../.opencode/plugins/sdd-migration-symlinks.js";
+import { checkExploreCommandFile } from "../.opencode/plugins/sdd-doctor-checks.js";
 
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = path.dirname(__filename);
@@ -556,7 +558,7 @@ async function runInit(args) {
 
 // ─── Doctor Command ──────────────────────────────────────────────────────────
 
-async function runDoctor(args) {
+export async function runDoctor(args, { exploreCommandPath } = {}) {
   const targetRoot = process.cwd();
   const results = { pass: 0, warn: 0, fail: 0, checks: [] };
 
@@ -625,6 +627,16 @@ async function runDoctor(args) {
 
   report("L0", "orphaned symlinks", orphanedCount === 0 ? "pass" : "warn", orphanedCount > 0 ? `${orphanedCount} old symlinks found — run "sdd-opencode migrate"` : "clean");
 
+  // L0: SDD Explore read-only contract
+  const exploreSourcePath = exploreCommandPath || path.join(packageRoot, ".opencode/commands/sdd-explore.md");
+  let exploreResult;
+  try {
+    exploreResult = checkExploreCommandFile(exploreSourcePath);
+  } catch {
+    exploreResult = { status: "fail", detail: "Cannot read explore command source" };
+  }
+  report("L0", "sdd-explore contract", exploreResult.status, exploreResult.detail);
+
   // L1: Plugin registration count
   console.log("\nL1: Plugin Registration");
 
@@ -728,79 +740,54 @@ function runWarm() {
 
 // ─── Migrate Command ─────────────────────────────────────────────────────────
 
-function runMigrate() {
-  console.log("\nMigrating from v0.2.x symlink-based installation...\n");
+export function runMigrate({ configDir = globalConfigDir, log = console.log, now } = {}) {
+  log("\nMigrating from v0.2.x symlink-based installation...\n");
 
-  const MIGRATION_MARKER = ".sdd-migrated-v030";
-  const markerPath = path.join(globalConfigDir, MIGRATION_MARKER);
+  const result = migrateOldSymlinks({ configDir, now });
 
-  if (fs.existsSync(markerPath)) {
-    console.log("Migration already completed. No action needed.");
-    return;
+  if (result.skipped) {
+    log("Migration already completed. No action needed.");
+    return result;
   }
 
-  const symlinkTargets = [
-    { dir: "commands", prefix: "sdd-" },
-    { dir: "agents", prefix: "sdd-" },
-    { dir: "rules", prefix: null },
-  ];
-
-  let removed = 0;
-
-  for (const { dir, prefix } of symlinkTargets) {
-    const dirPath = path.join(globalConfigDir, dir);
-    if (!fs.existsSync(dirPath)) continue;
-
-    for (const entry of fs.readdirSync(dirPath, { withFileTypes: true })) {
-      const fullPath = path.join(dirPath, entry.name);
-      try {
-        const stat = fs.lstatSync(fullPath);
-        if (!stat.isSymbolicLink()) continue;
-        if (prefix && !entry.name.startsWith(prefix)) continue;
-
-        const linkTarget = fs.readlinkSync(fullPath);
-        if (linkTarget.includes("sdd-multiagent-opencode") || linkTarget.includes("opencode-agent-rules")) {
-          fs.unlinkSync(fullPath);
-          console.log(`  Removed: ${path.join(dir, entry.name)}`);
-          removed++;
-        }
-      } catch {
-        // skip
-      }
-    }
+  for (const removedPath of result.removed) {
+    log(`  Removed: ${removedPath}`);
   }
 
-  if (removed > 0) {
-    try {
-      fs.writeFileSync(markerPath, new Date().toISOString());
-    } catch {
-      // skip
-    }
-    console.log(`\nMigration complete: ${removed} old symlinks removed.`);
-    console.log("Plugin-native registration is now active.");
+  if (result.removed.length > 0) {
+    log(`\nMigration complete: ${result.removed.length} old symlinks removed.`);
+    log("Plugin-native registration is now active.");
   } else {
-    console.log("No old symlinks found. Nothing to migrate.");
+    log("No old symlinks found. Nothing to migrate.");
   }
+
+  return result;
 }
 
 // ─── Main ────────────────────────────────────────────────────────────────────
 
-const args = parseArgs(process.argv);
-
-if (args.command === "help") {
-  usage();
-} else if (args.command === "init") {
-  runInit(args);
-} else if (args.command === "doctor") {
-  runDoctor(args);
-} else if (args.command === "warm") {
-  runWarm();
-} else if (args.command === "migrate") {
-  runMigrate();
-} else if (args.command === "test") {
-  console.log("Smoke test placeholder — plugin loads correctly.");
-} else {
-  console.error(`Unknown command: ${args.command}`);
-  usage();
-  process.exit(1);
+function main(argv = process.argv) {
+  const args = parseArgs(argv);
+
+  if (args.command === "help") {
+    usage();
+  } else if (args.command === "init") {
+    runInit(args);
+  } else if (args.command === "doctor") {
+    runDoctor(args);
+  } else if (args.command === "warm") {
+    runWarm();
+  } else if (args.command === "migrate") {
+    runMigrate();
+  } else if (args.command === "test") {
+    console.log("Smoke test placeholder — plugin loads correctly.");
+  } else {
+    console.error(`Unknown command: ${args.command}`);
+    usage();
+    process.exit(1);
+  }
+}
+
+if (process.argv[1] && import.meta.url === pathToFileURL(process.argv[1]).href) {
+  main();
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tudeorangbiasa/sdd-multiagent-opencode",
-  "version": "0.4.1",
+  "version": "0.5.0",
   "description": "Spec-Driven Development workflow kit for OpenCode with 5 core commands, multi-agent support, CLI wrappers, and configurable model routing",
   "type": "module",
   "main": ".opencode/plugins/sdd-register.js",

package/sdd-multiagent-opencode.json

@@ -18,7 +18,7 @@
       "model": "opencode/qwen3.6-plus-free"
     },
     "sdd-reviewer": {
-      "model": "opencode/minimax-m2.5-free"
+      "model": "opencode/qwen3.6-plus-free"
     },
     "sdd-quick": {
       "model": "opencode/qwen3.6-plus-free"

package/vendor/opencode-agent-rules/opencode-agent-rules.json

@@ -1,7 +1,7 @@
 {
   "agent": {
     "compaction": {
-      "model": "opencode/minimax-m2.5-free",
+      "model": "opencode/nemotron-3-super-free",
       "temperature": 0.1
     }
   }