@comfanion/workflow 4.36.41 → 4.36.43

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.43",
   "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.43",
+  "buildDate": "2026-01-24T23:17:57.477Z",
   "files": [
     "config.yaml",
     "FLOW.yaml",

package/src/opencode/FLOW.yaml

@@ -17,7 +17,7 @@ description: |
 # CONFIGURATION
 # =============================================================================
 config:
-  file: config.yaml
+  file: .opencode/config.yaml
   variables:
     - user_name
     - communication_language
@@ -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

@@ -1,7 +1,6 @@
 ---
-description: Create or update the Architecture document
+description: Use when creating or updating system architecture document. Designs modules, data ownership, integration patterns
 agent: architect
-model: anthropic/claude-sonnet-4-20250514
 ---
 
 # Architecture Creation/Update
@@ -47,7 +46,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/commands/archive.md

@@ -1,6 +1,6 @@
 ---
-description: Archive outdated documents while preserving history
-agent: archivist
+description: Use when archiving outdated documents or completed sprints while preserving history
+agent: pm
 ---
 
 # Archive Command

package/src/opencode/commands/change.md

@@ -1,5 +1,5 @@
 ---
-description: Manage change proposals for modifying existing documentation
+description: Use when managing change proposals for modifying existing documentation. Tracks deltas and impact
 agent: change-manager
 ---
 

package/src/opencode/commands/clarify.md

@@ -1,6 +1,6 @@
 ---
-description: Structured clarification of requirements before creating PRD/Architecture
-agent: requirements-analyst
+description: Use when clarifying requirements before creating PRD or Architecture. Asks structured questions to uncover gaps
+agent: analyst
 ---
 
 # Clarify Command

package/src/opencode/commands/code-review.md

@@ -1,3 +1,8 @@
+---
+description: Use when reviewing implemented code for quality, correctness, and adherence to project standards
+agent: dev
+---
+
 # /code-review Command
 
 Review implemented code for quality, correctness, and adherence to standards.
@@ -14,7 +19,7 @@ Review implemented code for quality, correctness, and adherence to standards.
 
 ## Agent
 
-This command invokes the **Dev** agent (Amelia) in review mode.
+This command invokes the **Dev** agent (Rick) in review mode.
 
 ## Process
 

package/src/opencode/commands/coding-standards.md

@@ -1,6 +1,6 @@
 ---
-description: Create or update coding standards documentation (modular, multiple files)
-agent: coding-standards
+description: Use when creating or updating coding standards documentation. Creates modular files for patterns, testing, API conventions
+agent: architect
 ---
 
 # Coding Standards Creation

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

@@ -1,3 +1,8 @@
+---
+description: Use when implementing a story using red-green-refactor TDD cycle. Finds next ready story or uses specified path
+agent: dev
+---
+
 # /dev-story Command
 
 Implement a story using red-green-refactor cycle with TODO tracking.
@@ -14,7 +19,7 @@ Implement a story using red-green-refactor cycle with TODO tracking.
 
 ## Agent
 
-This command invokes the **Dev** agent (Amelia).
+This command invokes the **Dev** agent (Rick).
 
 ## Process
 

package/src/opencode/commands/diagram.md

@@ -1,6 +1,6 @@
 ---
-description: Create technical diagrams (C4, sequence, ER, flowcharts) in Mermaid format
-agent: diagram-creator
+description: Use when creating technical diagrams - C4 architecture, sequence flows, ER data models, flowcharts in Mermaid format
+agent: architect
 ---
 
 # Diagram Creation

package/src/opencode/commands/epics.md

@@ -1,7 +1,6 @@
 ---
-description: Create epics from PRD and Architecture
-agent: sm
-model: anthropic/claude-sonnet-4-20250514
+description: Use when creating epics from PRD and Architecture. Breaks PRD requirements into implementable epics aligned with architecture modules
+agent: pm
 ---
 
 # Epic Creation

package/src/opencode/commands/help.md

@@ -1,6 +1,6 @@
 ---
-description: Analyze project state and suggest next steps (context-aware guidance)
-agent: workflow-orchestrator
+description: Use when needing guidance on project state, next steps, blockers, or quick wins in the workflow
+agent: pm
 ---
 
 # Help Command

package/src/opencode/commands/jira-sync.md

@@ -1,7 +1,6 @@
 ---
-description: Synchronize epics and stories with Jira
-agent: sm
-model: anthropic/claude-sonnet-4-20250514
+description: Use when synchronizing epics and stories with Jira. Creates issues, updates status, links branches
+agent: pm
 ---
 
 # Jira Synchronization

package/src/opencode/commands/module-docs.md

@@ -1,6 +1,6 @@
 ---
-description: Create detailed documentation for a module in docs/architecture/[module]/
-agent: module-docs
+description: Use when creating detailed documentation for a module - index.md, data-model.md, API specs, events
+agent: architect
 ---
 
 # Module Documentation

package/src/opencode/commands/prd.md

@@ -1,7 +1,6 @@
 ---
-description: Create or update the Product Requirements Document
+description: Use when creating or updating Product Requirements Document. Defines scope, FRs, NFRs, user journeys
 agent: pm
-model: anthropic/claude-sonnet-4-20250514
 ---
 
 # PRD Creation/Update

package/src/opencode/commands/quick.md

@@ -1,6 +1,6 @@
 ---
-description: Quick mode for small changes - minimal documentation workflow
-agent: workflow-orchestrator
+description: Use when making small changes (bug fixes, minor features) that don't need full documentation workflow
+agent: pm
 ---
 
 # Quick Mode

package/src/opencode/commands/requirements.md

@@ -1,7 +1,6 @@
 ---
-description: Gather and document FR/NFR requirements through stakeholder interview
+description: Use when gathering FR/NFR requirements through stakeholder interviews. First step before PRD
 agent: analyst
-model: anthropic/claude-sonnet-4-20250514
 ---
 
 # Requirements Gathering

package/src/opencode/commands/research.md

@@ -1,5 +1,5 @@
 ---
-description: Conduct technical, market, or domain research with structured documentation
+description: Use when conducting technical, market, or domain research. Creates structured research documentation
 agent: researcher
 ---
 

package/src/opencode/commands/search.md

@@ -1,5 +1,5 @@
 ---
-description: Semantic code search - find code by meaning, not just text
+description: Use when searching codebase semantically - find code by meaning, not just text matching
 agent: crawler
 ---
 

package/src/opencode/commands/sprint-plan.md

@@ -1,7 +1,6 @@
 ---
-description: Plan and manage sprints
-agent: sm
-model: anthropic/claude-sonnet-4-20250514
+description: Use when planning sprints, organizing epics into sprints, or tracking sprint progress. REQUIRES epics to exist first
+agent: pm
 ---
 
 # Sprint Planning

package/src/opencode/commands/stories.md

@@ -1,7 +1,6 @@
 ---
-description: Create stories for a specific epic
-agent: sm
-model: anthropic/claude-sonnet-4-20250514
+description: Use when creating stories for a specific epic. Breaks epic into implementable user stories with Given/When/Then acceptance criteria
+agent: pm
 ---
 
 # Story Creation

package/src/opencode/commands/unit-docs.md

@@ -1,5 +1,5 @@
 ---
-description: Document module/domain/service/entity/feature using Universal Unit format
+description: Use when documenting module/domain/service/entity using Universal Unit format with index.md, data-model.md
 agent: architect
 skills_loaded:
   - unit-writing

package/src/opencode/commands/validate.md

@@ -1,7 +1,6 @@
 ---
-description: Validate project artifacts (requirements, prd, architecture, epics)
+description: Use when validating project artifacts - requirements, PRD, architecture, or epics for completeness and quality
 agent: architect
-model: anthropic/claude-sonnet-4-20250514
 ---
 
 # Artifact Validation

package/src/opencode/commands/workflow-status.md

@@ -1,7 +1,6 @@
 ---
-description: Show project workflow status and suggest next steps
-agent: sprint-manager
-model: anthropic/claude-sonnet-4-20250514
+description: Use when checking project workflow status or getting guidance on next steps in the documentation pipeline
+agent: pm
 ---
 
 # Workflow Status

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/sprint-planning/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sprint-planning
-description: How to organize epics and stories into sprints, manage sprint-status.yaml, and track progress
+description: Use when organizing epics into sprints, creating sprint-status.yaml, or tracking sprint progress. REQUIRES epics to exist first - run /epics if none
 license: MIT
 compatibility: opencode
 metadata:
@@ -18,6 +18,34 @@ Use this skill when you need to:
 - Track sprint progress
 - Plan new sprints
 
+## Prerequisites
+
+**CRITICAL: Epics must exist before sprint planning!**
+
+```
+Check: ls docs/sprint-artifacts/backlog/epic-*.md 2>/dev/null || ls docs/sprint-artifacts/sprint-*/epic-*.md 2>/dev/null
+```
+
+| Check | Action if Missing |
+|-------|-------------------|
+| No epics in backlog or sprints | **STOP** → Run `/epics` first to create epics from PRD |
+| Epics exist but no stories | Epics can be planned, stories created later with `/stories` |
+| PRD missing | **STOP** → Run `/prd` first |
+
+### Dependency Chain
+
+```
+/prd → /architecture → /epics → /sprint-plan
+                          ↑
+                    YOU ARE HERE
+                    (need epics first!)
+```
+
+If user asks for sprint planning without epics:
+1. Inform them epics are required
+2. Offer to create epics first with `/epics`
+3. Only proceed with sprint planning after epics exist
+
 ## Sprint Duration
 
 - **Recommended:** 2 weeks

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
 -->
 
 ---