@hanzlaa/rcode 3.4.9 → 3.4.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hanzlaa/rcode",
-  "version": "3.4.9",
+  "version": "3.4.10",
   "description": "rcode — the memory bank for AI-driven SaaS teams. Persistent project context, distinctive engineering personas, and phase-based workflows. Built by Rihal. Works in Claude Code, Cursor, Gemini, VS Code, and Antigravity.",
   "main": "cli/index.js",
   "bin": {

package/rihal/workflows/do.md

@@ -296,6 +296,7 @@ Evaluate `$QUESTION` against these routing rules. Apply the **first matching** r
 | Implement a story, "work on story", "dev story", "build story" | `/rihal-dev-story` | Story-level implementation |
 | Find gaps in milestone plans, "gaps in plans", "missing plan", "unplanned phases" | `/rihal-plan-milestone-gaps` | Identify and fill planning gaps |
 | Executing a phase, "build phase N", "run phase N", "implement phase" | `/rihal-execute` | Direct phase execution request |
+| `/rihal-phase <number>` where number matches an existing phase dir | `/rihal-execute <N>` | User mistyped phase instead of execute — detect bare integer + existing dir, route to execute |
 | Running all remaining phases automatically | `/rihal-autonomous` | Full autonomous execution |
 | A review or quality concern about existing work | `/rihal-verify-work` | Needs verification |
 | "Council", "discuss strategy", "should we" | `/rihal-council` | Multi-agent strategic discussion |

package/rihal/workflows/phase.md

@@ -14,7 +14,42 @@ If `$ARGUMENTS` is empty AND no flag is set:
 
 STOP — do not proceed.
 
-## Step 1 — Parse mode flags
+## Step 1 — Disambiguate numeric arguments BEFORE routing
+
+If `$ARGUMENTS` is a bare integer (e.g. `116`, `20`, `7`) with no other words or flags:
+
+```bash
+# Check if a phase directory matching this number already exists
+PHASE_NUM="$ARGUMENTS"
+EXISTING=$(find .planning/phases -maxdepth 1 -type d -name "${PHASE_NUM}-*" 2>/dev/null | head -1)
+```
+
+If `$EXISTING` is non-empty, the user typed a phase number that already exists — they almost certainly meant to operate on it, not create a new one. Stop and ask:
+
+```
+Phase {N} already exists: {directory name}
+
+What did you mean to do?
+
+  /rihal-execute {N}   — execute the sprint plan for this phase
+  /rihal-plan {N}      — re-plan or view the plan for this phase
+  /rihal-status        — see overall project status
+
+  /rihal-phase "{description}"   — add a NEW phase (put the description in quotes)
+```
+
+Do NOT proceed to add/insert/remove. Wait for the user to clarify.
+
+If `$ARGUMENTS` is a bare integer and `$EXISTING` is empty, it's an ambiguous but plausible new-phase name. Proceed to Step 2 but warn:
+
+```
+Note: "{N}" looks like a number. If you meant to execute/plan phase {N}, use /rihal-execute {N} or /rihal-plan {N}.
+Adding a new phase named "{N}" — press Ctrl+C to cancel, or continue.
+```
+
+Then proceed to Step 2.
+
+## Step 1b — Parse mode flags
 
 Inspect `$ARGUMENTS`:
 
@@ -24,7 +59,7 @@ Inspect `$ARGUMENTS`:
 
 Strip the mode flag and pass remaining args to the underlying workflow.
 
-## Step 2 — Dispatch to underlying workflow
+## Step 2 — Dispatch to underlying workflow (after disambiguation)
 
 Each mode is implemented by an existing workflow: