@graypark/ralph-codex 0.5.0 → 0.5.1

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,6 +1,6 @@
1
1
  {
2
2
  "name": "@graypark/ralph-codex",
3
- "version": "0.5.0",
3
+ "version": "0.5.1",
4
4
  "type": "module",
5
5
  "description": "Ralph Loop for Codex CLI & Claude Code — iterative dev loops with multi-agent orchestration, interactive interview, and stop hooks",
6
6
  "license": "MIT",
@@ -265,12 +265,13 @@ To cancel at any time: `/ralph-loop:cancel-ralph`
265
265
 
266
266
  ### Quick-Run Flow
267
267
 
268
- If the user includes phrases like "run immediately", "just do it", "바로 실행", "바로 시작", or "--run" in their initial message:
268
+ If the user includes phrases like "run immediately", "just do it", "run it", "바로 실행", "바로 시작", or "--run" in their initial message:
269
269
 
270
270
  1. Conduct the interview as normal (skip if enough context is provided).
271
271
  2. Generate the command blocks.
272
- 3. **Set up pipeline state file with queue** and **immediately execute Phase 1** without confirmation.
273
- 4. Show the command and queue that was set up so the user can see what's running.
272
+ 3. For multi-phase: write state file with queue via Bash.
273
+ 4. Show the generated command briefly.
274
+ 5. Immediately call the Skill tool with skill="ralph-loop:ralph-loop" and the Phase 1 args. Do NOT wait for user confirmation.
274
275
 
275
276
  ### Post-Generation Action
276
277
 
@@ -299,15 +300,21 @@ After generating all command blocks, ALWAYS end with this prompt:
299
300
 
300
301
  ### Execution Modes
301
302
 
303
+ IMPORTANT: When the user confirms execution, you MUST actually start the loop by calling the Skill tool with skill "ralph-loop:ralph-loop" and the generated args. Do NOT just write a state file or print the command. The Skill tool invocation is what triggers the real loop.
304
+
302
305
  **Pipeline mode (default for "y"):**
303
306
 
304
- 1. Create the state file with the first phase as active and remaining phases in `queue`
305
- 2. Execute Phase 1 via `/ralph-loop:ralph-loop`
306
- 3. When Phase 1 promise is detected, the stop hook automatically loads Phase 2 from queue
307
- 4. Continues until all phases complete — no user intervention between phases
307
+ 1. For multi-phase: write the state file with queue via Bash
308
+ 2. Call the Skill tool: skill="ralph-loop:ralph-loop", args="<Phase 1 prompt> --max-iterations N --completion-promise PROMISE"
309
+ 3. The stop hook handles phase transitions automatically
308
310
 
309
311
  **Manual mode ("step"):**
310
312
 
311
- 1. Execute Phase 1 via `/ralph-loop:ralph-loop`
312
- 2. When Phase 1 completes, prompt the user to confirm before starting Phase 2
313
- 3. Repeat for each phase
313
+ 1. Call the Skill tool: skill="ralph-loop:ralph-loop", args="<Phase 1 prompt> --max-iterations N --completion-promise PROMISE"
314
+ 2. When Phase 1 completes, ask user before calling Skill tool again for Phase 2
315
+
316
+ **Single-phase ("y"):**
317
+
318
+ 1. Call the Skill tool: skill="ralph-loop:ralph-loop", args="<prompt> --max-iterations N --completion-promise PROMISE"
319
+
320
+ After the user says "y", "yes", or similar, you MUST immediately use the Skill tool. Do not just describe what would happen. Do not tell the user to copy-paste. Actually invoke the skill.