hool-cli 0.7.3 → 0.7.4

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/prompts/orchestrator.md +8 -8
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hool-cli",
3
- "version": "0.7.3",
3
+ "version": "0.7.4",
4
4
  "description": "Agent-Driven SDLC — scaffold and configure HOOL for any project",
5
5
  "bin": {
6
6
  "hool": "./dist/index.js"
package/prompts/orchestrator.md CHANGED
@@ -61,19 +61,19 @@ After the last interactive phase, the human is OUT. You run this loop autonomous
61
61
  b. Before any file edit: verify the file is in your writable paths. If not, dispatch the owning agent.
62
62
  c. Write a dispatch brief to `.hool/operations/context/TASK-XXX.md` with: what you need, why, which files matter, constraints from client-preferences.md
63
63
  d. Dispatch the assigned agent via CLI (see How to Dispatch Agents below) with the dispatch brief path and key file paths in the task prompt
64
- c. Agent finishes — run Post-Dispatch Health Check (see below)
65
- d. If health check fails (context overflow, error, crash) — handle per the failure table, re-dispatch if needed
66
- e. Verify: did the agent produce what was expected? Cross-check the agent's completion report against `git diff`.
67
- e. Mark task complete on task-board.md
68
- f. Commit: Stage the agent's modified files and commit with message:
64
+ e. Agent finishes — run Post-Dispatch Health Check (see below)
65
+ f. If health check fails (context overflow, error, crash) — handle per the failure table, re-dispatch if needed
66
+ g. Verify: did the agent produce what was expected? Cross-check the agent's completion report against `git diff`.
67
+ h. Mark task complete on task-board.md
68
+ i. Commit: Stage the agent's modified files and commit with message:
69
69
  "[description] (agent-name, TASK-XXX)"
70
70
  Example: "Add auth service endpoint (be-dev, TASK-005)"
71
71
  - Stage ONLY the files the agent modified (not `git add .`)
72
72
  - If parallel agents just completed, commit each agent's files separately in sequence
73
73
  - Never commit .hool/operations/ or .hool/memory/ files in the same commit as source code — commit those separately if needed
74
- g. Log to cold log
75
- h. Check: are there more tasks? -> go to 3a
76
- i. Check: did the agent surface issues? -> route them (see Feedback Routing)
74
+ j. Log to cold log
75
+ k. Check: are there more tasks? -> go to 3a
76
+ l. Check: did the agent surface issues? -> route them (see Feedback Routing)
77
77
  4. If no pending tasks:
78
78
  a. Check phase gate conditions
79
79
  b. If gate passes: advance current-phase.md, create tasks for next phase, go to 1