@fernado03/zoo-flow 0.8.0 → 0.8.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,7 +1,7 @@
1
1
  {
2
2
  "name": "@fernado03/zoo-flow",
3
3
  "description": "Workflow control plane for Zoo Code.",
4
- "version": "0.8.0",
4
+ "version": "0.8.2",
5
5
  "type": "module",
6
6
  "bin": {
7
7
  "zoo-flow": "bin/zoo-flow.js"
@@ -134,6 +134,16 @@ On `yes` → suggest `/update-docs <area>`. On `skip` → continue.
134
134
 
135
135
  Report: commit hash + message, journal entry path, whether `.gitignore` was updated, and any issue actions taken. Close with: "All of `docs/` is gitignored, so this entry stays local."
136
136
 
137
+ ## Complete
138
+
139
+ Call `attempt_completion` with:
140
+ - commit hash (short)
141
+ - journal entry path
142
+ - status (complete / blocked with reason)
143
+ - recommended next command
144
+
145
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
146
+
137
147
  ## Context economy
138
148
 
139
149
  Before broad reads, locate relevant files/symbols with `list_files`, `search_files`, or `codebase_search`.
@@ -38,3 +38,13 @@ Do not re-read unchanged files; use prior findings unless the file changed.
38
38
  - Update `CONTEXT.md` immediately for resolved terms.
39
39
  - Keep `CONTEXT.md` glossary-only; no impl/spec notes.
40
40
  - Offer ADR only when hard to reverse + surprising + real trade-off; use `ADR-FORMAT.md`.
41
+
42
+ ## Complete
43
+
44
+ Call `attempt_completion` with:
45
+ - questions resolved (count)
46
+ - docs updated (CONTEXT.md, ADRs created/updated)
47
+ - status (complete / blocked with reason)
48
+ - recommended next command
49
+
50
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -53,3 +53,13 @@ Use searches to identify dependency/call patterns before reading full modules. R
53
53
  3. If term sharpened, update `CONTEXT.md` immediately.
54
54
  4. Durable rejected reason useful later → offer ADR.
55
55
  5. Interface options requested → run interface-design workflow.
56
+
57
+ ## Complete
58
+
59
+ Call `attempt_completion` with:
60
+ - report location (`{tmpdir}/architecture-review-{timestamp}.html`)
61
+ - candidates found (count)
62
+ - status (complete / blocked with reason)
63
+ - recommended next command
64
+
65
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -35,3 +35,13 @@ Do not re-read unchanged files; use prior findings unless the file changed.
35
35
  7. No polish: no tests, minimal errors, no abstractions.
36
36
  8. Surface full relevant state after each action/variant switch.
37
37
  9. Done → capture answer in commit/ADR/issue/`NOTES.md`; delete or fold into real code.
38
+
39
+ ## Complete
40
+
41
+ Call `attempt_completion` with:
42
+ - question answered
43
+ - prototype location (`.scratch/prototypes/<slug>/` or real module path)
44
+ - outcome (absorbed / discarded / needs decision)
45
+ - recommended next command
46
+
47
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -97,9 +97,16 @@ End with exactly one result line:
97
97
  - `Review result: changes requested`
98
98
  - `Review result: blocked`
99
99
 
100
- ## 6. Save
100
+ ## 6. Save and complete
101
101
 
102
- Write the full review (findings, axes, result) to `.scratch/reviews/<date>/review-<slug>.md`. Reference this file path in `attempt_completion` so the orchestrator can read and present it.
102
+ Write the full review (findings, axes, result) to `.scratch/reviews/<date>/review-<slug>.md`.
103
+
104
+ Call `attempt_completion` with:
105
+ - file path where review was saved
106
+ - brief result line (approve / approve with nits / changes requested / blocked)
107
+ - recommended next command
108
+
109
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
103
110
 
104
111
  ## Recommended next command
105
112
 
@@ -52,6 +52,16 @@ Checklist per cycle:
52
52
 
53
53
  After green, suggest `/verify`, then `/review`, then `/commit-and-document` for non-trivial work. Do not auto-launch follow-up commands.
54
54
 
55
+ ## Complete
56
+
57
+ Call `attempt_completion` with:
58
+ - what was implemented (behaviours, interfaces)
59
+ - tests written (count, pass/fail)
60
+ - status (complete / blocked with reason)
61
+ - recommended next command
62
+
63
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
64
+
55
65
  ## Context economy
56
66
 
57
67
  Before broad reads, locate relevant files/symbols with `list_files`, `search_files`, or `codebase_search`.
@@ -43,3 +43,12 @@ Issue tracker + label vocabulary should exist; run `/setup-matt-pocock-skills` i
43
43
  ```
44
44
 
45
45
  If no blockers: `None - can start immediately`.
46
+
47
+ ## Complete
48
+
49
+ Call `attempt_completion` with:
50
+ - issues created (count, tracker URL or `.scratch/{feature-slug}/issues/`)
51
+ - status (published / blocked with reason)
52
+ - recommended next command
53
+
54
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -55,3 +55,12 @@ RULE: Do not interview user. Synthesize current context.
55
55
 
56
56
  {other notes}
57
57
  ```
58
+
59
+ ## Complete
60
+
61
+ Call `attempt_completion` with:
62
+ - PRD location (issue tracker URL or `.scratch/{feature-slug}/PRD.md`)
63
+ - status (published / blocked with reason)
64
+ - recommended next command
65
+
66
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -77,3 +77,12 @@ Show counts + one-line summaries. Let maintainer pick.
77
77
  ```
78
78
 
79
79
  Rules: capture resolved info; ask specific/actionable questions; on resume, do not re-ask answered questions.
80
+
81
+ ## Complete
82
+
83
+ Call `attempt_completion` with:
84
+ - issues triaged (count, outcomes applied)
85
+ - status (complete / blocked with reason)
86
+ - recommended next command
87
+
88
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -17,6 +17,15 @@ Use for small known fixes.
17
17
  8. For R3+ risk, suggest `/verify` or `/review` before commit. Otherwise offer `/commit-and-document` only after user satisfied.
18
18
  9. Do not auto-launch follow-up commands.
19
19
 
20
+ ## Complete
21
+
22
+ Call `attempt_completion` with:
23
+ - what was changed (file paths, line ranges)
24
+ - status (complete / blocked with reason)
25
+ - recommended next command
26
+
27
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
28
+
20
29
  ## Context economy
21
30
 
22
31
  Before broad reads, locate relevant files/symbols with `list_files`, `search_files`, or `codebase_search`.
@@ -64,3 +64,13 @@ Do not re-read unchanged files; use prior findings unless the file changed.
64
64
  ## 7. Recommend next step
65
65
 
66
66
  Recommend one: `/explore` (still unclear), `/feature` (plan emerged), `/refactor` (tangled-but-working code), `/fix` (bug found), `/commit-and-document` (done). Do not auto-run.
67
+
68
+ ## Complete
69
+
70
+ Call `attempt_completion` with:
71
+ - docs updated (file paths)
72
+ - what changed (summary)
73
+ - status (complete / blocked with reason)
74
+ - recommended next command
75
+
76
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -78,3 +78,14 @@ Reason: no verification command found
78
78
  ```
79
79
 
80
80
  Do not auto-launch any follow-up command.
81
+
82
+ ## 6. Complete
83
+
84
+ Write the full verification report to `.scratch/verify/<date>/verify-<slug>.md`.
85
+
86
+ Call `attempt_completion` with:
87
+ - file path where report was saved
88
+ - brief status (pass/fail/partial/blocked)
89
+ - recommended next command
90
+
91
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -11,3 +11,13 @@ description: Interview the user relentlessly about a plan or design until reachi
11
11
  4. Ask one question at a time.
12
12
  5. Include recommended answer.
13
13
  6. Inspect code instead of asking when code can answer.
14
+
15
+ ## Complete
16
+
17
+ Call `attempt_completion` with:
18
+ - decision tree branches resolved (count)
19
+ - key decisions made (summary)
20
+ - status (complete / blocked with reason)
21
+ - recommended next command
22
+
23
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -12,3 +12,11 @@ argument-hint: "What will the next session be used for?"
12
12
  4. Include suggested skills section.
13
13
  5. Reference artifacts by path/URL; do not duplicate.
14
14
  6. Redact secrets/API keys/passwords/PII.
15
+
16
+ ## Complete
17
+
18
+ Call `attempt_completion` with:
19
+ - handoff file path (OS temp dir)
20
+ - status (complete / blocked with reason)
21
+
22
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -105,3 +105,15 @@ Default: attempt an answer, then route to a high-reputation community from `RESO
105
105
  ## `NOTES.md`
106
106
 
107
107
  The user will sometimes express preferences of how they want to be taught, or things you should keep in mind. This is the place to record those preferences, so you can refer back to them when designing lessons or working with the user.
108
+
109
+ ## Complete
110
+
111
+ When the user ends the teaching session or says "done" / "stop teaching":
112
+
113
+ Call `attempt_completion` with:
114
+ - lessons created (count, paths)
115
+ - mission status (created / updated)
116
+ - learning records updated (count)
117
+ - status (session complete / paused)
118
+
119
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -50,3 +50,12 @@ Add when: deterministic op; repeated code; explicit error handling needed.
50
50
  - [ ] Terminology consistent.
51
51
  - [ ] Examples concrete.
52
52
  - [ ] References one level deep.
53
+
54
+ ## Complete
55
+
56
+ Call `attempt_completion` with:
57
+ - skill created (name, path)
58
+ - files written (SKILL.md, references, scripts)
59
+ - status (complete / blocked with reason)
60
+
61
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.