@fernado03/zoo-flow 0.7.3 → 0.7.4

package/package.json

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

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

@@ -6,8 +6,8 @@ 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.
+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. SAVE (Optional): Ask to save map to .scratch/explorations/<date>/explore-<slug>.md.
+5. COMPLETION: Reference the `.scratch/` file path in `attempt_completion`. The orchestrator will read and present it.
 
 $ARGUMENTS

package/templates/full/.roo/skills/engineering/diagnose/SKILL.md

@@ -82,3 +82,7 @@ MUST finish:
 - [ ] Throwaway harnesses deleted/moved.
 - [ ] Winning hypothesis stated in commit/PR.
 - [ ] Seam/locality blocker → recommend `/improve-codebase-architecture`.
+
+## 7. Save
+
+Write the full diagnosis (hypotheses, instrumentation, root cause, fix) to `.scratch/diagnoses/<date>/diagnose-<slug>.md`. Reference this file path in `attempt_completion` so the orchestrator can read and present it.

package/templates/full/.roo/skills/engineering/review/SKILL.md

@@ -97,6 +97,10 @@ End with exactly one result line:
 - `Review result: changes requested`
 - `Review result: blocked`
 
+## 6. Save
+
+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.
+
 ## Recommended next command
 
 If fixes are needed, recommend one next command only:

package/templates/full/.roo/skills/engineering/to-issues/SKILL.md

@@ -16,9 +16,10 @@ Issue tracker + label vocabulary should exist; run `/setup-matt-pocock-skills` i
 5. Present numbered breakdown: title; `HITL`/`AFK`; blockers; user stories.
 6. Ask user to validate granularity/deps/HITL/AFK/merge/split.
 7. Iterate until approved.
-8. Publish in dependency order.
-9. Apply `ready-for-agent` label unless instructed otherwise.
-10. DO NOT close/modify parent issue.
+8. Save approved issues to `.scratch/issues/<date>/issues-<slug>.md`.
+9. Publish in dependency order.
+10. Apply `ready-for-agent` label unless instructed otherwise.
+11. DO NOT close/modify parent issue.
 
 ## Issue template
 

package/templates/full/.roo/skills/engineering/to-prd/SKILL.md

@@ -15,8 +15,9 @@ RULE: Do not interview user. Synthesize current context.
 2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can.
 3. Check with the user that these seams match their expectations.
 4. Write PRD.
-5. Publish to issue tracker.
-6. Apply `ready-for-agent`.
+5. Save PRD to `.scratch/prds/<date>/prd-<slug>.md`.
+6. Publish to issue tracker.
+7. Apply `ready-for-agent`.
 
 ## PRD template