@fernado03/zoo-flow 0.8.5 → 0.8.7
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
|
@@ -4,10 +4,13 @@ argument-hint: <optional focus area, e.g. "auth", "billing", or empty for whole
|
|
|
4
4
|
mode: code-tweaker
|
|
5
5
|
---
|
|
6
6
|
|
|
7
|
+
Bootstrap .zoo-flow/CONTEXT.md for an existing project. Follow the skill exactly.
|
|
8
|
+
|
|
9
|
+
Skill: `.roo/skills/engineering/scaffold-context/SKILL.md`
|
|
10
|
+
|
|
7
11
|
EXECUTION RULES:
|
|
8
12
|
1. APPLY the slot discovery rule from `.roo/skills/engineering/grill-with-docs/CONTEXT-FORMAT.md` to find current CONTEXT.md, ADRs.
|
|
9
13
|
2. IF `.zoo-flow/CONTEXT.md` exists and is non-empty, ASK: skip / merge (default) / replace. Skip = do nothing. Merge = add only new terms, never overwrite. Replace = full rewrite from scan.
|
|
10
|
-
3.
|
|
11
|
-
4. DO NOT auto-launch any follow-up commands.
|
|
14
|
+
3. DO NOT auto-launch any follow-up commands.
|
|
12
15
|
|
|
13
16
|
$ARGUMENTS
|
|
@@ -2,9 +2,22 @@
|
|
|
2
2
|
|
|
3
3
|
A delegated task is the **entire command chain**, including every phase and every mode switch the command body defines — not the single phase you are currently running.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
## CRITICAL: Never switch to "code" mode
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
When implementation is needed, you MUST:
|
|
8
|
+
1. Call `attempt_completion` with the recommended next command (e.g., `/feature`)
|
|
9
|
+
2. Wait for the orchestrator to route the task
|
|
10
|
+
3. The orchestrator will delegate to `code-tweaker`
|
|
11
|
+
|
|
12
|
+
NEVER call `switch_mode` directly to "code", "Code", or any variant. The only valid mode slugs are:
|
|
13
|
+
- `code-tweaker` (for implementation)
|
|
14
|
+
- `system-architect` (for planning/review)
|
|
15
|
+
|
|
16
|
+
If you need implementation, call `attempt_completion` and recommend the next command. Do not switch modes yourself.
|
|
17
|
+
|
|
18
|
+
## Choosing your exit
|
|
19
|
+
|
|
20
|
+
- **More phases remain** (this or a later phase is assigned to `code-tweaker`, or control returns to you afterward): use `switch_mode` to `code-tweaker` (exact slug, never `code`). Never `attempt_completion`. Writing a plan, diagnosis, or `.scratch/` notes is not "done" — it is a handoff. Switch to `code-tweaker` to implement.
|
|
8
21
|
- **You are running the command's final phase** and it is complete or blocked: use `attempt_completion` to return to the orchestrator.
|
|
9
22
|
|
|
10
23
|
If you entered this window via `switch_mode` (you are mid-chain, not the entry point) and any phase remains, you hand back with `switch_mode`. Only the command's final phase returns to the orchestrator.
|