@fernado03/zoo-flow 0.7.7 → 0.7.9

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fernado03/zoo-flow",
   "description": "Workflow control plane for Zoo Code.",
-  "version": "0.7.7",
+  "version": "0.7.9",
   "type": "module",
   "bin": {
     "zoo-flow": "bin/zoo-flow.js"

package/templates/full/.roo/commands/explore.md

@@ -6,8 +6,9 @@ mode: system-architect
 EXECUTION RULES:
 1. READ `.zoo-flow/CONTEXT.md`. If it does not exist, output one line before step 2: "No CONTEXT.md found. Run /scaffold-context to fill, or continue without." Do not invent content.
 2. RUN skill: `.roo/skills/engineering/zoom-out/SKILL.md`.
-3. OUTPUT MAP: Create markdown with sections: Domain language, Modules, Data flow, Seams/callers, ADRs, Open questions. Write the full map to `.scratch/explorations/<date>/explore-<slug>.md`.
-4. NEXT STEPS: Suggest `/scaffold-context`, `/feature`, `/refactor`, or `/fix`. DO NOT auto-launch.
-5. COMPLETION: Reference the `.scratch/` file path in `attempt_completion`. The orchestrator will read and present it.
+3. OUTPUT MAP: Create markdown with sections: Domain language, Modules, Data flow, Seams/callers, ADRs, Open questions. Derive slug from the target area (e.g. "auth module" → `auth-module.md`). Write to `.scratch/explorations/<YYYY-MM-DD>/<slug>.md`.
+4. WRITE POINTER: Write the exact file path to `.scratch/LAST-EXPLORATION.md` so next commands can find it.
+5. NEXT STEPS: Suggest `/scaffold-context`, `/feature`, `/refactor`, or `/fix`. DO NOT auto-launch.
+6. COMPLETION: Include the exact file path in `attempt_completion`.
 
 $ARGUMENTS

package/templates/full/.roo/commands/feature.md

@@ -5,6 +5,7 @@ mode: system-architect
 ---
 EXECUTION RULES (Run sequentially. Wait for user between phases):
 0. TRACK: At start, write a phase checklist to `.scratch/feature-<slug>.md` (phases 1-5, each unchecked). Before any `switch_mode` or `attempt_completion`, update it. Do NOT `attempt_completion` while any phase is unchecked — `switch_mode` to the phase's owner instead.
+0b. READ `.scratch/LAST-EXPLORATION.md` if it exists to find the most recent exploration map. Reference it in phase 1.
 1. SHARPEN (Architect): Run skill `.roo/skills/engineering/grill-with-docs/SKILL.md`. Update docs.
    HARD STOP: Ask user to choose: Prototype OR skip to PRD.
 2. PROTOTYPE [Optional]: Follow `.roo/rules-system-architect/01-feature-prototype.md` for the architect→tweaker handoff.

package/templates/full/.roo/commands/fix.md

@@ -5,6 +5,7 @@ mode: system-architect
 ---
 EXECUTION RULES:
 0. TRACK: At start, write a phase checklist to `.scratch/fix-<slug>.md` (phases 1-5, each unchecked). Before any `switch_mode` or `attempt_completion`, update it. Do NOT `attempt_completion` while any phase is unchecked — `switch_mode` to the phase's owner instead.
+0b. READ `.scratch/LAST-EXPLORATION.md` if it exists to find the most recent exploration map. Reference it in phase 1.
 1. DIAGNOSE (Architect): Run skill `.roo/skills/engineering/diagnose/SKILL.md`. Run phases 1-3.
    HARD STOP: Present hypotheses. Wait for user selection. Ignore internal AFK rules.
 2. INSTRUMENT (Architect): Run phase 4 on chosen hypothesis. Find root cause.

package/templates/full/.roo/commands/refactor.md

@@ -5,6 +5,7 @@ mode: system-architect
 ---
 EXECUTION RULES:
 0. TRACK: At start, write a phase checklist to `.scratch/refactor-<slug>.md` (phases 1-3, each unchecked). Before any `switch_mode` or `attempt_completion`, update it. Do NOT `attempt_completion` while any phase is unchecked — `switch_mode` to the phase's owner instead.
+0b. READ `.scratch/LAST-EXPLORATION.md` if it exists to find the most recent exploration map. Reference it in phase 1.
 1. FIND (Architect): Run skill `.roo/skills/engineering/improve-codebase-architecture/SKILL.md`. List candidates.
    HARD STOP: Ask user which candidate to explore.
 2. GRILL (Architect): Run grilling loop. Update CONTEXT/ADRs inline.

package/templates/full/.roo/rules-code-tweaker/01-completion.md

@@ -20,7 +20,7 @@ Before any `attempt_completion`, re-read the command body and confirm no later p
 - remaining risk (what was not checked or is uncertain)
 - recommended next command (one only, no auto-launch)
 
-Before `attempt_completion`, present the full output to the user in a normal message if the work produced long results (verification report, diff summary). Then `attempt_completion` with only: brief status, file path if written to `.scratch/`, and recommended next command. The orchestrator summarizes completion messages — the user must see the full output first.
+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.
 
 Before running `git commit` or `git push`, halt and wait for explicit user approval. Never push unless explicitly asked.
 

package/templates/full/.roo/rules-custom-orchestrator/00-routing.md

@@ -6,12 +6,10 @@ Router only. No reading implementation files, editing, shell, or answering imple
 
 After `attempt_completion` from a worker, the orchestrator must:
 
-1. Show the worker's completion message (brief status + file path + recommended next command).
+1. Show the worker's completion message to the user (file path + brief status + recommended next command).
 2. Stop and wait for user input.
 
-The worker already presented the full output in a normal message before `attempt_completion`. The orchestrator does not need to repeat it.
-
-Do not route a new user message until the completion message is fully presented.
+The full output is in the `.scratch/` file referenced by the worker. The orchestrator does not read it — the user opens it in the editor.
 
 ## Hard delegation boundary
 

package/templates/full/.roo/rules-system-architect/02-completion.md

@@ -11,7 +11,7 @@ If you entered this window via `switch_mode` (you are mid-chain, not the entry p
 
 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.
 
-Do not use `attempt_completion` to avoid required implementation work. Before `attempt_completion`, present the full output to the user in a normal message so they see the complete details (review findings, exploration map, diagnosis, plan). Then `attempt_completion` with only: brief status, file path if written to `.scratch/`, and recommended next command. The orchestrator summarizes completion messages — the user must see the full output first.
+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.
 
 Halt for explicit user approval before testing a bug hypothesis, finalizing an architecture plan, publishing issues, or making irreversible decisions.