@comfanion/workflow 4.36.62 → 4.36.64
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
package/src/build-info.json
CHANGED
|
@@ -25,13 +25,13 @@ Story task is a specification. @coder needs executable instruction with full con
|
|
|
25
25
|
- **What was done** - results of previous tasks that this task depends on
|
|
26
26
|
- **Imports** - what packages to use
|
|
27
27
|
|
|
28
|
-
### Add Implementation
|
|
28
|
+
### Add Implementation Direction
|
|
29
29
|
|
|
30
|
-
|
|
31
|
-
-
|
|
32
|
-
- Error handling approach
|
|
33
|
-
- Logging requirements
|
|
34
|
-
- Validation rules
|
|
30
|
+
Provide guidance, not code:
|
|
31
|
+
- Interface signatures (what methods to implement)
|
|
32
|
+
- Error handling approach (what errors to return)
|
|
33
|
+
- Logging requirements (what to log)
|
|
34
|
+
- Validation rules (what to validate)
|
|
35
35
|
|
|
36
36
|
### Add Verification
|
|
37
37
|
|
|
@@ -62,8 +62,8 @@ Structure:
|
|
|
62
62
|
### Requirements
|
|
63
63
|
[Numbered list of what to implement with signatures/details]
|
|
64
64
|
|
|
65
|
-
###
|
|
66
|
-
[
|
|
65
|
+
### Pattern Reference
|
|
66
|
+
[Link to existing similar code to follow, NOT ready implementation]
|
|
67
67
|
|
|
68
68
|
### Error Handling
|
|
69
69
|
[How to handle errors]
|
|
@@ -115,6 +115,24 @@ Context: code to test, existing test examples
|
|
|
115
115
|
Requirements: test scenarios, mocks
|
|
116
116
|
Pattern: existing test structure
|
|
117
117
|
|
|
118
|
+
## Implementation is @coder's Job
|
|
119
|
+
|
|
120
|
+
**DO NOT give ready code. Give direction.**
|
|
121
|
+
|
|
122
|
+
✅ **DO provide:**
|
|
123
|
+
- Links to existing code as pattern reference
|
|
124
|
+
- Interface signatures (method names, params, return types)
|
|
125
|
+
- Requirements (what logic to implement)
|
|
126
|
+
- Error handling approach
|
|
127
|
+
- Validation rules
|
|
128
|
+
|
|
129
|
+
❌ **DO NOT provide:**
|
|
130
|
+
- Full method implementations
|
|
131
|
+
- Ready-to-copy code blocks
|
|
132
|
+
- Complete structs with all logic
|
|
133
|
+
|
|
134
|
+
**@coder writes the implementation.** Give direction, not solution.
|
|
135
|
+
|
|
118
136
|
## Methodology
|
|
119
137
|
|
|
120
138
|
Include in task based on config.yaml:
|
|
@@ -95,6 +95,24 @@ Summary table + detailed tasks.
|
|
|
95
95
|
- [ ] Tests pass
|
|
96
96
|
- [ ] Code reviewed
|
|
97
97
|
|
|
98
|
+
## No Code in Stories
|
|
99
|
+
|
|
100
|
+
**Stories are specifications, not implementations.**
|
|
101
|
+
|
|
102
|
+
✅ **Task provides:**
|
|
103
|
+
- Goal (what to achieve)
|
|
104
|
+
- Read First (where to find patterns)
|
|
105
|
+
- Output Files (what to create)
|
|
106
|
+
- Approach (high-level steps)
|
|
107
|
+
- Done When (how to verify)
|
|
108
|
+
|
|
109
|
+
❌ **Task does NOT provide:**
|
|
110
|
+
- Code Sketch with implementation
|
|
111
|
+
- Ready-to-copy code blocks
|
|
112
|
+
- Full method bodies
|
|
113
|
+
|
|
114
|
+
**@coder writes the code.** Story defines WHAT, not HOW.
|
|
115
|
+
|
|
98
116
|
## Task Structure (MANDATORY)
|
|
99
117
|
|
|
100
118
|
Each task MUST be self-contained:
|