@comfanion/workflow 4.1.0 → 4.1.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@comfanion/workflow",
-  "version": "4.1.0",
+  "version": "4.1.2",
   "description": "Initialize OpenCode Workflow system for AI-assisted development",
   "type": "module",
   "bin": {

package/src/build-info.json

@@ -1,6 +1,6 @@
 {
   "version": "3.0.0",
-  "buildDate": "2026-01-23T17:40:44.228Z",
+  "buildDate": "2026-01-23T17:53:50.018Z",
   "files": [
     "config.yaml",
     "FLOW.yaml",

package/src/opencode/agents/pm.md

@@ -37,7 +37,18 @@ permission:
     <r>Ship the smallest thing that validates the assumption</r>
     <r>Every feature must trace to a user problem</r>
     <r>NEVER create stories without acceptance criteria</r>
+    <r critical="true">BEFORE writing epic/story tasks: MUST Glob+Read coding standards (see skill)</r>
   </rules>
+  
+  <before-epic-story critical="MANDATORY">
+    <instruction>BEFORE writing ANY epic or story with tasks, you MUST execute:</instruction>
+    <step n="1">Glob "**/AGENTS.md" OR "**/CLAUDE.md" → Read the file</step>
+    <step n="2">Glob "**/coding-standards/**/*.md" → Read ALL files found</step>
+    <step n="3">Glob "**/[module]-data-model*.md" → Read data model</step>
+    <step n="4">Glob "**/src/services/[module]/**/domain/**/*.go" → Read 2-3 existing patterns</step>
+    <step n="5">ONLY THEN proceed to write tasks with Documentation links</step>
+    <warning>Tasks without proper Documentation links to coding standards = REJECTED</warning>
+  </before-epic-story>
 </activation>
 
 <persona>

package/src/opencode/config.yaml

@@ -6,7 +6,7 @@
 # PROJECT CONFIGURATION
 # =============================================================================
 project_name: "ai-wf"
-version: "4.1.0"
+version: "4.1.2"
 
 # =============================================================================
 # USER CONFIGURATION

package/src/opencode/skills/epic-writing/SKILL.md

@@ -18,44 +18,57 @@ Use this skill when you need to:
 - Define epic-level acceptance criteria
 - Track PRD coverage
 
-## MANDATORY: Load Technical Context First
+## MANDATORY: Read Before Writing Epic
 
-**Before writing ANY epic, you MUST read and understand:**
+**⚠️ STOP! Before writing ANY epic, execute these steps:**
 
-### 1. Project Architecture (REQUIRED)
-```
-Search and read in order:
-1. CLAUDE.md (root) - Project patterns, conventions, tech stack
-2. docs/architecture.md - System architecture, module boundaries
-3. docs/architecture/[module]/ - Module-specific documentation
-```
+### Step 1: Find and Read Project Standards
 
-### 2. Module/Domain Documentation (REQUIRED)
+```bash
+# Execute these Glob searches:
+Glob "**/AGENTS.md" OR "**/CLAUDE.md"       # → Read the file found
+Glob "**/docs/architecture.md"              # → Read system architecture
+Glob "**/coding-standards/**/*.md"          # → Read ALL coding standards
 ```
-For the specific module this epic covers:
-1. docs/architecture/[module]/index.md - Module overview
-2. docs/architecture/[module]/architecture.md - Module architecture
-3. docs/architecture/[module]/data-model.md - Database schema
-4. docs/architecture/[module]/api/ - API contracts
-5. docs/architecture/[module]/events/ - Event schemas
+
+**You MUST read these files before writing epic!**
+
+### Step 2: Find and Read Module Documentation
+
+```bash
+# For the module this epic covers (e.g., "catalog"):
+Glob "**/docs/**/catalog/**/*.md"           # → Read ALL module docs
+Glob "**/catalog-data-model*.md"            # → Read data model
+Glob "**/catalog-architecture*.md"          # → Read module architecture
 ```
 
-### 3. PRD Requirements (REQUIRED)
+### Step 3: Find and Read PRD
+
+```bash
+Glob "**/prd.md"                            # → Read PRD for FR-XXX references
+Glob "**/requirements/*.md"                 # → Read detailed requirements if exist
 ```
-1. docs/prd.md - Functional requirements (FR-XXX)
-2. docs/requirements/ - Detailed requirements if exists
+
+### Step 4: Find Existing Code Patterns (for technical notes)
+
+```bash
+# Find existing code to reference in Technical Notes:
+Glob "**/src/services/[module]/modules/*/domain/**/*.go"       # → Domain patterns
+Glob "**/src/services/[module]/modules/*/application/**/*.go"  # → Use case patterns
 ```
 
 ### Pre-Epic Checklist
 
-Before writing epic, confirm you have read:
-- [ ] CLAUDE.md - coding patterns and conventions
-- [ ] Architecture document - system design
-- [ ] Module documentation - specific module architecture
-- [ ] PRD - requirements this epic implements
+Before writing epic, confirm you executed:
+- [ ] **Glob + Read** AGENTS.md/CLAUDE.md
+- [ ] **Glob + Read** docs/architecture.md
+- [ ] **Glob + Read** coding-standards/*.md (ALL files)
+- [ ] **Glob + Read** module documentation (architecture, data-model)
+- [ ] **Glob + Read** PRD for requirements
+- [ ] **Glob** existing code patterns (for Technical Notes section)
 
-**⚠️ DO NOT proceed without reading technical documentation!**
-**Epic MUST reference architecture sections and follow established patterns.**
+**⛔ DO NOT WRITE EPIC WITHOUT COMPLETING ALL STEPS ABOVE!**
+**Epic without proper architecture references = REJECTED.**
 
 ---
 

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

@@ -18,42 +18,57 @@ Use this skill when you need to:
 - Define technical implementation tasks
 - Specify test scenarios
 
-## MANDATORY: Load Technical Standards First
+## MANDATORY: Read Before Writing Tasks
 
-**Before writing ANY story with tasks, you MUST read and understand:**
+**⚠️ STOP! Before writing ANY task, execute these steps:**
 
-### 1. Coding Standards (REQUIRED)
-```
-Search and read in order:
-1. CLAUDE.md (root) - Project patterns, code style, conventions
-2. docs/coding-standards/ - Detailed coding standards
-3. docs/coding-standards/testing-standards.md - Test patterns
-```
+### Step 1: Find and Read Coding Standards
 
-### 2. Module Architecture (REQUIRED)
+```bash
+# Execute these Glob searches:
+Glob "**/AGENTS.md" OR "**/CLAUDE.md"      # → Read the file found
+Glob "**/coding-standards/**/*.md"          # → Read ALL files found
+Glob "**/testing-standards*.md"             # → Read if exists
 ```
-For the specific module this story covers:
-1. docs/architecture/[module]/architecture.md - Module design
-2. docs/architecture/[module]/data-model.md - Database schema
-3. Existing code in src/services/[module]/ - Current patterns
+
+**You MUST read these files before writing tasks!**
+
+### Step 2: Find and Read Module Architecture
+
+```bash
+# For the module this story covers (e.g., "catalog"):
+Glob "**/docs/**/catalog/**/*.md"           # → Read architecture docs
+Glob "**/catalog-data-model*.md"            # → Read data model
 ```
 
-### 3. Parent Epic (REQUIRED)
+### Step 3: Find and Read Existing Code Patterns
+
+```bash
+# Find existing code to use as patterns:
+Glob "**/src/services/[module]/modules/*/domain/entity/*.go"      # → Example entities
+Glob "**/src/services/[module]/modules/*/domain/valueobject/*.go" # → Example VOs
+Glob "**/src/services/[module]/modules/*/application/usecase/*"   # → Example use cases
 ```
-1. The epic this story belongs to - for context and dependencies
-2. Other stories in the epic - for coordination
+
+**Pick 1-2 existing files as patterns for Documentation links in tasks.**
+
+### Step 4: Read Parent Epic
+
+```bash
+Glob "**/epic-[NN]*.md"                     # → Find and read the epic
 ```
 
 ### Pre-Story Checklist
 
-Before writing story tasks, confirm you have read:
-- [ ] CLAUDE.md - coding patterns and file structure
-- [ ] Coding standards - naming, error handling, testing
-- [ ] Module architecture - component boundaries
-- [ ] Parent epic - scope and dependencies
+Before writing tasks, confirm you executed:
+- [ ] **Glob + Read** AGENTS.md/CLAUDE.md 
+- [ ] **Glob + Read** coding-standards/*.md (ALL files)
+- [ ] **Glob + Read** module architecture and data-model
+- [ ] **Glob + Read** existing code patterns (at least 2 files)
+- [ ] **Read** parent epic
 
-**⚠️ DO NOT write technical tasks without reading coding standards!**
-**Tasks MUST follow project conventions and patterns from CLAUDE.md.**
+**⛔ DO NOT WRITE TASKS WITHOUT COMPLETING ALL STEPS ABOVE!**
+**Tasks without proper Documentation links = REJECTED.**
 
 ### Task File Paths