@fernado03/zoo-flow 0.8.3 → 0.8.5

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
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@fernado03/zoo-flow",
3
3
  "description": "Workflow control plane for Zoo Code.",
4
- "version": "0.8.3",
4
+ "version": "0.8.5",
5
5
  "type": "module",
6
6
  "bin": {
7
7
  "zoo-flow": "bin/zoo-flow.js"
@@ -3,12 +3,16 @@ description: "Explore unfamiliar code before /feature, /refactor, or /fix. Produ
3
3
  argument-hint: <feature or folder to map>
4
4
  mode: system-architect
5
5
  ---
6
+
7
+ Explore unfamiliar code and produce a written map. Follow the skill exactly.
8
+
9
+ Skill: `.roo/skills/engineering/zoom-out/SKILL.md`
10
+
6
11
  EXECUTION RULES:
7
12
  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.
8
- 2. RUN skill: `.roo/skills/engineering/zoom-out/SKILL.md`.
9
- 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`.
10
- 4. WRITE POINTER: Write the exact file path to `.scratch/LAST-EXPLORATION.md` so next commands can find it.
11
- 5. NEXT STEPS: Suggest `/scaffold-context`, `/feature`, `/refactor`, or `/fix`. DO NOT auto-launch.
12
- 6. COMPLETION: Include the exact file path in `attempt_completion`.
13
+ 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`.
14
+ 3. WRITE POINTER: Write the exact file path to `.scratch/LAST-EXPLORATION.md` so next commands can find it.
15
+ 4. NEXT STEPS: Suggest `/scaffold-context`, `/feature`, `/refactor`, or `/fix`. DO NOT auto-launch.
16
+ 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.
13
17
 
14
18
  $ARGUMENTS
@@ -216,3 +216,13 @@ paths.
216
216
 
217
217
  Confirm? (yes / edit / cancel)
218
218
  ```
219
+
220
+ ## Complete
221
+
222
+ Call `attempt_completion` with:
223
+ - file paths written (CONTEXT.md, ADRs, optional docs)
224
+ - terms added (count)
225
+ - status (complete / blocked with reason)
226
+ - recommended next command
227
+
228
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -75,3 +75,12 @@ Seed files: GitHub=`issue-tracker-github.md`; GitLab=`issue-tracker-gitlab.md`;
75
75
  ## Done
76
76
 
77
77
  Report created/updated files. State engineering skills now read `docs/agents/*.md`; user may edit directly.
78
+
79
+ ## Complete
80
+
81
+ Call `attempt_completion` with:
82
+ - files created/updated (AGENTS.md/CLAUDE.md, docs/agents/*.md)
83
+ - issue tracker configured
84
+ - status (complete / blocked with reason)
85
+
86
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
@@ -17,3 +17,13 @@ Read full files only when structure, ordering, or surrounding context is require
17
17
  Do not re-read unchanged files; use prior findings unless the file changed.
18
18
 
19
19
  Start with `list_files` and `search_files`/`codebase_search`. Read representative files and key entrypoints, not every file in the area.
20
+
21
+ ## Complete
22
+
23
+ Call `attempt_completion` with:
24
+ - modules mapped (list)
25
+ - key findings (summary)
26
+ - status (complete / blocked with reason)
27
+ - recommended next command
28
+
29
+ Do NOT use `ask_followup_question` or write results as plain text without calling the tool.