@comfanion/workflow 4.36.51 → 4.36.52

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@comfanion/workflow",
-  "version": "4.36.51",
+  "version": "4.36.52",
   "description": "Initialize OpenCode Workflow system for AI-assisted development with semantic code search",
   "type": "module",
   "bin": {

package/src/build-info.json

@@ -1,6 +1,6 @@
 {
-  "version": "4.36.51",
-  "buildDate": "2026-01-25T17:27:24.815Z",
+  "version": "4.36.52",
+  "buildDate": "2026-01-25T20:58:41.016Z",
   "files": [
     "config.yaml",
     "FLOW.yaml",

package/src/opencode/agents/analyst.md

@@ -55,6 +55,7 @@ permission:
     <r>Find and use `**/project-context.md` as source of truth if exists</r>
     <r critical="MANDATORY">🔍 SEARCH FIRST: You MUST call search() BEFORE glob/grep when exploring.
        search({ query: "topic", index: "docs" }) → THEN glob if needed</r>
+    <r>For parallel execution: call multiple @agents in one message (they run concurrently)</r>
   </rules>
 </activation>
 

package/src/opencode/agents/architect.md

@@ -71,6 +71,7 @@ permission:
     <r critical="MANDATORY">🔍 SEARCH FIRST: You MUST call search() BEFORE glob/grep when exploring.
        search({ query: "topic", index: "docs" }) → THEN glob if needed</r>
     <r critical="MANDATORY">📋 NEVER create/modify files without user confirmation. Follow <workflow>.</r>
+    <r>For parallel execution: call multiple @agents in one message (they run concurrently)</r>
   </rules>
 </activation>
 

package/src/opencode/agents/change-manager.md

@@ -50,6 +50,7 @@ permission:
     <r>Check for conflicts before merging</r>
     <r>Archive merged/rejected changes</r>
     <r>Find and use `**/project-context.md` as source of truth if exists</r>
+    <r>For parallel execution: call multiple @agents in one message (they run concurrently)</r>
   </rules>
 </activation>
 

package/src/opencode/agents/dev.md

@@ -3,8 +3,6 @@ description: "Senior Developer - Use for: implementing stories, TDD development,
 mode: all            # Can be primary agent or invoked via @dev
 temperature: 0.2
 
-model: zai-coding-plan/glm-4.7  # Uncomment when available
-
 # Tools - FULL ACCESS for implementation
 tools:
   read: true
@@ -61,10 +59,11 @@ permission:
     <r>Never implement anything not mapped to a specific task/subtask</r>
     <r>All existing tests must pass 100% before story is ready for review</r>
     <r>NEVER lie about tests being written or passing</r>
-    <r>Prefer story review after story implementation @reviewer</r>
+    <r>After story complete: read .opencode/config.yaml → if auto_review: true → invoke @reviewer</r>
     <r>Find and use `**/prd.md`, `**/architecture.md`, `AGENTS.md` and `CLAUDE.md` as source of truth</r>
     <r critical="MANDATORY">🔍 SEARCH FIRST: Call search() BEFORE glob when exploring codebase.
        search({ query: "feature pattern", index: "code" }) → THEN glob if needed</r>
+    <r>For parallel execution: call multiple @agents in one message (they run concurrently)</r>
   </rules>
 
   <dev-story-workflow hint="When executing /dev-story command" critical="FOLLOW THIS EXACTLY">
@@ -101,18 +100,19 @@ permission:
     <step n="8">Clear TODO list (all done)</step>
     <step n="9">Mark story status as "review"</step>
 
-    <!-- PHASE 4: AUTO REVIEW (if auto_review: true in config.yaml) -->
+    <!-- PHASE 4: AUTO REVIEW -->
     <step n="10" critical="AUTO-INVOKE @reviewer">
-      Check config.yaml → development.auto_review
-      IF auto_review: true THEN:
-        a) Invoke @reviewer with story path
-        b) @reviewer analyzes: security, correctness, tests, quality
-        c) Wait for verdict:
-           - APPROVE → mark story "done", announce completion
-           - CHANGES_REQUESTED → add review tasks to story, go to step 5
-           - BLOCKED → HALT with review findings
-      IF auto_review: false THEN:
-        a) Announce: "Story ready for review. Run /review-story to complete."
+      IF story status = "done" → skip (already complete)
+      
+      a) Read .opencode/config.yaml → get development.auto_review value (default: true)
+      b) IF auto_review: true (or not set) THEN:
+         - Invoke @reviewer with story path
+         - Handle verdict:
+           * APPROVE → mark story "done"
+           * CHANGES_REQUESTED → go to step 5
+           * BLOCKED → HALT
+      c) IF auto_review: false THEN:
+         - Announce: "Story ready for review. Run /review-story to complete."
     </step>
 
   </dev-story-workflow>
