agentsys 5.0.3 → 5.1.0

package/adapters/opencode/commands/consult.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: Consult another AI CLI tool for a second opinion. Use when you want to cross-check ideas, get alternative approaches, or validate decisions with Gemini, Codex, Claude, OpenCode, or Copilot.
 agent: general
@@ -12,67 +11,94 @@ agent: general
 
 # /consult - Cross-Tool AI Consultation
 
-You are executing the /consult command. Your job is to consult another AI CLI tool, get its response, and present the results to the user.
+You are executing the /consult command. Your job is to parse the user's request (natural language or flags), resolve missing parameters interactively, and execute the consultation.
 
 ## Constraints
 
 - NEVER expose API keys in commands or output
 - NEVER run with permission-bypassing flags (`--dangerously-skip-permissions`, `bypassPermissions`)
-- MUST use safe-mode defaults (`-a suggest` for Codex, `--allowedTools "Read,Glob,Grep"` for Claude)
+- MUST use safe-mode defaults (`--allowedTools "Read,Glob,Grep"` for Claude, `-c model_reasoning_effort` for Codex)
 - MUST enforce 120s timeout on all tool executions
-- MUST validate `--tool` against allow-list: gemini, codex, claude, opencode, copilot (reject all others)
+- MUST validate tool names against allow-list: gemini, codex, claude, opencode, copilot (reject all others)
 - MUST validate `--context=file=PATH` is within the project directory (reject absolute paths outside cwd)
 - MUST quote all user-provided values in shell commands to prevent injection
 - NEVER execute tools the user has not explicitly requested
 
-## Arguments
+## Execution
 
-Parse from $ARGUMENTS:
+### Phase 1: Parse Input (Flags + Natural Language)
 
-- **question**: What to ask the consulted tool (required unless --continue)
-- **--tool**: Target tool: `gemini`, `codex`, `claude`, `opencode`, `copilot` (interactive picker if omitted)
-- **--effort**: Thinking effort: `low`, `medium`, `high`, `max` (interactive picker if omitted)
-- **--model**: Specific model name (interactive picker if omitted). Free text.
-- **--context**: Auto-include context: `diff` (git diff), `file=PATH` (attach specific file), `none` (default)
-- **--continue**: Continue last consultation session, or `--continue=SESSION_ID` for specific session
+Parse `$ARGUMENTS` using both explicit flags and natural language extraction. Flags always take priority over NLP when both provide the same parameter.
 
-## Execution
+#### Step 1a: Extract explicit flags
+
+Look for and remove these flags from `$ARGUMENTS`:
+
+1. `--tool=VALUE` or `--tool VALUE` where VALUE is one of: gemini, codex, claude, opencode, copilot
+2. `--effort=VALUE` or `--effort VALUE` where VALUE is one of: low, medium, high, max
+3. `--model=VALUE` or `--model VALUE` (any string, including quoted)
+4. `--context=VALUE` where VALUE is: diff, file=PATH, or none
+5. `--continue` (optionally `--continue=SESSION_ID`)
+6. `--count=N` where N is 1-5
+
+Remove all matched flags and their values from `$ARGUMENTS`.
+
+#### Step 1b: Natural language extraction (on remaining text)
+
+After removing flags, parse the remaining text for these patterns:
 
-### Phase 1: Parse Arguments
+**Tool extraction** (case-insensitive):
+- "with {tool}" (e.g., "with codex") -> tool
+- "ask {tool}" (e.g., "ask gemini") -> tool
+- "consult {tool}" -> tool
+- "{tool} about" (e.g., "codex about") -> tool
+- Tool names: claude, gemini, codex, opencode, copilot
 
-Extract these values from `$ARGUMENTS`:
+**Count extraction**:
+- "ask {N} {tool}" (e.g., "ask 3 codex") -> count=N, tool
+- "{N} {tool}" (e.g., "3 codex") -> count=N, tool
+- "{N} instances" -> count=N
+- "few instances" / "multiple" / "several" -> count=ambiguous (ask user in Phase 2)
 
