@fernado03/zoo-flow 0.11.2 → 0.11.3

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.
Files changed (26) hide show
  1. package/package.json +1 -1
  2. package/templates/claude-code/.claude/skills/engineering/commit-and-document/SKILL.md +2 -1
  3. package/templates/claude-code/.claude/skills/engineering/diagnose/SKILL.md +2 -1
  4. package/templates/claude-code/.claude/skills/engineering/explore/SKILL.md +1 -1
  5. package/templates/claude-code/.claude/skills/engineering/feature/SKILL.md +2 -1
  6. package/templates/claude-code/.claude/skills/engineering/fix/SKILL.md +2 -1
  7. package/templates/claude-code/.claude/skills/engineering/grill-with-docs/SKILL.md +2 -1
  8. package/templates/claude-code/.claude/skills/engineering/improve-codebase-architecture/SKILL.md +2 -1
  9. package/templates/claude-code/.claude/skills/engineering/prototype/SKILL.md +2 -1
  10. package/templates/claude-code/.claude/skills/engineering/refactor/SKILL.md +2 -1
  11. package/templates/claude-code/.claude/skills/engineering/review/SKILL.md +2 -1
  12. package/templates/claude-code/.claude/skills/engineering/scaffold-context/SKILL.md +2 -1
  13. package/templates/claude-code/.claude/skills/engineering/setup-matt-pocock-skills/SKILL.md +2 -1
  14. package/templates/claude-code/.claude/skills/engineering/tdd/SKILL.md +2 -1
  15. package/templates/claude-code/.claude/skills/engineering/to-issues/SKILL.md +2 -1
  16. package/templates/claude-code/.claude/skills/engineering/to-prd/SKILL.md +2 -1
  17. package/templates/claude-code/.claude/skills/engineering/triage/SKILL.md +2 -1
  18. package/templates/claude-code/.claude/skills/engineering/tweak/SKILL.md +2 -1
  19. package/templates/claude-code/.claude/skills/engineering/update-docs/SKILL.md +2 -1
  20. package/templates/claude-code/.claude/skills/engineering/verify/SKILL.md +2 -1
  21. package/templates/claude-code/.claude/skills/engineering/zoom-out/SKILL.md +2 -1
  22. package/templates/claude-code/.claude/skills/productivity/grill-me/SKILL.md +2 -1
  23. package/templates/claude-code/.claude/skills/productivity/handoff/SKILL.md +2 -1
  24. package/templates/claude-code/.claude/skills/productivity/teach/SKILL.md +2 -1
  25. package/templates/claude-code/.claude/skills/productivity/write-a-skill/SKILL.md +2 -1
  26. package/templates/claude-code/CLAUDE.md +23 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@fernado03/zoo-flow",
3
- "version": "0.11.2",
3
+ "version": "0.11.3",
4
4
  "description": "Structured workflow templates for AI coding assistants",
5
5
  "type": "module",