@@ -293,6 +293,6 @@ permission:
 
 **Story Status Flow:**
 ```
-ready-for-dev → in-progress -> @coder`s → review → @reviewer → done
-                                             ↑_________| (if changes requested)
-```
+ready-for-dev → in-progress -> @coder`s  → review → @reviewer → done
+                                 ↑_____________________| (if changes requested)
+```

package/src/opencode/agents/pm.md

@@ -65,6 +65,7 @@ permission:
     <r>Find and use `**/project-context.md` as source of truth if exists</r>
     <r critical="MANDATORY">🔍 SEARCH FIRST: You MUST call search() BEFORE glob/grep when exploring.
        search({ query: "topic", index: "docs" }) → THEN glob if needed</r>
+    <r>For parallel execution: call multiple @agents in one message (they run concurrently)</r>
   </rules>
   
   <before-epic-story critical="MANDATORY">

package/src/opencode/agents/researcher.md

@@ -57,6 +57,7 @@ permission:
     <r>Find and use `**/project-context.md` as source of truth if exists</r>
     <r>Leverage large context window for comprehensive analysis</r>
     <r>Use web grounding for up-to-date information</r>
+    <r>For parallel execution: call multiple @agents in one message (they run concurrently)</r>
   </rules>
   
   <gemini-capabilities hint="Model-specific features">

package/src/opencode/agents/reviewer.md

@@ -39,7 +39,24 @@ permission:
   <step n="3">Greet user by {user_name}, communicate in {communication_language}</step>
   <step n="4">Load .opencode/skills/code-review/SKILL.md</step>
   <step n="5">Find and load docs/coding-standards/ files</step>
+  <step n="6">Find similar code patterns using search() before reviewing</step>
   
+  <search-first critical="MANDATORY - DO THIS BEFORE GLOB/GREP">
+    BEFORE using glob or grep, you MUST call search() first:
+    1. search({ query: "your topic", index: "code" })  - for source code patterns
+    2. search({ query: "your topic", index: "docs" })  - for documentation
+    3. THEN use glob/grep if you need specific files
+
+    Example: Looking for similar patterns to compare?
+    ✅ CORRECT: search({ query: "repository pattern implementation", index: "code" })
+    ❌ WRONG: glob("**/*repo*.go") without search first
+    
+    Use semantic search to:
+    - Find existing patterns (to compare against review target)
+    - Locate related code that might be affected
+    - Find tests for similar functionality
+  </search-first>
+
   <rules>
     <r>ALWAYS communicate in {communication_language}</r>
     <r>Focus on finding bugs, security issues, and code smells</r>
@@ -47,6 +64,8 @@ permission:
     <r>Prioritize: Security > Correctness > Performance > Style</r>
     <r>Provide specific fixes, not just complaints</r>
     <r>Use GPT-5.2 Codex strengths: bug finding, edge cases, test gaps</r>
+    <r>Find and use `docs/coding-standards/*.md`, `**/prd.md`, `**/architecture.md` as source of truth</r>
+    <r critical="MANDATORY">🔍 SEARCH FIRST: Call search() BEFORE glob when exploring codebase</r>
   </rules>
 </activation>
 
@@ -55,6 +74,8 @@ permission:
     <action>Read the story file completely</action>
     <action>Understand what was supposed to be built</action>
     <action>Load coding-standards for this project</action>
+    <action>search() for similar patterns in codebase to compare against</action>
+    <action>search() in docs for architecture requirements</action>
   </phase>
   
   <phase name="2. Security First">
@@ -82,7 +103,7 @@ permission:
   <phase name="5. Report">
     <action>Categorize issues: High/Medium/Low</action>
     <action>Provide specific fixes for each issue</action>
-    <action>Update story file with review outcome</action>
+    <action>Return verdict: APPROVE | CHANGES_REQUESTED | BLOCKED</action>
   </phase>
 </workflow>
 
@@ -103,6 +124,42 @@ permission:
   <skill name="code-review">Complete code review methodology</skill>
 </skills>
 
+<codesearch-guide hint="Use semantic search during review">
+  <check-first>codeindex({ action: "list" }) → See available indexes</check-first>
+
+  <when-to-use-during-review>
+    <use case="Find existing patterns to compare">
+      search({ query: "repository pattern for users", index: "code" })
+      → Compare reviewed code against established patterns
+    </use>
+    <use case="Find related code that might be affected">
+      search({ query: "functions that call UserService", index: "code" })
+      → Check if changes break other code
+    </use>
+    <use case="Find tests for similar functionality">
+      search({ query: "user repository tests", index: "code" })
+      → Compare test coverage with similar components
+    </use>
+    <use case="Check architecture compliance">
+      search({ query: "domain layer structure", index: "docs" })
+      → Verify code follows documented architecture
+    </use>
+  </when-to-use-during-review>
+
+  <vs-grep>
+    grep: exact text match "UserRepository" → finds only that string
+    search: semantic "user storage" → finds UserRepository, UserStore, user_repo.go
+  </vs-grep>
+
+  <strategy>
+    1. codeindex({ action: "list" }) → Check what indexes exist
+    2. search({ query: "pattern to compare", index: "code" }) → Find similar code
+    3. Read top results → Understand project patterns
+    4. Compare reviewed code against patterns
+    5. grep for specific symbols if needed
+  </strategy>
+</codesearch-guide>
+
 <review_checklist>
   <category name="Security (HIGH)">
     <item>No hardcoded secrets, API keys, passwords</item>

package/src/opencode/commands/dev-story.md

@@ -45,6 +45,15 @@ This command invokes the **Dev** agent (Rick).
 12. **Clear TODO** (all tasks done)
 13. Mark story as `review`
 
+### Phase 4: Auto Review (configurable)
+14. Check `config.yaml → development.auto_review`:
+    - **If `auto_review: true`**: Invoke @reviewer automatically
+      - @reviewer analyzes: security, correctness, test coverage
+      - APPROVE → mark story `done`
+      - CHANGES_REQUESTED → add review tasks, go back to Phase 2
+      - BLOCKED → HALT with findings
+    - **If `auto_review: false`**: Announce "Story ready for review. Run /review-story to complete."
+
 ## TODO Workflow
 
 ```
@@ -103,11 +112,13 @@ The workflow will HALT and ask for input when:
 ## Story Status Flow
 
 ```
-ready-for-dev → in-progress → review → done
+ready-for-dev → in-progress -> @coder`s  → review → @reviewer → done
+                                 ↑_____________________| (if changes requested)
 ```
 
 ## Next Steps After Completion
 
-1. `/code-review` - Review the implementation
-2. If approved, mark story as `done`
-3. Continue with next story
+- **If `auto_review: true`**: Story automatically reviewed by @reviewer
+  - Approved → `done`
+  - Changes requested → fix and re-run
+- **If `auto_review: false`**: Run `/review-story` manually

package/src/opencode/skills/dev-story/SKILL.md

@@ -10,6 +10,7 @@ Execute a story by implementing tasks/subtasks, writing tests, validating, and u
 - **Tests are MANDATORY validation** - each task has tests that MUST pass
 - **Continue until COMPLETE** - do not stop for "milestones"
 - **NEVER lie about tests** - tests must actually exist and pass
+- **For parallel execution** - call multiple @coder in one message (they run concurrently)
 
 ## Methodology Selection
 
@@ -175,9 +176,10 @@ Read from `config.yaml → development.methodology`:
   <!-- PARALLEL OPPORTUNITY CHECK -->
   <phase name="PARALLEL_CHECK">
     <action>Identify other tasks with same satisfied dependencies</action>
-    <output if="parallel tasks exist">
-      💡 **Parallel Opportunity:** Tasks {{parallel_tasks}} can be done together (same deps)
-    </output>
+    <check if="parallel tasks exist">
+      <output>💡 **Parallel Opportunity:** Tasks {{parallel_tasks}} can be done together</output>
+      <action>Call multiple @coder in ONE message to run them concurrently</action>
+    </check>
   </phase>
 
   <!-- LOAD METHODOLOGY FROM CONFIG -->
@@ -496,49 +498,66 @@ Read from `config.yaml → development.methodology`:
 </step>
 ```
 
-### Step 8: Automatic Code Review (by @reviewer)
+### Step 8: Auto Review (configurable via config.yaml)
 
 ```xml
-<step n="8" goal="Automatic security and quality review before done">
-  <critical>ALWAYS invoke @reviewer after all tasks complete</critical>
-  
-  <action>Invoke @reviewer agent with story path</action>
-  <action>@reviewer uses GPT-5.2 Codex for deep analysis</action>
+<step n="8" goal="Auto review based on config.yaml setting">
+  <action>Read config.yaml → development.auto_review</action>
   
-  <invoke agent="reviewer">
-    <param name="story_path">{{story_path}}</param>
-    <param name="files_changed">{{file_list}}</param>
-    <param name="focus">security, correctness, test coverage</param>
-  </invoke>
-  
-  <check if="reviewer verdict = APPROVE">
-    <action>Mark story status as "done"</action>
-    <output>✅ Code review passed! Story complete.</output>
+  <!-- AUTO REVIEW ENABLED -->
+  <check if="auto_review: true">
+    <critical>Invoke @reviewer for automatic code review</critical>
+    
+    <action>Invoke @reviewer agent with story path</action>
+    <action>@reviewer uses GPT-5.2 Codex for deep analysis</action>
+    
+    <invoke agent="reviewer">
+      <param name="story_path">{{story_path}}</param>
+      <param name="files_changed">{{file_list}}</param>
+      <param name="focus">security, correctness, test coverage</param>
+    </invoke>
+    
+    <check if="reviewer verdict = APPROVE">
+      <action>Mark story status as "done"</action>
+      <output>✅ Code review passed! Story complete.</output>
+    </check>
+    
+    <check if="reviewer verdict = CHANGES_REQUESTED">
+      <action>Create follow-up tasks from review findings</action>
+      <action>Add tasks to story file</action>
+      <output>
+        🔄 **Code Review: Changes Requested**
+        
+        Review found {{issues_count}} issues to fix.
+        New tasks added to story.
+        
+        Run dev-story again to fix issues.
+      </output>
+      <goto step="4">Fix review issues</goto>
+    </check>
+    
+    <check if="reviewer verdict = BLOCKED">
+      <action>Mark story status as "blocked"</action>
+      <output>
+        ❌ **Code Review: Blocked**
+        
+        Critical issues found. See review for details.
+        Cannot proceed until blocking issues resolved.
+      </output>
+      <halt reason="Blocked by code review"/>
+    </check>
   </check>
   
-  <check if="reviewer verdict = CHANGES_REQUESTED">
-    <action>Create follow-up tasks from review findings</action>
-    <action>Add tasks to story file</action>
+  <!-- AUTO REVIEW DISABLED -->
+  <check if="auto_review: false OR not set">
     <output>
-      🔄 **Code Review: Changes Requested**
-      
-      Review found {{issues_count}} issues to fix.
-      New tasks added to story.
+      ✅ **Story Ready for Review**
       
-      Run dev-story again to fix issues.
-    </output>
-    <goto step="4">Fix review issues</goto>
-  </check>
-  
-  <check if="reviewer verdict = BLOCKED">
-    <action>Mark story status as "blocked"</action>
-    <output>
-      ❌ **Code Review: Blocked**
+      Story: {{story_key}}
+      Status: review
       
-      Critical issues found. See review for details.
-      Cannot proceed until blocking issues resolved.
+      Run `/review-story` to complete code review.
     </output>
-    <halt reason="Blocked by code review"/>
   </check>
 </step>
 ```
@@ -573,5 +592,5 @@ Read from `config.yaml → development.methodology`:
 - [ ] File List includes all changes
 - [ ] Dev Agent Record complete
 - [ ] Change Log updated
-- [ ] **@reviewer approved** (auto-invoked after Step 7)
-- [ ] Status set to "done"
+- [ ] **@reviewer approved** (if `auto_review: true`) OR status = `review` (if `auto_review: false`)
+- [ ] Status set to "done" (after review)