-1. Look for `--tool=VALUE` or `--tool VALUE` where VALUE MUST be one of: gemini, codex, claude, opencode, copilot (reject others)
-2. Look for `--effort=VALUE` or `--effort VALUE` where VALUE MUST be one of: low, medium, high, max
-3. Look for `--model=VALUE` or `--model VALUE` (any string, including quoted strings like `"my model"`)
-4. Look for `--context=VALUE` where VALUE is: diff, file=PATH, or none
-5. Look for `--continue` (optionally `--continue=SESSION_ID`)
-6. Remove all matched flags (including their values) from `$ARGUMENTS`. Handle quoted flag values (e.g., `--model "gpt 4"`) by removing the entire quoted string. Everything remaining is the **question**.
+**Count validation**: After extracting count (from flags or NLP), validate: 1 <= count <= 5. If count < 1 or count > 5, show `[ERROR] Instance count must be 1-5. Got: {count}` and stop.
 
-If no question text and no `--continue` flag found, show:
+**Effort extraction**:
+- "quick" / "fast" / "brief" -> effort=low
+- "thorough" / "deep" / "carefully" / "detailed" -> effort=high
+- "maximum" / "max effort" / "exhaustive" -> effort=max
+
+**Question extraction**:
+- Text after "about" is the question (e.g., "with codex about my auth approach" -> question="my auth approach")
+- If no "about" pattern, everything remaining after removing tool/count/effort markers is the question
+
+**Precedence rule**: Flags from Step 1a always override NLP from Step 1b.
+
+If no question text and no `--continue` flag found after both steps:
 ```
-[ERROR] Usage: /consult "your question" [--tool=gemini|codex|claude|opencode|copilot] [--effort=low|medium|high|max]
+[ERROR] Usage: /consult "your question" or /consult with gemini about your question
 ```
 
-### Phase 2: Interactive Parameter Selection
+### Phase 2: Interactive Parameter Resolution
 
-MUST resolve ALL missing parameters interactively before Phase 3. ONLY skip this phase if ALL of --tool, --effort, AND --model are explicitly provided by the user in $ARGUMENTS. Do NOT silently default any parameter.
+MUST resolve ALL missing parameters interactively. ONLY skip this phase if ALL required params (tool, effort, model) are resolved AND either a question exists or --continue is present. Do NOT silently default any parameter.
 
 #### Step 2a: Handle --continue
 
+**Note:** `--continue` and `--count > 1` are mutually exclusive. Session resume applies to a single tool session. If both are present, show `[ERROR] Cannot use --continue with --count > 1. Use --continue for single session resume.` and stop.
+
 If `--continue` is present:
 1. Read the session file at `{AI_STATE_DIR}/consult/last-session.json`
 
    Platform state directory:
-   - Claude Code: `.opencode/`
+   - Claude Code: `.claude/`
    - OpenCode: `.opencode/`
    - Codex CLI: `.codex/`
 2. If the file exists, restore the saved tool, session_id, and model from it
 3. If the file does not exist, show `[WARN] No previous session found` and proceed as a fresh consultation
 
-#### Step 2b: Batch Selection (tool + effort)
+#### Step 2b: Detect installed tools
 
-First, detect which tools are installed by running all 5 checks **in parallel** via Bash:
+Run all 5 checks **in parallel** via Bash:
 
 - `where.exe <tool> 2>nul && echo FOUND || echo NOTFOUND` (Windows)
 - `which <tool> 2>/dev/null && echo FOUND || echo NOTFOUND` (Unix)
@@ -81,12 +107,14 @@ Check for: claude, gemini, codex, opencode, copilot.
 
 If zero tools are installed: `[ERROR] No AI CLI tools found. Install at least one: npm i -g @anthropic-ai/claude-code, npm i -g @openai/codex, npm i -g opencode-ai`
 