6
6
  "bin": {
@@ -30,7 +30,8 @@ Do not re-read unchanged files; use prior findings unless the file changed.
30
30
 
31
31
  ## Complete
32
32
 
33
- Return completion with:
33
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
34
+
34
35
  - commit hash
35
36
  - files changed
36
37
  - documentation updated
@@ -128,7 +128,8 @@ Write `<session-dir>/root-cause.md`:
128
128
 
129
129
  Write `<session-dir>/diagnosis.md` with full log (hypotheses, instrumentation results, timeline).
130
130
 
131
- Return completion with:
131
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
132
+
132
133
  - `<session-dir>/root-cause.md` path
133
134
  - root cause summary
134
135
  - fix applied
@@ -43,7 +43,7 @@ Look for:
43
43
 
44
44
  ## 4. Report findings
45
45
 
46
- Return completion with:
46
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
47
47
 
48
48
  - modules/components identified
49
49
  - key dependencies and relationships
@@ -50,7 +50,8 @@ Delegate to implementer profile via `Agent` tool. Implementer executes:
50
50
 
51
51
  ## 5. Verify and report
52
52
 
53
- Implementer returns completion with:
53
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
54
+
54
55
  - feature implemented
55
56
  - tests status (all passing)
56
57
  - recommended next command (typically `/verify` then `/review` then `/commit-and-document`)
@@ -41,7 +41,8 @@ Delegate to implementer profile via `Agent` tool. Implementer executes:
41
41
 
42
42
  ## 4. Verify and report
43
43
 
44
- Implementer returns completion with:
44
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
45
+
45
46
  - root cause identified
46
47
  - fix implemented
47
48
  - regression test added
@@ -29,7 +29,8 @@ Do not re-read unchanged files; use prior findings unless the file changed.
29
29
 
30
30
  ## Complete
31
31
 
32
- Return completion with:
32
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
33
+
33
34
  - documentation location
34
35
  - key findings and insights
35
36
  - recommended next command (typically `/feature` or `/refactor` if changes needed)
@@ -33,7 +33,8 @@ Do not re-read unchanged files; use prior findings unless the file changed.
33
33
 
34
34
  ## Complete
35
35
 
36
- Return completion with:
36
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
37
+
37
38
  - architecture proposal location
38
39
  - key improvements identified
39
40
  - recommended next command (typically `/refactor` to implement changes)
@@ -28,7 +28,8 @@ Do not re-read unchanged files; use prior findings unless the file changed.
28
28
 
29
29
  ## Complete
30
30
 
31
- Return completion with:
31
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
32
+
32
33
  - prototype location
33
34
  - findings and insights
34
35
  - recommendations for next steps (proceed with design, explore alternative, or abandon)
@@ -42,7 +42,8 @@ Delegate to implementer profile via `Agent` tool. Implementer executes:
42
42
 
43
43
  ## 4. Verify and report
44
44
 
45
- Implementer returns completion with:
45
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
46
+
46
47
  - what was refactored
47
48
  - structural improvements achieved
48
49
  - tests status (all passing)
@@ -125,7 +125,8 @@ Write `<session-dir>/synthesis.md` with:
125
125
  - Prioritized findings by severity
126
126
  - Result line: `approve` / `approve with nits` / `changes requested` / `blocked`
127
127
 
128
- Return completion with:
128
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
129
+
129
130
  - `<session-dir>/synthesis.md` path
130
131
  - brief result line (approve / approve with nits / changes requested / blocked)
131
132
  - recommended next command
@@ -38,7 +38,8 @@ Do not re-read unchanged files; use prior findings unless the file changed.
38
38
 
39
39
  ## Complete
40
40
 
41
- Return a summary with:
41
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
42
+
42
43
  - CONTEXT.md location
43
44
  - sections added/updated
44
45
  - recommended next command (typically `/explore` to deepen understanding, or `/feature`/`/refactor` to start work)
@@ -42,7 +42,8 @@ Do not re-read unchanged files; use prior findings unless the file changed.
42
42
 
43
43
  ## Complete
44
44
 
45
- Return a summary with:
45
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
46
+
46
47
  - configuration files updated
47
48
  - conventions document location
48
49
  - recommended next command (typically `/verify` to ensure config is valid)
@@ -54,7 +54,8 @@ After green, suggest `/verify`, then `/review`, then `/commit-and-document` for
54
54
 
55
55
  ## Complete
56
56
 
57
- Return a summary with:
57
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
58
+
58
59
  - what was implemented (behaviours, interfaces)
59
60
  - tests written (count, pass/fail)
60
61
  - status (complete / blocked with reason)
@@ -30,7 +30,8 @@ Do not re-read unchanged files; use prior findings unless the file changed.
30
30
 
31
31
  ## Complete
32
32
 
33
- Return completion with:
33
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
34
+
34
35
  - issues directory location
35
36
  - issue count and summary
36
37
  - dependency graph
@@ -33,7 +33,8 @@ Do not re-read unchanged files; use prior findings unless the file changed.
33
33
 
34
34
  ## Complete
35
35
 
36
- Return completion with:
36
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
37
+
37
38
  - PRD location
38
39
  - summary of requirements
39
40
  - recommended next command (typically `/to-issues` to break down into tasks)
@@ -30,7 +30,8 @@ Do not re-read unchanged files; use prior findings unless the file changed.
30
30
 
31
31
  ## Complete
32
32
 
33
- Return completion with:
33
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
34
+
34
35
  - triage document location
35
36
  - prioritized list summary
36
37
  - recommended next command (typically `/fix` for bugs, `/feature` for features, or `/refactor` for tech debt)
@@ -19,7 +19,8 @@ Use for small known fixes.
19
19
 
20
20
  ## Complete
21
21
 
22
- Return a summary with:
22
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
23
+
23
24
  - what was changed (file paths, line ranges)
24
25
  - status (complete / blocked with reason)
25
26
  - recommended next command
@@ -27,7 +27,8 @@ Do not re-read unchanged files; use prior findings unless the file changed.
27
27
 
28
28
  ## Complete
29
29
 
30
- Return completion with:
30
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
31
+
31
32
  - documentation files updated
32
33
  - summary of changes
33
34
  - recommended next command (typically `/verify` to ensure docs are accurate)
@@ -32,7 +32,8 @@ Do not re-read unchanged files; use prior findings unless the file changed.
32
32
 
33
33
  ## Complete
34
34
 
35
- Return completion with:
35
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
36
+
36
37
  - verification commands run
37
38
  - pass/fail status for each
38
39
  - recommended next command (typically `/review` if passed, or `/fix` if failed)
@@ -68,7 +68,8 @@ Do not re-read unchanged files; use prior findings unless the file changed.
68
68
 
69
69
  ## Complete
70
70
 
71
- Return completion with:
71
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
72
+
72
73
  - `<session-dir>/synthesis.md` file path
73
74
  - high-level structure summary
74
75
  - recommended next command (typically `/explore` for deeper dive, or `/feature`/`/refactor` if changes needed)
@@ -14,7 +14,8 @@ description: Interview the user about a plan or design until reaching shared und
14
14
 
15
15
  ## Complete
16
16
 
17
- Return a summary with:
17
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
18
+
18
19
  - decision tree branches resolved (count)
19
20
  - key decisions made (summary)
20
21
  - status (complete / blocked with reason)
@@ -15,6 +15,7 @@ argument-hint: "What will the next session be used for?"
15
15
 
16
16
  ## Complete
17
17
 
18
- Return a summary with:
18
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
19
+
19
20
  - handoff file path (OS temp dir)
20
21
  - status (complete / blocked with reason)
@@ -109,7 +109,8 @@ The user will sometimes express preferences of how they want to be taught, or th
109
109
 
110
110
  When the user ends the teaching session or says "done" / "stop teaching":
111
111
 
112
- Return a summary with:
112
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
113
+
113
114
  - lessons created (count, paths)
114
115
  - mission status (created / updated)
115
116
  - learning records updated (count)
@@ -53,7 +53,8 @@ Add when: deterministic op; repeated code; explicit error handling needed.
53
53
 
54
54
  ## Complete
55
55
 
56
- Return a summary with:
56
+ **COMPLETION PROTOCOL**: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
57
+
57
58
  - skill created (name, path)
58
59
  - files written (SKILL.md, references, scripts)
59
60
  - status (complete / blocked with reason)
@@ -122,6 +122,29 @@ Agent(
122
122
  )
123
123
  ```
124
124
 
125
+ ### Agent Completion Protocol
126
+
127
+ **Critical**: When delegating to an agent via the `Agent` tool, the agent must understand how to return its work:
128
+
129
+ 1. **Your final text message IS the return value** - The parent agent receives exactly what you write as your last message
130
+ 2. **Output the completion summary, then STOP** - Do not call any more tools after writing your completion
131
+ 3. **Be complete in your final message** - Include all required information (files changed, status, recommendations)
132
+
133
+ Add this to your agent prompts:
134
+ ```
135
+ COMPLETION PROTOCOL:
136
+ Your final text message is your return value to the parent agent.
137
+ When you finish, output a summary with:
138
+ - What was done
139
+ - Status: complete / blocked (with reason)
140
+ - Files changed (if any)
141
+ - Recommended next command (if any)
142
+
143
+ Then STOP - do not call any more tools or take any more actions.
144
+ ```
145
+
146
+ This is similar to how ultracode's Workflow tool handles subagent completion.
147
+
125
148
  ### Multi-Phase Commands
126
149
 
127
150
  Commands like `/fix`, `/feature`, and `/refactor` involve multiple phases: