@fernado03/zoo-flow 0.7.14 → 0.7.15
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
|
@@ -11,7 +11,21 @@ If you entered this window via `switch_mode` (you are mid-chain, not the entry p
|
|
|
11
11
|
|
|
12
12
|
Before any `attempt_completion`, re-read the command body and confirm no later phase is assigned to another mode. If one is, `switch_mode` instead.
|
|
13
13
|
|
|
14
|
-
|
|
14
|
+
## How to call attempt_completion
|
|
15
|
+
|
|
16
|
+
`attempt_completion` is a tool call with a `result` parameter. You MUST call it as a tool, not as plain text. Example:
|
|
17
|
+
|
|
18
|
+
```
|
|
19
|
+
attempt_completion(result="Done. Changed X in file Y. Status: complete. Next: /verify")
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
Do NOT:
|
|
23
|
+
- Use `ask_followup_question` to present results (this keeps the subtask alive)
|
|
24
|
+
- Write the result as plain text without calling the tool
|
|
25
|
+
- Use `switch_mode` to return to the orchestrator (use `attempt_completion` instead)
|
|
26
|
+
- Stop without calling any completion tool
|
|
27
|
+
|
|
28
|
+
## What attempt_completion must include
|
|
15
29
|
|
|
16
30
|
- what was done (exact scope)
|
|
17
31
|
- files changed or inspected (paths)
|
|
@@ -20,10 +34,10 @@ Before any `attempt_completion`, re-read the command body and confirm no later p
|
|
|
20
34
|
- remaining risk (what was not checked or is uncertain)
|
|
21
35
|
- recommended next command (one only, no auto-launch)
|
|
22
36
|
|
|
23
|
-
Write long output (verification report, diff summary) to `.scratch/` with a descriptive path. `attempt_completion` must include: file path where output was saved, brief status, and recommended next command. The user will open the file to see full details.
|
|
24
|
-
|
|
25
|
-
Before running `git commit` or `git push`, halt and wait for explicit user approval. Never push unless explicitly asked.
|
|
26
|
-
|
|
37
|
+
Write long output (verification report, diff summary) to `.scratch/` with a descriptive path. `attempt_completion` must include: file path where output was saved, brief status, and recommended next command. The user will open the file to see full details.
|
|
38
|
+
|
|
39
|
+
Before running `git commit` or `git push`, halt and wait for explicit user approval. Never push unless explicitly asked.
|
|
40
|
+
|
|
27
41
|
For non-trivial `/tdd`, `/fix`, `/feature`, `/refactor`, or R3+ `/tweak` work, recommend `/verify` before `/review` before `/commit-and-document`. Do not auto-launch those commands.
|
|
28
42
|
|
|
29
43
|
If the user explicitly says to remember a project rule, or the same mistake has repeated, ask before appending a short lesson to `.zoo-flow/LESSONS.md`. Do not read or write lessons by default.
|
|
@@ -11,10 +11,26 @@ If you entered this window via `switch_mode` (you are mid-chain, not the entry p
|
|
|
11
11
|
|
|
12
12
|
Before any `attempt_completion`, re-read the command body and confirm no later phase is assigned to another mode. If one is, `switch_mode` instead.
|
|
13
13
|
|
|
14
|
+
## How to call attempt_completion
|
|
15
|
+
|
|
16
|
+
`attempt_completion` is a tool call with a `result` parameter. You MUST call it as a tool, not as plain text. Example:
|
|
17
|
+
|
|
18
|
+
```
|
|
19
|
+
attempt_completion(result="Done. Explored X. Status: complete. Next: /feature")
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
Do NOT:
|
|
23
|
+
- Use `ask_followup_question` to present results (this keeps the subtask alive)
|
|
24
|
+
- Write the result as plain text without calling the tool
|
|
25
|
+
- Use `switch_mode` to return to the orchestrator (use `attempt_completion` instead)
|
|
26
|
+
- Stop without calling any completion tool
|
|
27
|
+
|
|
28
|
+
## What attempt_completion must include
|
|
29
|
+
|
|
14
30
|
Do not use `attempt_completion` to avoid required implementation work. Write the full output (review findings, exploration map, diagnosis, plan) to `.scratch/` with a descriptive path. `attempt_completion` must include: file path where output was saved, brief status, and recommended next command. The user will open the file to see full details.
|
|
15
31
|
|
|
16
|
-
Halt for explicit user approval before testing a bug hypothesis, finalizing an architecture plan, publishing issues, or making irreversible decisions.
|
|
17
|
-
|
|
32
|
+
Halt for explicit user approval before testing a bug hypothesis, finalizing an architecture plan, publishing issues, or making irreversible decisions.
|
|
33
|
+
|
|
18
34
|
For non-trivial completed plans or reviews, recommend the next command only. Typical chain: implementation command -> `/verify` -> `/review` -> `/commit-and-document`. Do not auto-launch those commands.
|
|
19
35
|
|
|
20
36
|
If the user explicitly says to remember a project rule, or the same mistake has repeated, ask before appending a short lesson to `.zoo-flow/LESSONS.md`. Do not read or write lessons by default.
|