@comfanion/workflow 4.37.1 → 4.37.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@comfanion/workflow",
3
- "version": "4.37.1",
3
+ "version": "4.37.2",
4
4
  "description": "Initialize OpenCode Workflow system for AI-assisted development with semantic code search",
5
5
  "type": "module",
6
6
  "bin": {
@@ -1,6 +1,6 @@
1
1
  {
2
- "version": "4.37.1",
3
- "buildDate": "2026-01-26T20:31:11.486Z",
2
+ "version": "4.37.2",
3
+ "buildDate": "2026-01-26T20:36:35.766Z",
4
4
  "files": [
5
5
  "config.yaml",
6
6
  "FLOW.yaml",
@@ -96,9 +96,31 @@ permission:
96
96
  <phase name="1. Discovery">
97
97
  <action>Search for related documents (search → then glob/grep if needed)</action>
98
98
  <action>Read existing architecture, PRD, related modules</action>
99
- <action>If PRD exists: Read "Project Classification" section to understand size</action>
99
+ <action critical="MANDATORY">Read PRD "Project Classification" section (first section) to understand project size</action>
100
+ <action>If no PRD: Load skill `architecture-design` → check size guidelines table</action>
100
101
  <action>Identify what needs to be created/updated</action>
101
102
  </phase>
103
+
104
+ <size-awareness critical="MANDATORY">
105
+ BEFORE writing architecture, you MUST know project size:
106
+
107
+ 1. Read PRD → "Project Classification" section
108
+ 2. Note the size: TOY/SMALL/MEDIUM/LARGE/ENTERPRISE
109
+ 3. Load skill: architecture-design → see size guidelines table
110
+ 4. Adapt your architecture depth:
111
+ - TOY: 200-500 lines, simple diagram
112
+ - SMALL: 500-1000 lines, C4 Context+Container+Component
113
+ - MEDIUM: 1000-2000 lines, full C4 + break into MODULES
114
+ - LARGE: 2000-4000 lines, multiple files, DOMAINS
115
+ - ENTERPRISE: 4000+ lines, per-domain files
116
+
117
+ Example:
118
+ - PRD says "TOY" → Write 350 lines, 3 components, NO modules
119
+ - PRD says "MEDIUM" → Write 1500 lines, 3 MODULES with Unit docs
120
+
121
+ DON'T write 2000-line architecture for Tetris!
122
+ DON'T write 500-line architecture for E-commerce!
123
+ </size-awareness>
102
124
 
103
125
  <phase name="2. Planning">
104
126
  <action>Create tasklist with todowrite()</action>
@@ -148,8 +148,25 @@ permission:
148
148
  <instruction>BEFORE starting ANY work (PRD, epics, stories):</instruction>
149
149
 
150
150
  <step n="1">If PRD exists: Read "Project Classification" section (first section)</step>
151
- <step n="2">If no PRD: Load skill `prd-writing` to understand size classification</step>
152
- <step n="3">Adapt your approach based on size</step>
151
+ <step n="2">If no PRD yet: Load skill `prd-writing` → read "How to Classify Project Size" section</step>
152
+ <step n="3">Determine project size based on scope/complexity/data/integrations (NOT timeline!)</step>
153
+ <step n="4">If creating PRD: Fill "Project Classification" section FIRST before writing anything else</step>
154
+ <step n="5">Adapt your approach based on size</step>
155
+
156
+ <classification-reminder>
157
+ When creating PRD, you MUST:
158
+ 1. Load skill: prd-writing
159
+ 2. Read the classification guide in the skill
160
+ 3. Ask user about: scope, data model, integrations, team size
161
+ 4. Classify: TOY/SMALL/MEDIUM/LARGE/ENTERPRISE
162
+ 5. Fill Project Classification table in PRD (first section!)
163
+ 6. Then write rest of PRD according to that size
164
+
165
+ Example questions:
166
+ - "How many database tables do you expect?" (5-10 = SMALL, 20+ = MEDIUM)
167
+ - "How many external integrations?" (0-2 = SMALL, 3-5 = MEDIUM)
168
+ - "Is this a single app or multiple modules?" (single = SMALL, modules = MEDIUM)
169
+ </classification-reminder>
153
170
 
154
171
  <key-principle>
155
172
  TOY/SMALL → Flat structure, no modules