@comfanion/workflow 3.7.2 → 3.8.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@comfanion/workflow",
-  "version": "3.7.2",
+  "version": "3.8.0",
   "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-23T16:50:19.585Z",
+  "buildDate": "2026-01-23T17:01:07.473Z",
   "files": [
     "config.yaml",
     "FLOW.yaml",

package/src/opencode/config.yaml

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

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

@@ -18,6 +18,47 @@ Use this skill when you need to:
 - Define epic-level acceptance criteria
 - Track PRD coverage
 
+## MANDATORY: Load Technical Context First
+
+**Before writing ANY epic, you MUST read and understand:**
+
+### 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
+```
+
+### 2. Module/Domain Documentation (REQUIRED)
+```
+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
+```
+
+### 3. PRD Requirements (REQUIRED)
+```
+1. docs/prd.md - Functional requirements (FR-XXX)
+2. docs/requirements/ - Detailed requirements if exists
+```
+
+### 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
+
+**⚠️ DO NOT proceed without reading technical documentation!**
+**Epic MUST reference architecture sections and follow established patterns.**
+
+---
+
 ## Template
 
 Use template at: `@.opencode/templates/epic-template.md`

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

@@ -18,6 +18,67 @@ Use this skill when you need to:
 - Define technical implementation tasks
 - Specify test scenarios
 
+## MANDATORY: Load Technical Standards First
+
+**Before writing ANY story with tasks, you MUST read and understand:**
+
+### 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
+```
+
+### 2. Module Architecture (REQUIRED)
+```
+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
+```
+
+### 3. Parent Epic (REQUIRED)
+```
+1. The epic this story belongs to - for context and dependencies
+2. Other stories in the epic - for coordination
+```
+
+### 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
+
+**⚠️ DO NOT write technical tasks without reading coding standards!**
+**Tasks MUST follow project conventions and patterns from CLAUDE.md.**
+
+### Task File Paths
+
+When defining tasks, use EXACT paths following project structure:
+```
+src/services/[module]/
+├── cmd/api/main.go
+├── modules/[submodule]/
+│   ├── domain/
+│   │   ├── aggregate/[entity].go      ← Domain entities
+│   │   ├── valueobject/[vo].go        ← Value objects
+│   │   └── repository/[repo].go       ← Repository interfaces
+│   ├── application/
+│   │   └── usecase/[UseCase]/         ← Use case (4 files)
+│   │       ├── inport.go
+│   │       ├── dto.go
+│   │       ├── handler.go
+│   │       └── mappers.go
+│   └── infrastructure/
+│       ├── repo/[entity]_postgres.go  ← Repository impl
+│       └── http/[handler].go          ← HTTP handlers
+```
+
+---
+
 ## Template
 
 Use template at: `@.opencode/templates/story-template.md`

package/src/opencode/templates/epic-template.md

@@ -24,10 +24,23 @@
 **Enables (unlocks these):**
 - [Epic ID]: [brief reason]
 
+### Technical Documentation (MANDATORY)
+
+**Documents used to create this epic:**
+- [ ] `CLAUDE.md` - Project patterns and conventions
+- [ ] `docs/architecture.md` - Section: [specific section]
+- [ ] `docs/architecture/{{module}}/` - Module documentation
+  - [ ] `index.md` - Module overview
+  - [ ] `architecture.md` - Module design
+  - [ ] `data-model.md` - Database schema
+  - [ ] `api/` - API contracts
+  - [ ] `events/` - Event schemas
+
 ### Architecture References
 
-- [Link to architecture section]
-- [Link to data model]
+- [Link to architecture section that this epic implements]
+- [Link to data model section]
+- [Link to API contracts if applicable]
 
 ### PRD Coverage
 

package/src/opencode/templates/story-template.md

@@ -296,6 +296,22 @@ Settings → Editor → TODO → Add Pattern:
 
 <!-- Context for the developer implementing this story -->
 
+### Coding Standards Applied (MANDATORY)
+
+**Standards documents used for this story:**
+- [ ] `CLAUDE.md` - Project patterns, file structure, conventions
+- [ ] `docs/coding-standards/` - Detailed coding standards
+  - [ ] Naming conventions
+  - [ ] Error handling patterns
+  - [ ] Testing patterns
+- [ ] `docs/architecture/{{module}}/architecture.md` - Module-specific patterns
+
+**Key patterns from CLAUDE.md:**
+- File naming: `{{file_naming_pattern}}`
+- Package structure: `{{package_structure}}`
+- Error handling: `{{error_handling_pattern}}`
+- Test file naming: `{{test_naming_pattern}}`
+
 ### Architecture Requirements
 - Follow hexagonal architecture patterns
 - Domain layer must not import infrastructure
@@ -314,10 +330,12 @@ Settings → Editor → TODO → Add Pattern:
 ### Reference Files
 - `src/path/to/related/file` - [why relevant]
 - `docs/architecture.md#section` - [architecture guidance]
+- `CLAUDE.md#section` - [coding patterns]
 
 ### Patterns to Follow
-- See `CLAUDE.md` or `docs/coding-standards/` for coding standards
-- Follow project architecture patterns
+- **MANDATORY:** Follow patterns from `CLAUDE.md`
+- **MANDATORY:** Follow `docs/coding-standards/`
+- Match existing code style in module
 
 ### API/Interface
 ```