-Then use a SINGLE AskUserQuestion call to ask all missing parameters at once. Include only the questions for parameters NOT already provided in $ARGUMENTS:
+#### Step 2c: Batch selection for missing params
+
+Use a SINGLE AskUserQuestion call to ask all missing parameters at once. Include ONLY questions for parameters NOT already resolved from Phase 1:
 
 ```
 AskUserQuestion:
   questions:
-    - header: "AI Tool"                          # SKIP if --tool provided
+    - header: "AI Tool"                          # SKIP if tool resolved
       question: "Which AI tool should I consult?"
       multiSelect: false
       options (only if installed):
@@ -96,7 +124,7 @@ AskUserQuestion:
         - label: "OpenCode"     description: "Flexible model choice"
         - label: "Copilot"      description: "GitHub-integrated AI"
 
-    - header: "Effort"                           # SKIP if --effort provided
+    - header: "Effort"                           # SKIP if effort resolved
       question: "What thinking effort level?"
       multiSelect: false
       options:
@@ -104,16 +132,29 @@ AskUserQuestion:
         - label: "Low"                   description: "Fast, minimal reasoning"
         - label: "High"                  description: "Thorough analysis"
         - label: "Max"                   description: "Maximum reasoning depth"
+
+    - header: "Instances"                        # SKIP if count resolved or not hinted
+      question: "How many parallel consultations?"
+      multiSelect: false
+      options:
+        - label: "1 (Single)"             description: "Standard single consultation"
+        - label: "2 (Compare)"            description: "Two responses to compare"
+        - label: "3 (Panel)"              description: "Three perspectives"
+        - label: "5 (Full spread)"        description: "Five diverse perspectives"
 ```
 
-Map tool choice to lowercase: "Claude" -> "claude", "Codex" -> "codex", etc.
-Map effort choice: "Medium (Recommended)" -> "medium", "Low" -> "low", "High" -> "high", "Max" -> "max".
+ONLY show the Instances question if:
+- The user explicitly mentioned multiple instances (e.g., "few", "multiple", "several")
+- The count was set but ambiguous
+Do NOT show Instances question for simple single-tool requests. Default count=1 silently when no multi-instance intent detected.
 
-IMPORTANT: Do NOT skip any missing parameter. Do NOT silently default --effort to "medium" or --tool to any value. Present pickers for ALL unresolved parameters.
+Map tool choice to lowercase: "Claude" -> "claude", "Codex" -> "codex", etc.
+Map effort choice: "Medium (Recommended)" -> "medium", "Low" -> "low", etc.
+Map count choice: "1 (Single)" -> 1, "2 (Compare)" -> 2, "3 (Panel)" -> 3.
 
-#### Step 2c: Model Selection (MUST ask if no --model)
+#### Step 2d: Model selection (MUST ask if no --model)
 
-After tool is resolved (from Step 2b or $ARGUMENTS), present a model picker with options specific to the selected tool. The user can always type a custom model name via the "Other" option.
+After tool is resolved, present a model picker with options specific to the selected tool. The user can always type a custom model name via the "Other" option.
 
 **For Claude:**
 ```
@@ -153,7 +194,7 @@ AskUserQuestion:
         - label: "gpt-5.3-codex"        description: "Latest, most capable coding model"
         - label: "gpt-5.2-codex"        description: "Strong coding model"
         - label: "gpt-5.2"              description: "General purpose GPT-5.2"
-        - label: "gpt-5-codex-mini"     description: "Cost-effective, 4x more usage"
+        - label: "gpt-5.3-codex-spark"   description: "Cost-effective, 4x more usage"
 ```
 
 **For OpenCode:**
@@ -180,17 +221,21 @@ AskUserQuestion:
       options:
         - label: "claude-sonnet-4-5"        description: "Default Copilot model"
         - label: "claude-opus-4-6"          description: "Most capable Claude model"
-        - label: "gpt-5.3-codex"              description: "OpenAI GPT-5.3 Codex"
+        - label: "gpt-5.3-codex"            description: "OpenAI GPT-5.3 Codex"
         - label: "gemini-3-pro"             description: "Google Gemini 3 Pro"
 ```
 
-Map the user's choice to the model string (strip " (Recommended)" suffix if present). Pass the selected model to the skill via `--model`.
+Map the user's choice to the model string (strip " (Recommended)" suffix if present).
 
-IMPORTANT: Do NOT skip this step. Do NOT silently use a default model. If --model was not explicitly provided in $ARGUMENTS, you MUST present this picker. The model lists above are current as of Feb 2026 - the user may type any model name supported by their tool via the "Other" option.
+IMPORTANT: Do NOT skip model selection. Do NOT silently use a default model. If --model was not explicitly provided, you MUST present this picker.
 
-### Phase 3: Invoke Consult Skill
+### Phase 3: Execute Consultation
 
-With all parameters resolved (tool, effort, model, question, and optionally context, continue), invoke the `consult` skill using the Skill tool:
+With all parameters resolved (tool, effort, model, question, count, and optionally context/continue):
+
+#### Single instance (count=1, the default)
+
+Invoke the `consult` skill directly using the Skill tool:
 
 ```
 Skill: consult
