@comfanion/workflow 4.38.1-dev.15 → 4.38.1-dev.16

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@comfanion/workflow",
-  "version": "4.38.1-dev.15",
+  "version": "4.38.1-dev.16",
   "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.38.1-dev.15",
-  "buildDate": "2026-01-27T13:37:51.112Z",
+  "version": "4.38.1-dev.16",
+  "buildDate": "2026-01-27T15:49:05.194Z",
   "files": [
     ".gitignore",
     "config.yaml",

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

@@ -255,11 +255,22 @@ Brief prose section with:
 - Each module gets its own FR table
 - Example: "Order Management Module" → FR-ORD-001, FR-ORD-002
 
-**Table format:**
+**Table format (with traceability):**
 
-| ID | Requirement | Priority |
-|----|-------------|----------|
-| FR-001 | {{requirement}} | P0 |
+| ID | Requirement | Priority | Module | Doc Section | Arch § | Epic | Status |
+|----|-------------|----------|--------|-------------|--------|------|--------|
+| FR-001 | {{requirement}} | P0 | {{module}} | → Unit: `{{name}}` | §{{N}} | → Epic: `{{file}}` | ⬜ |
+
+**Column filling:**
+- **@pm (you):** ID, Requirement, Priority, Module — filled when writing PRD
+- **@architect:** Doc Section, Arch § — filled when creating architecture/unit docs
+- **@pm:** Epic — filled when creating epics (`/epics`)
+- **@dev:** Status — marked ✅ when done
+
+**Doc Section format:**
+- Use `→ Unit: Name`, `→ Module: Name`, `→ Service: Name`, etc.
+- Examples: `→ Unit: Task`, `→ Module: Auth`, `→ Service: NotificationService`
+- Leave blank initially, @architect fills later
 
 With **Notes:** for business rules after each domain table.
 
@@ -272,10 +283,19 @@ FR-INV-001  # Inventory module
 
 ### 5. Non-Functional Requirements
 
-Tables for:
-- Performance (with metrics)
-- Security
-- Scalability
+**Table format (with traceability):**
+
+| ID | Requirement | Priority | Module | Doc Section | Arch § | Status |
+|----|-------------|----------|--------|-------------|--------|--------|
+| NFR-001 | {{requirement}} | P0 | — | — | §{{N}} | ⬜ |
+
+**Column filling:**
+- **@pm (you):** ID, Requirement, Priority, Module (if specific)
+- **@architect:** Doc Section (if specific), Arch §
+- **@dev:** Status
+
+**Optional details section:**
+Add Performance/Security/Scalability subsections if NFRs need detailed explanation.
 
 ### 6. Critical Business Rules
 

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

@@ -117,18 +117,21 @@ TaskFlow is a B2B platform for managing distributed teams. The system handles ta
 
 ## Functional Requirements
 
+> **Traceability:** Each FR tracks Module, Unit, Architecture section, Epic, and Status.
+> **Maintained by:** @pm (Epic), @architect (Module/Unit/Arch §), @dev (Status).
+
 ### {{Domain_1}}
 
-| ID | Requirement | Priority |
-|----|-------------|----------|
-| FR-001 | {{requirement}} | P0 |
-| FR-002 | {{requirement}} | P0 |
-| FR-003 | {{requirement}} | P1 |
+| ID | Requirement | Priority | Module | Doc Section | Arch § | Epic | Status |
+|----|-------------|----------|--------|-------------|--------|------|--------|
+| FR-001 | {{requirement}} | P0 | {{module}} | → Unit: `{{name}}` | §{{N}} | → Epic: `{{file}}` | ⬜ |
+| FR-002 | {{requirement}} | P0 | {{module}} | → Module: `{{name}}` | §{{N}} | → Epic: `{{file}}` | ⬜ |
+| FR-003 | {{requirement}} | P1 | {{module}} | → Service: `{{name}}` | §{{N}} | → Epic: `{{file}}` | ⬜ |
 
-<!-- e.g.
-| FR-001 | User can create task with title, description, due date | P0 |
-| FR-002 | User can assign task to team member | P0 |
-| FR-003 | System sends notification on assignment | P1 |
+<!-- Example:
+| FR-001 | User can create task with title, description, due date | P0 | Task | → Unit: `Task` | §3.1 | → Epic: `epic-01-task-crud.md` | ✅ |
+| FR-002 | User can assign task to team member | P0 | Task | → Unit: `Task` | §3.1 | → Epic: `epic-01-task-crud.md` | ⬜ |
+| FR-003 | System sends notification on assignment | P1 | Notification | → Service: `NotificationService` | §3.3 | → Epic: `epic-03-notifications.md` | ⬜ |
 -->
 
 **Notes:**
@@ -136,24 +139,40 @@ TaskFlow is a B2B platform for managing distributed teams. The system handles ta
 
 ### {{Domain_2}}
 
-| ID | Requirement | Priority |
-|----|-------------|----------|
-| FR-010 | {{requirement}} | P0 |
+| ID | Requirement | Priority | Module | Doc Section | Arch § | Epic | Status |
+|----|-------------|----------|--------|-------------|--------|------|--------|
+| FR-010 | {{requirement}} | P0 | {{module}} | → Unit: `{{name}}` | §{{N}} | → Epic: `{{file}}` | ⬜ |
 
 ---
 
 ## Non-Functional Requirements
 
+> **Traceability:** NFRs also track Module (if specific), Architecture section, and Status.
+
+| ID | Requirement | Priority | Module | Doc Section | Arch § | Status |
+|----|-------------|----------|--------|-------------|--------|--------|
+| NFR-001 | {{requirement}} | P0 | — | — | §{{N}} | ⬜ |
+| NFR-002 | {{requirement}} | P0 | {{module}} | → Unit: `{{name}}` | §{{N}} | ⬜ |
+
+<!-- Example:
+| NFR-001 | API response time < 200ms (p95) | P0 | — | — | §5 Performance | ⬜ |
+| NFR-002 | Task data encrypted at rest | P0 | Task | → Unit: `Task` | §4 Security | ⬜ |
+-->
+
+---
+
+## Non-Functional Requirements (Details)
+
+> Optional: Add detailed notes for complex NFRs here.
+
 ### Performance
-| Metric | Target |
-|--------|--------|
-| {{metric}} | {{value}} |
+- {{details_if_needed}}
 
 ### Security
-- {{requirement}}
+- {{details_if_needed}}
 
 ### Scalability
-- {{requirement}}
+- {{details_if_needed}}
 
 ---