@fernado03/zoo-flow 0.11.3 → 0.12.0

package/bin/zoo-flow.js

@@ -13,34 +13,34 @@ const claudeCodeTemplateRoot = path.join(packageRoot, "templates", "claude-code"
 
 const COMMAND_POLICY = {
   routed: {
-    "tweak": "code-tweaker",
-    "tdd": "code-tweaker",
-    "update-docs": "code-tweaker",
-    "commit-and-document": "code-tweaker",
-    "prototype": "code-tweaker",
-    "scaffold-context": "code-tweaker",
-    "verify": "code-tweaker",
-    "fix": "system-architect",
-    "feature": "system-architect",
-    "refactor": "system-architect",
-    "explore": "system-architect",
-    "triage": "system-architect",
-    "review": "system-architect"
+    "zoo-tweak": "code-tweaker",
+    "zoo-tdd": "code-tweaker",
+    "zoo-update-docs": "code-tweaker",
+    "zoo-commit-and-document": "code-tweaker",
+    "zoo-prototype": "code-tweaker",
+    "zoo-scaffold-context": "code-tweaker",
+    "zoo-verify": "code-tweaker",
+    "zoo-fix": "system-architect",
+    "zoo-feature": "system-architect",
+    "zoo-refactor": "system-architect",
+    "zoo-explore": "system-architect",
+    "zoo-triage": "system-architect",
+    "zoo-review": "system-architect"
   },
   helpers: {
-    "diagnose": "system-architect",
-    "grill-with-docs": "system-architect",
-    "improve-codebase-architecture": "system-architect",
-    "to-prd": "system-architect",
-    "to-issues": "system-architect",
-    "zoom-out": "system-architect",
-    "handoff": "system-architect",
-    "grill-me": "system-architect",
-    "write-a-skill": "code-tweaker",
-    "setup-matt-pocock-skills": "code-tweaker",
-    "teach": "code-tweaker"
+    "zoo-diagnose": "system-architect",
+    "zoo-grill-with-docs": "system-architect",
+    "zoo-improve-codebase-architecture": "system-architect",
+    "zoo-to-prd": "system-architect",
+    "zoo-to-issues": "system-architect",
+    "zoo-zoom-out": "system-architect",
+    "zoo-handoff": "system-architect",
+    "zoo-grill-me": "system-architect",
+    "zoo-write-a-skill": "code-tweaker",
+    "zoo-setup-matt-pocock-skills": "code-tweaker",
+    "zoo-teach": "code-tweaker"
   },
-  modelessUtilities: ["caveman"]
+  modelessUtilities: ["zoo-caveman"]
 };
 
 const ALLOWED_COMMAND_MODES = new Set(["system-architect", "code-tweaker", "custom-orchestrator"]);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fernado03/zoo-flow",
-  "version": "0.11.3",
+  "version": "0.12.0",
   "description": "Structured workflow templates for AI coding assistants",
   "type": "module",
   "bin": {

package/templates/full/.roo/commands/{explore.md → zoo-explore.md}

@@ -1,18 +1,18 @@
----
-description: "Explore unfamiliar code before /feature, /refactor, or /fix. Produces written map."
-argument-hint: <feature or folder to map>
-mode: system-architect
----
-
-Explore unfamiliar code and produce a written map. Follow the skill exactly.
-
-Skill: `.roo/skills/engineering/zoom-out/SKILL.md`
-
-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. 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`.
-3. WRITE POINTER: Write the exact file path to `.scratch/LAST-EXPLORATION.md` so next commands can find it.
-4. NEXT STEPS: Suggest `/scaffold-context`, `/feature`, `/refactor`, or `/fix`. DO NOT auto-launch.
-5. COMPLETION: Call `attempt_completion` with the exact file path, status, and recommended next command. Do NOT use `ask_followup_question` or write results as plain text.
-
-$ARGUMENTS
+---
+description: "Explore unfamiliar code before /feature, /refactor, or /fix. Produces written map."
+argument-hint: <feature or folder to map>
+mode: system-architect
+---
+
+Explore unfamiliar code and produce a written map. Follow the skill exactly.
+
+Skill: `.roo/skills/engineering/zoom-out/SKILL.md`
+
+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. 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`.
+3. WRITE POINTER: Write the exact file path to `.scratch/LAST-EXPLORATION.md` so next commands can find it.
+4. NEXT STEPS: Suggest `/scaffold-context`, `/feature`, `/refactor`, or `/fix`. DO NOT auto-launch.
+5. COMPLETION: Call `attempt_completion` with the exact file path, status, and recommended next command. Do NOT use `ask_followup_question` or write results as plain text.
+
+$ARGUMENTS

package/templates/full/.roo/commands/{scaffold-context.md → zoo-scaffold-context.md}

@@ -1,16 +1,16 @@
----
-description: "Bootstrap .zoo-flow/CONTEXT.md (and 0-2 starter ADRs) for an existing project by scanning code for domain terms and cross-cutting decisions. Shows proposed entries inline and asks for confirm before writing. Use when starting Zoo Flow on a project with no CONTEXT.md, or to expand a thin one."
-argument-hint: <optional focus area, e.g. "auth", "billing", or empty for whole project>
-mode: code-tweaker
----
-
-Bootstrap .zoo-flow/CONTEXT.md for an existing project. Follow the skill exactly.
-
-Skill: `.roo/skills/engineering/scaffold-context/SKILL.md`
-
-EXECUTION RULES:
-1. APPLY the slot discovery rule from `.roo/skills/engineering/grill-with-docs/CONTEXT-FORMAT.md` to find current CONTEXT.md, ADRs.
-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.
-3. DO NOT auto-launch any follow-up commands.
-
-$ARGUMENTS
+---
+description: "Bootstrap .zoo-flow/CONTEXT.md (and 0-2 starter ADRs) for an existing project by scanning code for domain terms and cross-cutting decisions. Shows proposed entries inline and asks for confirm before writing. Use when starting Zoo Flow on a project with no CONTEXT.md, or to expand a thin one."
+argument-hint: <optional focus area, e.g. "auth", "billing", or empty for whole project>
+mode: code-tweaker
+---
+
+Bootstrap .zoo-flow/CONTEXT.md for an existing project. Follow the skill exactly.
+
+Skill: `.roo/skills/engineering/scaffold-context/SKILL.md`
+
+EXECUTION RULES:
+1. APPLY the slot discovery rule from `.roo/skills/engineering/grill-with-docs/CONTEXT-FORMAT.md` to find current CONTEXT.md, ADRs.
+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.
+3. DO NOT auto-launch any follow-up commands.
+
+$ARGUMENTS

package/templates/full/.roo/commands/{setup-matt-pocock-skills.md → zoo-setup-matt-pocock-skills.md}

@@ -1,8 +1,8 @@
----
-description: "Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, or `triage` — or if those skills appear to be missing issue tracker, triage label, or domain-doc configuration."
-mode: code-tweaker
----
-
+---
+description: "Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, or `triage` — or if those skills appear to be missing issue tracker, triage label, or domain-doc configuration."
+mode: code-tweaker
+---
+
 Skill: `.roo/skills/engineering/setup-matt-pocock-skills/SKILL.md`
-
-$ARGUMENTS
+
+$ARGUMENTS

package/templates/full/.roo/commands/{update-docs.md → zoo-update-docs.md}

@@ -1,22 +1,22 @@
----
-description: "Update repo documentation so it matches the current code."
-argument-hint: <doc or area to update>
-mode: code-tweaker
----
-
-Update repo documentation so it matches the current code. Surgical edits only — read existing docs first, verify claims against code, never rewrite wholesale unless the existing doc is unsalvageable. Follow the skill exactly.
-
-Skill: `.roo/skills/engineering/update-docs/SKILL.md`
-
-Find the target doc in `.zoo-flow/` or `docs/`. If it does not exist, ask once: "No <doc> found. Create a stub at .zoo-flow/<doc>? (yes / pick-existing / skip)".
-
-Do NOT use this for:
-
-- Domain glossary terms — use `/grill-with-docs`
-- ADRs — use `/grill-with-docs` or `/refactor`
-- Local commit journal entries — use `/commit-and-document`
-- Read-only understanding — use `/explore`
-
-If `$ARGUMENTS` is empty, ask once: "Which documentation file or area should I update?"
-
-$ARGUMENTS
+---
+description: "Update repo documentation so it matches the current code."
+argument-hint: <doc or area to update>
+mode: code-tweaker
+---
+
+Update repo documentation so it matches the current code. Surgical edits only — read existing docs first, verify claims against code, never rewrite wholesale unless the existing doc is unsalvageable. Follow the skill exactly.
+
+Skill: `.roo/skills/engineering/update-docs/SKILL.md`
+
+Find the target doc in `.zoo-flow/` or `docs/`. If it does not exist, ask once: "No <doc> found. Create a stub at .zoo-flow/<doc>? (yes / pick-existing / skip)".
+
+Do NOT use this for:
+
+- Domain glossary terms — use `/grill-with-docs`
+- ADRs — use `/grill-with-docs` or `/refactor`
+- Local commit journal entries — use `/commit-and-document`
+- Read-only understanding — use `/explore`
+
+If `$ARGUMENTS` is empty, ask once: "Which documentation file or area should I update?"
+
+$ARGUMENTS

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

@@ -44,25 +44,25 @@ Slash commands are internal routing labels unless the user explicitly typed one
 
 ## Routed commands
 
-| Workflow             | Command                | Mode             |
-| -------------------- | ---------------------- | ---------------- |
-| small implementation | `/tweak`               | code-tweaker     |
-| test-first           | `/tdd`                 | code-tweaker     |
-| documentation update | `/update-docs`         | code-tweaker     |
-| commit and journal   | `/commit-and-document` | code-tweaker     |
-| prototype            | `/prototype`           | code-tweaker     |
-| context scaffolding  | `/scaffold-context`    | code-tweaker     |
-| diagnosis            | `/fix`                 | system-architect |
-| feature planning     | `/feature`             | system-architect |
-| refactor planning    | `/refactor`            | system-architect |
-| exploration          | `/explore`             | system-architect |
-| issue triage         | `/triage`              | system-architect |
-| review               | `/review`              | system-architect |
-| verification         | `/verify`              | code-tweaker     |
+| Workflow             | Command                 | Mode             |
+| -------------------- | ----------------------- | ---------------- |
+| small implementation | `/zoo-tweak`            | code-tweaker     |
+| test-first           | `/zoo-tdd`              | code-tweaker     |
+| documentation update | `/zoo-update-docs`      | code-tweaker     |
+| commit and journal   | `/zoo-commit-and-document` | code-tweaker  |
+| prototype            | `/zoo-prototype`        | code-tweaker     |
+| context scaffolding  | `/zoo-scaffold-context` | code-tweaker     |
+| diagnosis            | `/zoo-fix`              | system-architect |
+| feature planning     | `/zoo-feature`          | system-architect |
+| refactor planning    | `/zoo-refactor`         | system-architect |
+| exploration          | `/zoo-explore`          | system-architect |
+| issue triage         | `/zoo-triage`           | system-architect |
+| review               | `/zoo-review`           | system-architect |
+| verification         | `/zoo-verify`           | code-tweaker     |
 
 ## Routing decision guide
 
-Read intent, not keywords. Top-down: 1. unknown code area or unclear next move → exploration; 2. broken behavior with unknown cause → diagnosis; 3. new capability needing design, PRD, issue slicing, or phase gates → feature planning; 4. working behavior but structure is the problem → refactor planning; 5. small known low-risk change → small implementation; 6. clear behavior and interface, user wants tests first → test-first; 7. throwaway design/state/UI uncertainty → prototype; 8. docs drift from code → documentation update; 9. finished work needs commit/journal → commit and journal; 10. issue creation, sorting, labels, or tracker workflow → issue triage; 11. diff, branch, PR, standards, architecture, or pre-commit inspection → review; 12. check if this passes, run tests for this change, verify the branch, or make sure nothing broke → verification.
+Read intent, not keywords. Top-down: 1. unknown code area or unclear next move → `/zoo-explore`; 2. broken behavior with unknown cause → `/zoo-fix`; 3. new capability needing design, PRD, issue slicing, or phase gates → `/zoo-feature`; 4. working behavior but structure is the problem → `/zoo-refactor`; 5. small known low-risk change → `/zoo-tweak`; 6. clear behavior and interface, user wants tests first → `/zoo-tdd`; 7. throwaway design/state/UI uncertainty → `/zoo-prototype`; 8. docs drift from code → `/zoo-update-docs`; 9. finished work needs commit/journal → `/zoo-commit-and-document`; 10. issue creation, sorting, labels, or tracker workflow → `/zoo-triage`; 11. diff, branch, PR, standards, architecture, or pre-commit inspection → `/zoo-review`; 12. check if this passes, run tests for this change, verify the branch, or make sure nothing broke → `/zoo-verify`.
 
 ## Routing weight
 
@@ -78,7 +78,7 @@ Diagnosis vs small implementation: unknown cause → diagnosis; known cause →
 
 ## Confidence and presentation
 
-Explicit slash command from user = approval; route as-is. Clear free-form request = recommend one plain-language workflow plus one safe alternative if useful. Genuine tie = offer numbered plain-language choices. Prefer lighter workflow when safe, but do not skip needed diagnosis, planning, or approval. Follow `.roo/rules/03-manual-reply-protocol.md`: no slash commands, mode names, or executable routing text in selectable options. Good free-form option: 1. Make the small implementation change; 2. Explore the area first. Bad free-form option: 1. `/tweak`; 2. `/explore`.
+Explicit slash command from user = approval; route as-is. Clear free-form request = recommend one plain-language workflow plus one safe alternative if useful. Genuine tie = offer numbered plain-language choices. Prefer lighter workflow when safe, but do not skip needed diagnosis, planning, or approval. Follow `.roo/rules/03-manual-reply-protocol.md`: no slash commands, mode names, or executable routing text in selectable options. Good free-form option: 1. Make the small implementation change; 2. Explore the area first. Bad free-form option: 1. `/zoo-tweak`; 2. `/zoo-explore`.
 
 ## Approval gate
 
@@ -94,8 +94,8 @@ For non-trivial work, suggest the next command chain only after the current comm
 
 Recommended chains:
 
-- test-first → verification → review → commit and journal
-- diagnosis → verification → review → commit and journal
-- refactor planning → verification → review → commit and journal
-- feature planning → verification → review → commit and journal
-- small implementation → verification or review when risk is R3+
+- `/zoo-tdd` → `/zoo-verify` → `/zoo-review` → `/zoo-commit-and-document`
+- `/zoo-fix` → `/zoo-verify` → `/zoo-review` → `/zoo-commit-and-document`
+- `/zoo-refactor` → `/zoo-verify` → `/zoo-review` → `/zoo-commit-and-document`
+- `/zoo-feature` → `/zoo-verify` → `/zoo-review` → `/zoo-commit-and-document`
+- `/zoo-tweak` → `/zoo-verify` or `/zoo-review` when risk is R3+

package/templates/full/.roo/skills/engineering/commit-and-document/SKILL.md

@@ -1,163 +1,163 @@
----
-name: commit-and-document
-description: Stage selected files, write a Conventional Commit, optionally link a GitHub issue, and append a dated journal entry under docs/journal/. Use when the user wants to commit work and capture a local record of what changed.
----
-
-# Commit and Document
-
-Deterministic flow. Execute steps in order; do not deviate.
-
-## 1. Inspect git changes
-
-Run and read:
-
-- `git status --short`
-- `git diff --stat`
-- `git diff --cached --stat`
-
-Summarise: which files, what changed.
-
-If the working tree is clean, stop and report. Skip the rest.
-
-## 2. Propose a Conventional Commit
-
-One-line message:
-
-```
-<type>(<scope>): <short, action-focused summary>
-```
-
-- **type**: `feat`, `fix`, `refactor`, `docs`, `chore`, `test`, `style`, `perf`
-- **scope**: area touched. Omit parens if unclear.
-- **summary**: imperative, present tense, under 70 chars, starts with a verb.
-
-Show: proposed message, files to stage, files excluded (tests, docs, secrets). Ask: "Commit with this message? (yes / edit / cancel)". On `edit`, accept the user's revised message verbatim and re-run detection (step 2.5) on it before proceeding. On `cancel`, stop and report.
-
-## 2.5 Detect or ask for an issue reference
-
-Silent pre-checks first:
-
-1. `git remote -v` → bail if no `github.com` remote.
-2. `command -v gh` → bail if `gh` is not installed.
-
-Detection on the proposed message:
-
-- Closing keywords: `Closes/Close/Closed/Fixes/Fix/Fixed/Resolves/Resolve/Resolved #N` (case-insensitive)
-- Bare `#N` anywhere
-
-Branches:
-
-- **A — closing keyword present**: ask "After commit, comment on issue #N and close it? (yes / no)". `yes` → `{action: close, issue: N}`.
-- **B — bare `#N`**: ask "After commit, post a progress comment on issue #N? (yes / no / close)". Map to `comment` / `close` / none.
-- **C — no reference**: ask once "Is this commit related to a GitHub issue? (issue number / no / skip)". On a number, ask "Comment only or close after commit? (comment / close)". Anything non-numeric → none.
-
-Carry the result as `issue_action` (default `none`).
-
-## 3. Stage and commit
-
-Stage explicit files with `git add <file>...` (never `git add .`). Exclude:
-
-- anything under `test/`, `tests/`, `__tests__/`, `spec/`, `specs/`
-- files matching `*.test.*`, `*.spec.*`, `test_*`, `*_test.*`
-- anything that looks like secrets (`.env`, credentials, tokens)
-
-Flag exclusions to the user.
-
-Commit with the approved message. Capture the short hash via `git rev-parse --short HEAD`.
-
-## 3.5 Act on the issue reference
-
-If `issue_action` is `none`, skip.
-
-Otherwise build:
-
-```
-> *This was generated by AI during commit.*
-
-Linked from commit `<short-hash>`: <commit subject>
-```
-
-Run `gh issue comment <N> --body "<body>"`. If `action == close`, then run `gh issue close <N>` (never `--comment`; comment first).
-
-If either fails, report the error and continue. Do not abort. Do not close an issue you could not comment on.
-
-## 4. Ensure docs/ is gitignored
-
-Read `.gitignore`. If no line matches `docs/`, append:
-
-```
-# Local documentation — never committed
-docs/
-```
-
-Do not commit the gitignore change. If the user accidentally staged anything under `docs/`, unstage it (`git restore --staged docs/<path>`) and warn.
-
-## 5. Inspect existing docs/journal/
-
-List `docs/journal/` if present. If it uses a different date/file convention than the default below, follow its existing convention. Create the directory if missing.
-
-## 6. Write a dated entry
-
-Date via `date +%Y-%m-%d`. Create `docs/journal/<YYYY-MM-DD>/` if missing. Write `<HH-MM>-<short-slug>.md` (kebab-case slug, 3–6 words from the summary). Template:
-
-```md
-# <Commit summary>
-
-**Commit:** <full hash>
-**Short hash:** <short hash>
-**Date:** <YYYY-MM-DD HH:MM local time>
-
-## What changed
-
-<2–4 sentences. Plain English, not a file list.>
-
-## Why
-
-<1–3 sentences on motivation, pulled from conversation context.>
-
-## Notes for future me
-
-<Gotchas/follow-ups, one paragraph max. Skip if nothing worth saying.>
-```
-
-## 7. Surface stale docs (if any)
-
-Read `git diff --cached --stat`. If any staged path overlaps with a path
-referenced in `.zoo-flow/CONTEXT.md`, output exactly one line
-before "Confirm":
-
-  "Public surface may have drifted. Run /update-docs? (yes / skip)"
-
-On `yes` → suggest `/update-docs <area>`. On `skip` → continue.
-
-## 8. Confirm
-
-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."
-
-## Complete
-
-Call `attempt_completion` with:
-- commit hash (short)
-- journal entry path
-- status (complete / blocked with reason)
-- recommended next command
-
-Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
-
-## Context economy
-
-Before broad reads, locate relevant files/symbols with `list_files`, `search_files`, or `codebase_search`.
-
-Prefer targeted `read_file` ranges or indentation/block reads once the relevant area is known.
-
-Read full files only when structure, ordering, or surrounding context is required for correctness.
-
-Do not re-read unchanged files; use prior findings unless the file changed.
-
-Use `git status --short`, `git diff --stat`, and targeted `git diff -- <file>` rather than dumping the full repo diff at once.
-
-## Safety
-
-- Never `git push`, `--amend`, `--force`, or `reset --hard`.
-- Flag suspected secrets; do not stage them.
-- If `git status` is clean, abort early.
+---
+name: commit-and-document
+description: Stage selected files, write a Conventional Commit, optionally link a GitHub issue, and append a dated journal entry under docs/journal/. Use when the user wants to commit work and capture a local record of what changed.
+---
+
+# Commit and Document
+
+Deterministic flow. Execute steps in order; do not deviate.
+
+## 1. Inspect git changes
+
+Run and read:
+
+- `git status --short`
+- `git diff --stat`
+- `git diff --cached --stat`
+
+Summarise: which files, what changed.
+
+If the working tree is clean, stop and report. Skip the rest.
+
+## 2. Propose a Conventional Commit
+
+One-line message:
+
+```
+<type>(<scope>): <short, action-focused summary>
+```
+
+- **type**: `feat`, `fix`, `refactor`, `docs`, `chore`, `test`, `style`, `perf`
+- **scope**: area touched. Omit parens if unclear.
+- **summary**: imperative, present tense, under 70 chars, starts with a verb.
+
+Show: proposed message, files to stage, files excluded (tests, docs, secrets). Ask: "Commit with this message? (yes / edit / cancel)". On `edit`, accept the user's revised message verbatim and re-run detection (step 2.5) on it before proceeding. On `cancel`, stop and report.
+
+## 2.5 Detect or ask for an issue reference
+
+Silent pre-checks first:
+
+1. `git remote -v` → bail if no `github.com` remote.
+2. `command -v gh` → bail if `gh` is not installed.
+
+Detection on the proposed message:
+
+- Closing keywords: `Closes/Close/Closed/Fixes/Fix/Fixed/Resolves/Resolve/Resolved #N` (case-insensitive)
+- Bare `#N` anywhere
+
+Branches:
+
+- **A — closing keyword present**: ask "After commit, comment on issue #N and close it? (yes / no)". `yes` → `{action: close, issue: N}`.
+- **B — bare `#N`**: ask "After commit, post a progress comment on issue #N? (yes / no / close)". Map to `comment` / `close` / none.
+- **C — no reference**: ask once "Is this commit related to a GitHub issue? (issue number / no / skip)". On a number, ask "Comment only or close after commit? (comment / close)". Anything non-numeric → none.
+
+Carry the result as `issue_action` (default `none`).
+
+## 3. Stage and commit
+
+Stage explicit files with `git add <file>...` (never `git add .`). Exclude:
+
+- anything under `test/`, `tests/`, `__tests__/`, `spec/`, `specs/`
+- files matching `*.test.*`, `*.spec.*`, `test_*`, `*_test.*`
+- anything that looks like secrets (`.env`, credentials, tokens)
+
+Flag exclusions to the user.
+
+Commit with the approved message. Capture the short hash via `git rev-parse --short HEAD`.
+
+## 3.5 Act on the issue reference
+
+If `issue_action` is `none`, skip.
+
+Otherwise build:
+
+```
+> *This was generated by AI during commit.*
+
+Linked from commit `<short-hash>`: <commit subject>
+```
+
+Run `gh issue comment <N> --body "<body>"`. If `action == close`, then run `gh issue close <N>` (never `--comment`; comment first).
+
+If either fails, report the error and continue. Do not abort. Do not close an issue you could not comment on.
+
+## 4. Ensure docs/ is gitignored
+
+Read `.gitignore`. If no line matches `docs/`, append:
+
+```
+# Local documentation — never committed
+docs/
+```
+
+Do not commit the gitignore change. If the user accidentally staged anything under `docs/`, unstage it (`git restore --staged docs/<path>`) and warn.
+
+## 5. Inspect existing docs/journal/
+
+List `docs/journal/` if present. If it uses a different date/file convention than the default below, follow its existing convention. Create the directory if missing.
+
+## 6. Write a dated entry
+
+Date via `date +%Y-%m-%d`. Create `docs/journal/<YYYY-MM-DD>/` if missing. Write `<HH-MM>-<short-slug>.md` (kebab-case slug, 3–6 words from the summary). Template:
+
+```md
+# <Commit summary>
+
+**Commit:** <full hash>
+**Short hash:** <short hash>
+**Date:** <YYYY-MM-DD HH:MM local time>
+
+## What changed
+
+<2–4 sentences. Plain English, not a file list.>
+
+## Why
+
+<1–3 sentences on motivation, pulled from conversation context.>
+
+## Notes for future me
+
+<Gotchas/follow-ups, one paragraph max. Skip if nothing worth saying.>
+```
+
+## 7. Surface stale docs (if any)
+
+Read `git diff --cached --stat`. If any staged path overlaps with a path
+referenced in `.zoo-flow/CONTEXT.md`, output exactly one line
+before "Confirm":
+
+  "Public surface may have drifted. Run /zoo-update-docs? (yes / skip)"
+
+On `yes` → suggest `/zoo-update-docs <area>`. On `skip` → continue.
+
+## 8. Confirm
+
+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."
+
+## Complete
+
+Call `attempt_completion` with:
+- commit hash (short)
+- journal entry path
+- status (complete / blocked with reason)
+- recommended next command
+
+Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
+
+## Context economy
+
+Before broad reads, locate relevant files/symbols with `list_files`, `search_files`, or `codebase_search`.
+
+Prefer targeted `read_file` ranges or indentation/block reads once the relevant area is known.
+
+Read full files only when structure, ordering, or surrounding context is required for correctness.
+
+Do not re-read unchanged files; use prior findings unless the file changed.
+
+Use `git status --short`, `git diff --stat`, and targeted `git diff -- <file>` rather than dumping the full repo diff at once.
+
+## Safety
+
+- Never `git push`, `--amend`, `--force`, or `reset --hard`.
+- Flag suspected secrets; do not stage them.
+- If `git status` is clean, abort early.

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

@@ -37,7 +37,7 @@ Rules:
 
 ## 3. Hypotheses (with working memory)
 
-Initialize session: `.scratch/diagnoses/<YYYY-MM-DD>/diagnose-<slug>/`
+Initialize session: `.scratch/diagnoses/<YYYY-MM-DD>/zoo-diagnose-<slug>/`
 
 Write `<session-dir>/session.md` with symptom, repro steps, error signatures.
 
@@ -97,7 +97,7 @@ MUST finish:
 - [ ] `[DEBUG-...]` logs removed from source.
 - [ ] Throwaway harnesses deleted/moved.
 - [ ] Winning hypothesis stated in commit/PR.
-- [ ] Seam/locality blocker → recommend `/improve-codebase-architecture`.
+- [ ] Seam/locality blocker → recommend `/zoo-improve-codebase-architecture`.
 
 Tweaker MUST `switch_mode` back to `system-architect` for Phase 7.
 
@@ -133,4 +133,4 @@ Call `attempt_completion` with:
 - root cause summary
 - fix applied
 - status
-- recommended next command (typically `/verify` then `/review` then `/commit-and-document`)
+- recommended next command (typically `/zoo-verify` then `/zoo-review` then `/zoo-commit-and-document`)

package/templates/full/.roo/skills/engineering/grill-with-docs/SKILL.md

@@ -16,7 +16,7 @@ description: Grilling session that challenges your plan against the existing dom
 
 ## Docs
 
-See `.roo/skills/engineering/grill-with-docs/CONTEXT-FORMAT.md` for layout and detection. Create docs lazily only when recording needed.
+See `.roo/skills/engineering/zoo-grill-with-docs/CONTEXT-FORMAT.md` for layout and detection. Create docs lazily only when recording needed.
 
 ## Context economy
 

package/templates/full/.roo/skills/engineering/improve-codebase-architecture/SKILL.md

@@ -60,6 +60,6 @@ Call `attempt_completion` with:
 - candidates found (count and titles)
 - user selection (which candidate was chosen, if any)
 - status (complete / blocked with reason)
-- recommended next command (`/refactor` to implement the chosen candidate, or `/feature` if it requires PRD + issue slicing)
+- recommended next command (`/zoo-refactor` to implement the chosen candidate, or `/zoo-feature` if it requires PRD + issue slicing)
 
 Do NOT use `ask_followup_question` or write results as plain text without calling the tool.