@@ -199,15 +244,35 @@ Args: "[question]" --tool=[tool] --effort=[effort] --model=[model] [--context=[c
 Example: "Is this the right approach?" --tool=gemini --effort=high --model=gemini-3-pro
 ```
 
-The skill handles the full consultation lifecycle: it resolves the model from the effort level, builds the CLI command, packages any context, executes the command via Bash with a 120-second timeout, and returns a plain JSON result.
+The skill handles the full consultation lifecycle: model resolution, command building, context packaging, execution with 120s timeout, and returns a plain JSON result.
 
-### Phase 4: Parse Skill Output
+#### Multi-instance (count > 1)
 
-The skill returns a plain JSON object containing: `tool`, `model`, `effort`, `duration_ms`, `response`, `session_id`, and `continuable`. Parse the JSON directly from the skill output.
+Spawn the `consult-agent` via the Task tool with all resolved parameters:
 
-### Phase 5: Present Results
+```
+Task:
+  subagent_type: "consult-agent"
+  prompt: |
+    Execute a multi-instance consultation with these pre-resolved parameters:
+    - tool: [tool]
+    - model: [model]
+    - effort: [effort]
+    - question: [question]
+    - count: [count]
+    - context: [context or none]
+
+    Run [count] parallel consultations with the same tool and parameters.
+    Return all responses formatted with numbered headers and a brief synthesis.
+```
+
+The agent handles parallel execution, temp file management, result parsing, and synthesis.
+
+### Phase 4: Present Results
 
-After parsing the JSON, format and display the result as human-friendly text:
+#### Single instance
+
+Parse the skill's plain JSON output and display:
 
 ```
 Tool: {tool}, Model: {model}, Effort: {effort}, Duration: {duration_ms}ms.
@@ -218,12 +283,11 @@ The results of the consultation are:
 
 For continuable tools (Claude, Gemini, Codex, OpenCode), display: `Session: {session_id} - use /consult --continue to resume`
 
-Save session state for continuable tools (Claude, Gemini, Codex, OpenCode) to `{AI_STATE_DIR}/consult/last-session.json`.
+Save session state to `{AI_STATE_DIR}/consult/last-session.json`.
+
+#### Multi-instance
 
-Platform state directory:
-- Claude Code: `.opencode/`
-- OpenCode: `.opencode/`
-- Codex CLI: `.codex/`
+Display the agent's formatted output directly. The agent returns numbered responses with a synthesis section.
 
 On failure: `[ERROR] Consultation Failed: {specific error message}`
 
@@ -231,22 +295,34 @@ On failure: `[ERROR] Consultation Failed: {specific error message}`
 
 | Error | Output |
 |-------|--------|
-| No question provided | `[ERROR] Usage: /consult "your question" [--tool=gemini\|codex\|claude\|opencode\|copilot] [--effort=low\|medium\|high\|max]` |
+| No question provided | `[ERROR] Usage: /consult "your question" or /consult with gemini about your question` |
 | Tool not installed | `[ERROR] {tool} is not installed. Install with: {install command from skill}` |
 | Tool execution fails | `[ERROR] {tool} failed: {error}. Try a different tool with --tool=[other]` |
 | Timeout (>120s) | `[ERROR] {tool} timed out after 120s. Try --effort=low for faster response` |
 | No tools available | `[ERROR] No AI CLI tools found. Install: npm i -g @anthropic-ai/claude-code` |
 | Session not found | `[WARN] No previous session found. Starting fresh consultation.` |
 | API key missing | `[ERROR] {tool} requires API key. Set {env var} (see skill for details)` |
+| Count out of range | `[ERROR] Instance count must be 1-5. Got: {count}` |
+| Multi-instance partial failure | Show successful responses, note failures |
 
 ## Example Usage
 
 ```bash
-/consult "Is this the right approach for error handling?" --tool=gemini --effort=high
-/consult "Review this function for performance issues" --tool=codex
-/consult "What alternative patterns would you suggest?" --tool=claude --effort=max
+# Natural language (NLP parsing)
+/consult with codex about my auth approach
+/consult ask 3 codex about this design
+/consult gemini should I use redis or postgres
+/consult thoroughly ask claude about error handling
+/consult codex few instances about performance
+
+# Explicit flags (backward compatible)
+/consult "Is this the right approach?" --tool=gemini --effort=high
+/consult "Review this function" --tool=codex --count=3
 /consult "Suggest improvements" --tool=opencode --model=github-copilot/claude-opus-4-6
-/consult "Continue from where we left off" --continue
+/consult --continue
 /consult "Explain this error" --context=diff --tool=gemini
 /consult "Review this file" --context=file=src/index.js --tool=claude
+
+# Mixed (flags + natural language)
+/consult with gemini --effort=max about database schema design
 ```

package/adapters/opencode/commands/debate.md

@@ -0,0 +1,224 @@
+---
+description: Structured debate between two AI tools to stress-test ideas. Proposer/Challenger format with a verdict.
+agent: general
+---
+
+> **OpenCode Note**: Invoke agents using `@agent-name` syntax.
+> Available agents: task-discoverer, exploration-agent, planning-agent,
+> implementation-agent, deslop-agent, delivery-validator, sync-docs-agent, consult-agent
+> Example: `@exploration-agent analyze the codebase`
+
+
+# /debate - Structured AI Dialectic
+
+You are executing the /debate command. Your job is to parse the user's request, resolve missing parameters interactively, and spawn the debate orchestrator.
+
+## Constraints
+
+- NEVER expose API keys in commands or output
+- NEVER run with permission-bypassing flags
+- MUST validate tool names against allow-list: gemini, codex, claude, opencode, copilot
+- Proposer and challenger MUST be different tools
+- Rounds MUST be 1-5 (default: 2)
+
+## Execution
+
+### Phase 1: Parse Input (Flags + Natural Language)
+
+Parse `$ARGUMENTS` using both explicit flags and natural language. Flags take priority.
+
+#### Step 1a: Extract explicit flags
+
+1. `--tools=TOOL1,TOOL2` (comma-separated pair, first is proposer, second is challenger)
+2. `--rounds=N` where N is 1-5
+3. `--effort=VALUE` where VALUE is one of: low, medium, high, max
+4. `--model-proposer=VALUE` (any string)
+5. `--model-challenger=VALUE` (any string)
+6. `--context=VALUE` where VALUE is: diff, file=PATH, or none (passed through to consult skill for each tool invocation)
+
+Remove matched flags from `$ARGUMENTS`.
+
+#### Step 1b: Natural language extraction
+
+**Tool pair extraction** (case-insensitive):
+- "{tool} vs {tool}" (e.g., "codex vs gemini") -> proposer, challenger
+- "{tool} and {tool}" -> proposer, challenger
+- "with {tool} and {tool}" -> proposer, challenger
+- "between {tool} and {tool}" -> proposer, challenger
+- Tool names: claude, gemini, codex, opencode, copilot
+
+**Rounds extraction**:
+- "{N} rounds" -> rounds=N
+- "single round" / "one round" -> rounds=1
+- "deep" / "extended" -> rounds=3
+
+**Effort extraction** (same as consult):
+- "quick" / "fast" -> effort=low
+- "thorough" / "deep" / "carefully" -> effort=high
+- "maximum" / "max effort" -> effort=max
+
+**Topic extraction**:
+- Text after "about" is the topic
+- If no "about" pattern, remaining text after removing tool/rounds/effort markers
+
+**Validation**: rounds must be 1-5. Proposer and challenger must differ. If same tool specified for both, show: `[ERROR] Proposer and challenger must be different tools.`
+
+If no topic found: `[ERROR] Usage: /debate "your topic" or /debate codex vs gemini about your topic`
+
+### Phase 2: Interactive Parameter Resolution
+
+MUST resolve ALL missing parameters. Do NOT silently default.
+
+#### Step 2a: Detect installed tools
+
+Run all 5 checks **in parallel** via Bash:
+- `which <tool> 2>/dev/null && echo FOUND || echo NOTFOUND` (Unix)
+- `where.exe <tool> 2>nul && echo FOUND || echo NOTFOUND` (Windows)
+
+Check for: claude, gemini, codex, opencode, copilot.
+
+If fewer than 2 tools installed: `[ERROR] Debate requires at least 2 AI CLI tools. Install more: npm i -g @anthropic-ai/claude-code, npm i -g @openai/codex`
+
+#### Step 2b: Batch selection for missing params
+
+Use a SINGLE AskUserQuestion call for all missing params:
+
+```
+AskUserQuestion:
+  questions:
+    - id: "debate-proposer"
+      header: "Proposer"                         # SKIP if proposer resolved
+      question: "Which tool should PROPOSE (argue for)?"
+      multiSelect: false
+      options (only installed tools):
+        - label: "Claude"       description: "Deep code reasoning"
+        - label: "Gemini"       description: "Fast multimodal analysis"
+        - label: "Codex"        description: "Agentic coding"
+        - label: "OpenCode"     description: "Flexible model choice"
+        - label: "Copilot"      description: "GitHub-integrated AI"
+
+    - id: "debate-challenger"
+      header: "Challenger"                       # SKIP if challenger resolved
+      question: "Which tool should CHALLENGE (find flaws)?"
+      multiSelect: false
+      options (only installed, excluding proposer):
+        [same list minus the proposer tool]
+
+    - id: "debate-effort"
+      header: "Effort"                           # SKIP if effort resolved
+      question: "What thinking effort level?"
+      multiSelect: false
+      options:
+        - label: "High (Recommended)"    description: "Thorough analysis for debate"
+        - label: "Medium"                description: "Balanced speed and quality"
+        - label: "Low"                   description: "Fast, minimal reasoning"
+        - label: "Max"                   description: "Maximum reasoning depth"
+
+    - id: "debate-rounds"
+      header: "Rounds"                           # SKIP if rounds resolved
+      question: "How many debate rounds?"
+      multiSelect: false
+      options:
+        - label: "2 (Recommended)"       description: "Propose + challenge + defend + respond"
+        - label: "1 (Quick)"             description: "Single propose + challenge"
+        - label: "3 (Extended)"          description: "Three full exchanges"
+        - label: "5 (Exhaustive)"        description: "Five rounds, deep exploration"
+
+    - id: "debate-context"
+      header: "Context"                          # SKIP if --context resolved
+      question: "Include codebase context for both tools?"
+      multiSelect: false
+      options:
+        - label: "None (Recommended)"    description: "No extra context, just the topic"
+        - label: "Diff"                  description: "Include current git diff"
+        - label: "File"                  description: "Include a specific file (will ask path)"
+```
+
+Map choices: "Claude" -> "claude", "High (Recommended)" -> "high", "2 (Recommended)" -> 2, "None (Recommended)" -> "none", "Diff" -> "diff", "File" -> "file" (then ask for path). Strip " (Recommended)" suffix.
+
+If context resolved to "file":
+  Use a follow-up AskUserQuestion to ask for the file path:
+  ```
+  AskUserQuestion:
+    questions:
+      - id: "debate-file-path"
+        header: "File path"
+        question: "Which file should both tools see?"
+        multiSelect: false
+        options:
+          - label: "src/"               description: "Source directory file"
+          - label: "README.md"          description: "Project readme"
+  ```
+  The user can type any path via "Other".
+  After getting the path:
+  1. Reject absolute paths outside the current working directory
+  2. Reject paths containing `..` that escape the project root
+  3. Reject UNC paths (`\\` or `//` prefix)
+  4. Validate the file exists using the Read tool
+  If the path escapes the project: `[ERROR] Context file must be within the project directory`
+  If the file doesn't exist: `[ERROR] Context file not found: {PATH}`
+  If valid, set context to `file={user_provided_path}`.
+
+If proposer and challenger resolve to the same tool after selection, show error and re-ask for challenger.
+
+### Phase 3: Spawn Debate Orchestrator
+
+With all parameters resolved, spawn the debate orchestrator agent:
+
+```
+Task:
+  subagent_type: "debate-orchestrator"
+  model: opus
+  prompt: |
+    Execute a structured debate with these pre-resolved parameters:
+    - topic: [topic]
+    - proposer: [proposer tool]
+    - challenger: [challenger tool]
+    - effort: [effort]
+    - rounds: [rounds]
+    - model_proposer: [model or "omit"]
+    - model_challenger: [model or "omit"]
+
+    If model is "omit" or empty, do NOT include --model in consult skill invocations. The consult skill will use effort-based defaults.
+    - context: [context or "none"]
+
+    Follow the debate skill templates. Display each round progressively.
+    Deliver a verdict that picks a winner.
+```
+
+### Phase 4: Present Results
+
+Display the orchestrator's output directly. It includes:
+- Progressive round-by-round output (displayed as each round completes)
+- Final synthesis with verdict, agreements, disagreements, and recommendation
+
+On failure: `[ERROR] Debate Failed: {specific error message}`
+
+## Error Handling
+
+| Error | Output |
+|-------|--------|
+| No topic provided | `[ERROR] Usage: /debate "your topic" or /debate codex vs gemini about your topic` |
+| Tool not installed | `[ERROR] {tool} is not installed. Install with: {install command}` |
+| Fewer than 2 tools | `[ERROR] Debate requires at least 2 AI CLI tools installed.` |
+| Same tool for both | `[ERROR] Proposer and challenger must be different tools.` |
+| Rounds out of range | `[ERROR] Rounds must be 1-5. Got: {rounds}` |
+| Context file not found | `[ERROR] Context file not found: {PATH}` |
+| Orchestrator fails | `[ERROR] Debate failed: {error}` |
+
+## Example Usage
+
+```bash
+# Natural language
+/debate codex vs gemini about microservices vs monolith
+/debate with claude and codex about our auth implementation
+/debate thoroughly gemini vs codex about database schema design
+/debate codex vs gemini 3 rounds about event sourcing
+
+# Explicit flags
+/debate "Should we use event sourcing?" --tools=claude,gemini --rounds=3 --effort=high
+/debate "Redis vs PostgreSQL for caching" --tools=codex,opencode
+
+# Mixed
+/debate codex vs gemini --effort=max about performance optimization strategies
+```

package/adapters/opencode/commands/delivery-approval.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: Validate task completion and approve for shipping. Can be used standalone or called by the workflow. Runs autonomous validation checks.
 agent: general

package/adapters/opencode/commands/deslop.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: This skill should be used when the user asks to "clean up slop", "remove AI artifacts", "deslop the codebase", "find debug statements", "remove console.logs", "repo hygiene", or mentions "AI slop", "code cleanup", "slop detection".
 agent: general

package/adapters/opencode/commands/drift-detect.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: Deep repository analysis to realign project plans with actual code reality
 agent: general

package/adapters/opencode/commands/enhance.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: Analyze plugins, agents, prompts, docs, hooks, and skills for best-practice gaps
 agent: general

package/adapters/opencode/commands/learn.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: Use when user asks to "learn about topic", "research subject", "create learning guide", "build knowledge base", "study topic", or wants to gather online resources on any subject.
 agent: general

package/adapters/opencode/commands/next-task.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: Master workflow orchestrator with autonomous task-to-production automation
 agent: general

package/adapters/opencode/commands/perf.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: Structured performance investigation with baselines, profiling, and evidence-backed decisions
 agent: general

package/adapters/opencode/commands/repo-map.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: Generate and maintain a cached AST repo map (symbols, imports, exports) using ast-grep for accurate drift detection and analysis
 agent: general

package/adapters/opencode/commands/ship-ci-review-loop.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: "Use when monitoring CI and handling review comments during /ship. Details mandatory wait periods, auto-reviewer handling, and comment resolution."
 agent: general

package/adapters/opencode/commands/ship-deployment.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: "Use when deploying and validating during /ship. Details Railway/Vercel deployment, smoke testing, and rollback procedures."
 agent: general

package/adapters/opencode/commands/ship-error-handling.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 agent: general
 ---

package/adapters/opencode/commands/ship.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: Complete PR workflow from commit to production with validation
 agent: general

package/adapters/opencode/commands/sync-docs.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 description: Use when user asks to "update docs", "sync documentation", "fix outdated docs", "update changelog", "docs are stale", or after completing code changes that might affect documentation.
 agent: general

package/adapters/opencode/skills/agnix/SKILL.md

@@ -1,8 +1,7 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: agnix
 description: "Use when user asks to 'lint agent configs', 'validate skills', 'check CLAUDE.md', 'validate hooks', 'lint MCP'. Validates agent configuration files against 155 rules across 10+ AI tools."
-version: 5.0.3
+version: 5.1.0
 argument-hint: "[path] [--fix] [--strict] [--target=claude-code|cursor|codex]"
 ---