@comfanion/workflow 4.36.41 → 4.36.42

package/README.md

@@ -38,7 +38,7 @@ Development: /dev-story ↔ /code-review (loop until done)
 
 - **requirements-gathering** - Extract FR/NFR through interviews
 - **prd-writing** - Product requirements documents
-- **architecture-design** - Hexagonal/DDD patterns
+- **architecture-design** - System architecture patterns
 - **story-writing** - User stories with Given/When/Then AC
 - **dev-story** - Red-green-refactor implementation cycle
 - **jira-integration** - Bidirectional sync with Jira

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@comfanion/workflow",
-  "version": "4.36.41",
+  "version": "4.36.42",
   "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.41",
-  "buildDate": "2026-01-24T22:03:27.547Z",
+  "version": "4.36.42",
+  "buildDate": "2026-01-24T22:23:56.887Z",
   "files": [
     "config.yaml",
     "FLOW.yaml",

package/src/opencode/FLOW.yaml

@@ -370,7 +370,7 @@ agents:
     file: agents/architect.md
     expertise:
       - Distributed systems
-      - DDD, hexagonal architecture
+      - Architecture patterns (chooses based on context)
       - System design
     personality: Technical, precise, patterns-focused
     skills_used:

package/src/opencode/agents/architect.md

@@ -109,7 +109,7 @@ permission:
 
 <persona>
   <role>System Architect + Technical Design Leader</role>
-  <identity>Senior architect with expertise in distributed systems, cloud infrastructure, API design. DDD and hexagonal architecture expert.</identity>
+  <identity>Senior architect with expertise in distributed systems, cloud infrastructure, API design. Chooses architecture patterns based on project needs, not dogma.</identity>
   <communication_style>Calm, pragmatic, balancing 'what could be' with 'what should be.' Technical but accessible. Always considers trade-offs.</communication_style>
   <principles>
     - Channel expert lean architecture: distributed systems, cloud patterns, scalability
@@ -129,12 +129,14 @@ permission:
 </skills>
 
 <design-principles>
-  1. Hexagonal Architecture - Separate domain from infrastructure
+  1. Right Pattern for Context - Choose architecture style based on project needs (see architecture-design skill)
   2. Single Responsibility - Each module has one job
   3. Explicit Contracts - Clear interfaces between modules
-  4. Event-Driven - Loose coupling via events where appropriate
-  5. Idempotency - Operations should be safely retryable
-  6. Observability First - Design for debugging and monitoring
+  4. Separation of Concerns - Isolate business logic from infrastructure
+  5. Event-Driven Where Appropriate - Loose coupling via events when justified
+  6. Idempotency - Operations should be safely retryable
+  7. Observability First - Design for debugging and monitoring
+  8. Trade-off Aware - Document decisions with pros/cons in ADRs
 </design-principles>
 
 <documentation-structure hint="For unit-writing skill">

package/src/opencode/checklists/architecture-checklist.md

@@ -56,8 +56,8 @@ Use this checklist to validate architecture before proceeding to epic/story crea
 ## Design Quality
 
 ### Architecture Patterns
-- [ ] Chosen patterns documented (hexagonal, DDD, etc.)
-- [ ] Pattern choice justified
+- [ ] Chosen pattern documented (Layered, Hexagonal, Clean, Microservices, etc.)
+- [ ] Pattern choice justified with ADR
 - [ ] Consistent pattern application
 
 ### Module Design
@@ -93,9 +93,8 @@ Use this checklist to validate architecture before proceeding to epic/story crea
 
 ## Coding Standards Alignment
 
-- [ ] Architecture follows CLAUDE.md patterns
-- [ ] Hexagonal architecture enforced
-- [ ] Use case pattern applicable
+- [ ] Architecture follows AGENTS.md patterns
+- [ ] Chosen architecture pattern consistently applied
 - [ ] Testing strategy fits architecture
 
 ## ADR Quality

package/src/opencode/checklists/code-review-checklist.md

@@ -18,11 +18,11 @@ Use this checklist when reviewing implemented code before marking story as "done
 ## Code Quality
 
 ### Architecture Compliance
-- [ ] Follows hexagonal architecture
-- [ ] Domain layer has no infrastructure imports
-- [ ] Use cases have 4 files (inport, dto, handler, mappers)
+- [ ] Follows project's chosen architecture pattern (AGENTS.md)
+- [ ] Business logic isolated from infrastructure
+- [ ] Clear separation of concerns
 - [ ] Explicit mapping (no reflection libraries)
-- [ ] Dependencies flow correctly (infra → app → domain)
+- [ ] Dependencies flow correctly per chosen pattern
 
 ### Code Structure
 - [ ] Single responsibility principle followed

package/src/opencode/commands/architecture.md

@@ -47,7 +47,7 @@ $ARGUMENTS
 
 ## Alignment Checks
 
-- Follows hexagonal architecture (CLAUDE.md)
+- Follows project's chosen architecture pattern (AGENTS.md)
 - Matches existing code structure
 - NFRs have architectural support
 

package/src/opencode/opencode.json

@@ -2,8 +2,8 @@
   "$schema": "https://opencode.ai/config.json",
   
   "instructions": [
+    "AGENTS.md",
     ".opencode/FLOW.yaml",
-    "docs/requirements/requirements.md",
     "docs/prd.md",
     "docs/architecture.md"
   ],

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

@@ -175,7 +175,8 @@ ADR-[NNN]-[short-title].md
 
 Examples:
 - ADR-001-postgresql-database.md
-- ADR-002-hexagonal-architecture.md
+- ADR-002-architecture-pattern.md
+- ADR-003-api-versioning.md
 ```
 
 ### IDs

package/src/opencode/skills/architecture-design/template.md

@@ -31,7 +31,7 @@ author: {{author}}
 <!-- e.g.
 TaskFlow is a task management platform for distributed teams.
 
-**Architecture Pattern:** Modular Monolith with Hexagonal Architecture — enables independent scaling while keeping deployment simple
+**Architecture Pattern:** Modular Monolith — enables independent scaling while keeping deployment simple (pattern chosen based on team size and scale requirements)
 
 **Key Domains:**
 1. **Task Domain** (2 modules) — Task CRUD, assignments, status workflow
@@ -53,8 +53,8 @@ TaskFlow is a task management platform for distributed teams.
 | Communication | {{decision}} | {{why}} |
 
 <!-- e.g.
-| Architecture | Hexagonal (Ports & Adapters) | Organizational standard |
-| Database | PostgreSQL per module | Service isolation |
+| Architecture | Modular Monolith | Team size, deployment simplicity |
+| Database | PostgreSQL | ACID needed, team expertise |
 | Communication | REST sync + Kafka async | REST for queries, Kafka for events |
 -->
 

package/src/opencode/skills/code-review/SKILL.md

@@ -28,9 +28,9 @@ For each AC in the story:
 ### 3. Code Quality Review
 
 #### Architecture Compliance
-- [ ] Follows hexagonal architecture
-- [ ] Domain layer has no infrastructure imports
-- [ ] Use cases have 4 files (inport, dto, handler, mappers)
+- [ ] Follows project's chosen architecture pattern (see AGENTS.md)
+- [ ] Business logic isolated from infrastructure
+- [ ] Clear separation of concerns
 - [ ] Explicit mapping (no reflection libraries)
 
 #### Code Structure

package/src/opencode/skills/coding-standards/SKILL.md

@@ -58,7 +58,7 @@ docs/coding-standards/
 
 | Topic | Document | Key Rules |
 |-------|----------|-----------|
-| Project Layout | [project-structure.md](./project-structure.md) | Hexagonal, modules |
+| Project Layout | [project-structure.md](./project-structure.md) | Modules, structure |
 | Go Code | [go-standards.md](./go-standards.md) | Naming, errors, imports |
 | Testing | [testing-standards.md](./testing-standards.md) | 80% coverage, table-driven |
 | API | [api-standards.md](./api-standards.md) | REST, error format |
@@ -150,13 +150,12 @@ project/
 ```markdown
 # Architecture Patterns
 
-## Required Patterns
+## Chosen Pattern
 
-### Hexagonal Architecture
-[Description, when to use, example structure]
+### [Pattern Name] (e.g., Layered, Hexagonal, Clean, Vertical Slices)
+[Description, why chosen for this project, example structure]
 
-### Use Case Pattern
-[4-file structure, example]
+See architecture-design skill for pattern selection guidance.
 
 ### Repository Pattern
 [Interface in domain, implementation in infrastructure]

package/src/opencode/skills/diagram-creation/SKILL.md

@@ -202,7 +202,7 @@ C4Component
 
 ## Patterns Used
 
-- Hexagonal Architecture (Ports & Adapters)
+- [Project's chosen architecture pattern]
 - Dependency injection
 - Repository pattern
 ```

package/src/opencode/skills/prd-writing/template.md

@@ -31,7 +31,7 @@ author: {{author}}
 <!-- e.g.
 TaskFlow is a B2B platform for managing distributed teams. The system handles task management, real-time collaboration, and team analytics.
 
-**Architecture:** Modular Monolith with Hexagonal Architecture
+**Architecture:** Modular Monolith (pattern chosen based on team size and requirements)
 
 **Key Domains:**
 1. **Task Management** — CRUD, assignments, status workflow

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

@@ -19,7 +19,7 @@ size: S | M | L
 - {{what_this_story_does_NOT_do}}
 
 <!-- e.g.
-Implement CRUD operations for Task entity following hexagonal architecture.
+Implement CRUD operations for Task entity following project architecture.
 
 **Context:** This story is part of Epic 1 (Task Management Core). It focuses on the domain layer and repository.
 
@@ -52,8 +52,8 @@ Implement CRUD operations for Task entity following hexagonal architecture.
 | → Epic: `{{epic_path}}` | Technical Decisions | ADRs for this epic |
 
 <!-- e.g.
-| → `CLAUDE.md` | All | Project patterns, naming |
-| → `docs/coding-standards/` | All | **MANDATORY** — hexagonal, error handling |
+| → `AGENTS.md` | All | Project patterns, naming |
+| → `docs/coding-standards/` | All | **MANDATORY** — architecture, error handling |
 | → Unit: `Task` | Data Model, Operations | Fields, validation rules |
 | → `docs/architecture.md` | Task Module | Internal services, events |
 | → `docs/architecture.md#error-handling` | Error Handling | Error codes format |
@@ -76,7 +76,7 @@ Story is complete when:
 - [ ] Empty title returns validation error (400, TASK_001)
 - [ ] Task ID is UUID format
 - [ ] Tests cover: create, validation, duplicate handling
-- [ ] Code follows hexagonal architecture from coding-standards
+- [ ] Code follows architecture patterns from coding-standards
 -->
 
 ---