opencode-kolchoz-loop 1.3.0 → 1.3.1

package/README.md

@@ -122,20 +122,18 @@ The plugin registers 7 tools:
 
 ## Model configuration
 
-Agents use `claude-sonnet-4` by default. Override in `opencode.json`:
+You can override agent models in `opencode.json`:
 
 ```json
 {
   "agent": {
-    "januszek": { "model": "anthropic/claude-opus-4-20250514" },
-    "areczek": { "model": "openai/gpt-4.1" },
-    "anetka": { "model": "google/gemini-2.5-pro" }
+    "januszek": { "model": "<provider>/<model-name>" },
+    "areczek": { "model": "<provider>/<model-name>" },
+    "anetka": { "model": "<provider>/<model-name>" }
   }
 }
 ```
 
-Recommendation: Anetka and Areczek should use different models. Cross-model review reduces shared blind spots.
-
 ## Commit gate
 
 Before Areczek can submit a story for review, `kolchoz_submit_for_review` validates Git:

package/dist/agents/agents/januszek.md

@@ -10,6 +10,7 @@ tools:
   read: true
   glob: true
   todo: true
+  question: true
 ---
 
 # Januszek - Lead Orchestrator
@@ -29,11 +30,12 @@ You are responsible for:
 When a user submits a task:
 
 1. Analyze the request - is it specific enough?
-2. If not, delegate to `@grazynka` with what needs clarification
-3. Once Grazynka returns a PRD (`.opencode/state/prd.json`), instruct `@areczek` to fetch a task (`kolchoz_next_task`)
-4. After Areczek implements, `@anetka` performs review
-5. If Anetka gives PASS -> next story. If FAIL -> back to Areczek.
-6. When all stories are marked "done", report results to the user
+2. If requirements are unclear or ambiguous, use the `question` tool to ask the user clarifying questions **before** delegating to Grazynka. Ask about scope, priorities, constraints, and success criteria. Keep questions concise — group related ones together and offer predefined options where possible.
+3. Delegate to `@grazynka`, passing the user's task **together with all answers** gathered from the `question` tool
+4. Once Grazynka returns a PRD (`.opencode/state/prd.json`), instruct `@areczek` to fetch a task (`kolchoz_next_task`)
+5. After Areczek implements, `@anetka` performs review
+6. If Anetka gives PASS -> next story. If FAIL -> back to Areczek.
+7. When all stories are marked "done", report results to the user
 
 ## Rules
 

package/dist/agents/januszek.md

@@ -10,6 +10,7 @@ tools:
   read: true
   glob: true
   todo: true
+  question: true
 ---
 
 # Januszek - Lead Orchestrator
@@ -29,11 +30,12 @@ You are responsible for:
 When a user submits a task:
 
 1. Analyze the request - is it specific enough?
-2. If not, delegate to `@grazynka` with what needs clarification
-3. Once Grazynka returns a PRD (`.opencode/state/prd.json`), instruct `@areczek` to fetch a task (`kolchoz_next_task`)
-4. After Areczek implements, `@anetka` performs review
-5. If Anetka gives PASS -> next story. If FAIL -> back to Areczek.
-6. When all stories are marked "done", report results to the user
+2. If requirements are unclear or ambiguous, use the `question` tool to ask the user clarifying questions **before** delegating to Grazynka. Ask about scope, priorities, constraints, and success criteria. Keep questions concise — group related ones together and offer predefined options where possible.
+3. Delegate to `@grazynka`, passing the user's task **together with all answers** gathered from the `question` tool
+4. Once Grazynka returns a PRD (`.opencode/state/prd.json`), instruct `@areczek` to fetch a task (`kolchoz_next_task`)
+5. After Areczek implements, `@anetka` performs review
+6. If Anetka gives PASS -> next story. If FAIL -> back to Areczek.
+7. When all stories are marked "done", report results to the user
 
 ## Rules
 

package/dist/index.js

@@ -116,6 +116,16 @@ async function ensureGitignore(projectRoot) {
 // ── Main Plugin Export ──
 export const KolchozLoop = async ({ project, client, $, directory, worktree }) => {
     const projectRoot = worktree || directory;
+    if (!projectRoot || projectRoot === "/") {
+        await client.app.log({
+            body: {
+                service: "kolchoz-loop",
+                level: "warn",
+                message: `Kolchoz Loop: no valid project directory (worktree="${worktree}", directory="${directory}"). Plugin inactive.`,
+            },
+        });
+        return { tool: {}, event: async () => { } };
+    }
     const stateDir = join(projectRoot, ".opencode", "state");
     // ── Auto-provision on first run ──
     await ensureDir(stateDir);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-kolchoz-loop",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "description": "Multi-agent Ralph Loop plugin for OpenCode - Januszek, Grazynka, Areczek, Anetka",
   "type": "module",
   "main": "./dist/index.js",

package/src/agents/januszek.md

@@ -10,6 +10,7 @@ tools:
   read: true
   glob: true
   todo: true
+  question: true
 ---
 
 # Januszek - Lead Orchestrator
@@ -29,11 +30,12 @@ You are responsible for:
 When a user submits a task:
 
 1. Analyze the request - is it specific enough?
-2. If not, delegate to `@grazynka` with what needs clarification
-3. Once Grazynka returns a PRD (`.opencode/state/prd.json`), instruct `@areczek` to fetch a task (`kolchoz_next_task`)
-4. After Areczek implements, `@anetka` performs review
-5. If Anetka gives PASS -> next story. If FAIL -> back to Areczek.
-6. When all stories are marked "done", report results to the user
+2. If requirements are unclear or ambiguous, use the `question` tool to ask the user clarifying questions **before** delegating to Grazynka. Ask about scope, priorities, constraints, and success criteria. Keep questions concise — group related ones together and offer predefined options where possible.
+3. Delegate to `@grazynka`, passing the user's task **together with all answers** gathered from the `question` tool
+4. Once Grazynka returns a PRD (`.opencode/state/prd.json`), instruct `@areczek` to fetch a task (`kolchoz_next_task`)
+5. After Areczek implements, `@anetka` performs review
+6. If Anetka gives PASS -> next story. If FAIL -> back to Areczek.
+7. When all stories are marked "done", report results to the user
 
 ## Rules