@hanzlaa/rcode 3.3.0 → 3.3.1

package/rihal/workflows/karpathy-audit.md

@@ -14,15 +14,15 @@ If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 **Usage:**
 ```
-/rihal:code-review --karpathy <phase> [--files=path1,path2]
-/rihal:code-review --karpathy <git-ref>..HEAD
+/rihal-code-review --karpathy <phase> [--files=path1,path2]
+/rihal-code-review --karpathy <git-ref>..HEAD
 ```
 
 **Examples:**
 ```
-/rihal:code-review --karpathy 03
-/rihal:code-review --karpathy 02 --files=src/
-/rihal:code-review --karpathy HEAD~5..HEAD
+/rihal-code-review --karpathy 03
+/rihal-code-review --karpathy 02 --files=src/
+/rihal-code-review --karpathy HEAD~5..HEAD
 ```
 
 <process>
@@ -44,7 +44,7 @@ Parse: `phase_found`, `phase_dir`, `phase_number`, `padded_phase`.
 
 If phase_found is false:
 ```
-Error: Phase ${PHASE_ARG} not found. Try /rihal:code-review --karpathy HEAD~5..HEAD to audit recent commits instead.
+Error: Phase ${PHASE_ARG} not found. Try /rihal-code-review --karpathy HEAD~5..HEAD to audit recent commits instead.
 ```
 
 If git ref format (contains ".." or has no digit at start):
@@ -343,7 +343,7 @@ Aggregate all findings into a structured report:
 ---
 
 **Generated:** {date}
-**Run:** /rihal:code-review --karpathy {original_arguments}
+**Run:** /rihal-code-review --karpathy {original_arguments}
 ```
 
 Write report to stdout and optionally to file `{phase_dir}/{padded_phase}-KARPATHY-AUDIT.md` if phase mode.
@@ -369,14 +369,14 @@ If FAIL:
 
 {list top 3 critical findings}
 
-Review the full report above. Use /rihal:code-review-fix to auto-fix some issues.
+Review the full report above. Use /rihal-code-review-fix to auto-fix some issues.
 ```
 
 **Next steps:**
 ```
 View full report: {report file path}
-Rerun: /rihal:code-review --karpathy {arguments}
-Auto-fix some issues: /rihal:code-review-fix {phase}
+Rerun: /rihal-code-review --karpathy {arguments}
+Auto-fix some issues: /rihal-code-review-fix {phase}
 ```
 </step>
 
@@ -395,7 +395,7 @@ Auto-fix some issues: /rihal:code-review-fix {phase}
 
 ## On Error
 
-- **Phase not found:** suggest `/rihal:code-review --karpathy HEAD~5..HEAD` as the git-ref fallback.
+- **Phase not found:** suggest `/rihal-code-review --karpathy HEAD~5..HEAD` as the git-ref fallback.
 - **No source files in diff:** report "no auditable changes in range" and STOP — do not invent findings.
 - **karpathy-guidelines.md missing:** print "Reference doc missing. Run: npx @hanzlaa/rcode install ." and STOP.
 - **Empty diff:** STOP gracefully, do not run principle checks against an empty input.

package/rihal/workflows/list-plans.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:list-plans
+# Workflow: rihal-list-plans
 
 <purpose>
 Display a table of all SPRINT.md plans across every phase in `.planning/phases/`. Gives a single-screen view of every plan in the project — phase, sprint ID, goal, story counts, point totals, and execution state. Use before starting new work to see what's already planned or in flight.
@@ -27,7 +27,7 @@ End with totals footer and Next Up routing hint.
 If `$ARGUMENTS` contains `--help` or `-h`:
 
 ```
-/rihal:list-plans [--phase <id>] [--status <state>] [--detail]
+/rihal-list-plans [--phase <id>] [--status <state>] [--detail]
 
   --phase <id>     Filter to one phase (e.g. 04 or 04-dashboard-refresh)
   --status <state> Filter by plan state: todo | active | done | blocked
@@ -48,7 +48,7 @@ If `$PHASES_DIR` does not exist, print:
 No plans yet. This project has no `.planning/phases/` directory.
 
 Create the first plan:
-  /rihal:plan "<task description>"
+  /rihal-plan "<task description>"
 ```
 
 STOP.
@@ -119,16 +119,16 @@ Totals: {N} plans · {done_stories}/{total_stories} stories · {done_pts}/{total
 
 Pick ONE suggestion based on the current state:
 
-- If there is an `active` plan → `Next: /rihal:sprint-status --sprint <id>` (that plan's sprint ID)
-- If no active but todos exist → `Next: /rihal:execute .planning/phases/<first-todo-phase>/SPRINT.md`
-- If a plan is `blocked` → `Next: /rihal:correct-course --phase <id>`
-- If all done → `Next: /rihal:new-milestone  (or `/rihal:sprint-planning` for the next sprint)`
+- If there is an `active` plan → `Next: /rihal-sprint-status --sprint <id>` (that plan's sprint ID)
+- If no active but todos exist → `Next: /rihal-execute .planning/phases/<first-todo-phase>/SPRINT.md`
+- If a plan is `blocked` → `Next: /rihal-correct-course --phase <id>`
+- If all done → `Next: /rihal-new-milestone  (or `/rihal-sprint-planning` for the next sprint)`
 
 If unplanned phases exist, also print:
 
 ```
 ⚠ Phases without SPRINT.md: {list}
-  Draft a plan:  /rihal:plan --phase <id>
+  Draft a plan:  /rihal-plan --phase <id>
 ```
 </process>
 

package/rihal/workflows/list-workspaces.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:list-workspaces
+# Workflow: rihal-list-workspaces
 
 <purpose>
 Display all active workspaces with summary status, creation date, and current phase. Use this to understand what parallel work is happening and switch contexts.
@@ -9,7 +9,7 @@ Display all active workspaces with summary status, creation date, and current ph
 If `$ARGUMENTS` contains only `--help` or `-h`:
 
 ```
-/rihal:list-workspaces [--detail]
+/rihal-list-workspaces [--detail]
 ```
 
 STOP — do not proceed.
@@ -21,7 +21,7 @@ Verify `.rihal/workspaces.csv` exists. If not:
 ```
 No workspaces defined yet. Create one:
 
-/rihal:new-workspace <name>
+/rihal-new-workspace <name>
 ```
 
 STOP.
@@ -75,7 +75,7 @@ Workspace: {NAME}
     - Active tasks: {count}
     - Phases completed: {count}
   
-  Use: /rihal:plan <task> --workspace={name}
+  Use: /rihal-plan <task> --workspace={name}
 ```
 
 ## Step 6 — Report
@@ -85,7 +85,7 @@ If no workspaces:
 ```
 No workspaces yet. Create one:
 
-/rihal:new-workspace <name>
+/rihal-new-workspace <name>
 ```
 
 Otherwise:
@@ -93,8 +93,8 @@ Otherwise:
 ```
 ✓ {count} active workspaces
   Use --detail for full status
-  Switch: /rihal:workspace <name>
-  Remove: /rihal:remove-workspace <name>
+  Switch: /rihal-workspace <name>
+  Remove: /rihal-remove-workspace <name>
 ```
 
 ## Success Criteria

package/rihal/workflows/map-codebase.md

@@ -52,13 +52,13 @@ End with closure banner + top findings summary:
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:map-codebase <argument-here>
+/rihal-map-codebase <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:map-codebase example 1
-/rihal:map-codebase example 2
+/rihal-map-codebase example 1
+/rihal-map-codebase example 2
 ```
 
 STOP — do not proceed.
@@ -404,14 +404,14 @@ Created .planning/codebase/:
 
 **Initialize project** — use codebase context for planning
 
-`/rihal:new-project`
+`/rihal-new-project`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- Re-run mapping: `/rihal:map-codebase`
+- Re-run mapping: `/rihal-map-codebase`
 - Review specific file: `cat .planning/codebase/STACK.md`
 - Edit any document before proceeding
 

package/rihal/workflows/milestone-summary.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:milestone-summary
+# Workflow: rihal-milestone-summary
 
 <purpose>
 Generate a human-readable summary of the current or specified milestone, including all phases, decisions, outcomes, and lessons learned. Output can be Markdown (default) or PDF. This creates a narrative view of the entire milestone arc.
@@ -9,13 +9,13 @@ Generate a human-readable summary of the current or specified milestone, includi
 If `$ARGUMENTS` contains only `--help` or `-h`:
 
 ```
-/rihal:milestone-summary [--format=markdown|pdf] [--include-decisions]
+/rihal-milestone-summary [--format=markdown|pdf] [--include-decisions]
 ```
 
 **Examples:**
 ```
-/rihal:milestone-summary
-/rihal:milestone-summary --format=pdf --include-decisions
+/rihal-milestone-summary
+/rihal-milestone-summary --format=pdf --include-decisions
 ```
 
 STOP — do not proceed.
@@ -35,7 +35,7 @@ If not found:
 ```
 ⚠ No active milestone. Create one:
 
-/rihal:new-milestone <name>
+/rihal-new-milestone <name>
 ```
 
 STOP. Store path as `$MILESTONE_DIR`.
@@ -188,8 +188,8 @@ If no phase summaries found:
 ```
 ⚠ No phase summaries in milestone. Execute phases first:
 
-/rihal:plan <phase description>
-/rihal:execute <plan-artifact>
+/rihal-plan <phase description>
+/rihal-execute <plan-artifact>
 ```
 
 If ROADMAP.md missing:

package/rihal/workflows/new-milestone.md

@@ -30,12 +30,12 @@ Read these files in parallel:
 - `.planning/PROJECT.md` — existing project, validated requirements, decisions
 - `.planning/MILESTONES.md` — what shipped previously (may not exist on first milestone)
 - `.planning/STATE.md` — pending todos, blockers
-- `.planning/MILESTONE-CONTEXT.md` — if it exists (from a prior `/rihal:discuss` about the next milestone)
+- `.planning/MILESTONE-CONTEXT.md` — if it exists (from a prior `/rihal-discuss` about the next milestone)
 
 If `.planning/PROJECT.md` does not exist, STOP and redirect:
 
 ```
-⚠ No project initialized. Run /rihal:new-project first.
+⚠ No project initialized. Run /rihal-new-project first.
 ```
 
 ## 2. Gather milestone goals
@@ -132,7 +132,7 @@ This document evolves at phase transitions and milestone boundaries.
 4. Decisions to log? → add to Key Decisions
 5. "What This Is" still accurate? → update if drifted
 
-**After each milestone (via `/rihal:complete-milestone`):**
+**After each milestone (via `/rihal-complete-milestone`):**
 1. Full review of all sections
 2. Core Value check
 3. Audit Out of Scope — reasons still valid?
@@ -182,7 +182,7 @@ Delete `MILESTONE-CONTEXT.md` if it exists (consumed):
 rm -f .planning/MILESTONE-CONTEXT.md
 ```
 
-Clear leftover phase directories from the previous milestone only if the previous milestone was archived (check `.planning/archive/` exists and contains the prior milestone's dir). If not archived, do NOT delete — prompt user to run `/rihal:complete-milestone` on the prior milestone first.
+Clear leftover phase directories from the previous milestone only if the previous milestone was archived (check `.planning/archive/` exists and contains the prior milestone's dir). If not archived, do NOT delete — prompt user to run `/rihal-complete-milestone` on the prior milestone first.
 
 Load commit conventions (see `@.rihal/references/commit-conventions.md` — run the project-local scan before writing the commit message):
 
@@ -236,7 +236,7 @@ fi
 If the previous milestone has not been completed/archived, STOP:
 
 ```
-⚠ Prior milestone not archived. Run /rihal:complete-milestone v[prev] before --reset-phase-numbers.
+⚠ Prior milestone not archived. Run /rihal-complete-milestone v[prev] before --reset-phase-numbers.
 ```
 
 ## 8. Research decision
@@ -253,7 +253,7 @@ If `research_enabled=false`:
 - "Skip research (current default)" — go straight to requirements
 - "Research first" — discover patterns, features, architecture for NEW capabilities
 
-**Do NOT persist this choice.** To change the default, the user runs `/rihal:settings`.
+**Do NOT persist this choice.** To change the default, the user runs `/rihal-settings`.
 
 **If "Research first":**
 
@@ -580,9 +580,9 @@ node ".rihal/bin/rihal-tools.cjs" state add-decision \
 
 `/clear` then:
 
-`/rihal:discuss-phase [N]` — gather context and clarify approach
+`/rihal-discuss-phase [N]` — gather context and clarify approach
 or
-`/rihal:plan [N]` — skip discussion, plan directly
+`/rihal-plan [N]` — skip discussion, plan directly
 ```
 
 </process>
@@ -601,13 +601,13 @@ or
 - [ ] User approval captured before commit
 - [ ] Phase numbering mode respected (continued or reset)
 - [ ] All commits made (or gracefully skipped if .planning/ gitignored)
-- [ ] User shown next command: `/rihal:discuss-phase [N]`
+- [ ] User shown next command: `/rihal-discuss-phase [N]`
 </success_criteria>
 
 <on_error>
 - **Empty `$ARGUMENTS` with no conversational context:** ask for milestone name; do not invent one.
-- **No `.planning/PROJECT.md`:** redirect to `/rihal:new-project`.
-- **Prior milestone not archived + `--reset-phase-numbers`:** stop, tell user to run `/rihal:complete-milestone` first.
+- **No `.planning/PROJECT.md`:** redirect to `/rihal-new-project`.
+- **Prior milestone not archived + `--reset-phase-numbers`:** stop, tell user to run `/rihal-complete-milestone` first.
 - **Roadmapper returns ROADMAP BLOCKED:** surface the blocker, collect resolution, re-spawn.
 - **`rihal-tools.cjs state` fails:** continue — state tracking is optional, file artifacts are mandatory.
 - **`.planning/` is gitignored:** write files, print ℹ notice, do not error.

package/rihal/workflows/new-project-research.md

@@ -1,7 +1,7 @@
 # Subworkflow: new-project — Research Phase
 
 <purpose>
-Research phase of /rihal:new-project. Loaded from new-project.md via @-reference when user opts into research. Produces research artifacts that feed into Step 7 (Define Requirements) and Step 8 (Create Roadmap).
+Research phase of /rihal-new-project. Loaded from new-project.md via @-reference when user opts into research. Produces research artifacts that feed into Step 7 (Define Requirements) and Step 8 (Create Roadmap).
 
 **Invariants from parent:** {project_name}, {planning_artifacts}, {researcher_model}, {synthesizer_model}, {user_preference_research}. Set in new-project.md Steps 1–5.5 before this loads.
 </purpose>

package/rihal/workflows/new-project-roadmap.md

@@ -1,7 +1,7 @@
 # Subworkflow: new-project — Requirements & Roadmap
 
 <purpose>
-Requirements + roadmap phase of /rihal:new-project. Loaded from new-project.md via @-reference after setup (and optionally research) complete. Produces PROJECT.md requirements, ROADMAP.md, and the 'Done' signoff.
+Requirements + roadmap phase of /rihal-new-project. Loaded from new-project.md via @-reference after setup (and optionally research) complete. Produces PROJECT.md requirements, ROADMAP.md, and the 'Done' signoff.
 
 **Invariants from parent:** {project_name}, {planning_artifacts}, research artifacts (if any), PROJECT.md skeleton. Set in new-project.md Steps 1–5.5 (and optionally new-project-research.md).
 </purpose>
@@ -339,7 +339,7 @@ Present completion summary:
 ╚══════════════════════════════════════════╝
 ```
 
-Exit skill and invoke SlashCommand("/rihal:discuss-phase 1 --auto")
+Exit skill and invoke SlashCommand("/rihal-discuss-phase 1 --auto")
 
 **If interactive mode:**
 
@@ -359,15 +359,15 @@ PHASE1_HAS_UI=$(echo "$PHASE1_SECTION" | grep -qi "UI hint.*yes" && echo "true"
 
 **Phase 1: [Phase Name]** — [Goal from ROADMAP.md]
 
-/rihal:discuss-phase 1 — gather context and clarify approach
+/rihal-discuss-phase 1 — gather context and clarify approach
 
 <sub>/clear first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- /rihal:ui-phase 1 — generate UI design contract (recommended for frontend phases)
-- /rihal:plan-phase 1 — skip discussion, plan directly
+- /rihal-ui-phase 1 — generate UI design contract (recommended for frontend phases)
+- /rihal-plan-phase 1 — skip discussion, plan directly
 
 ───────────────────────────────────────────────────────────────
 ```
@@ -381,14 +381,14 @@ PHASE1_HAS_UI=$(echo "$PHASE1_SECTION" | grep -qi "UI hint.*yes" && echo "true"
 
 **Phase 1: [Phase Name]** — [Goal from ROADMAP.md]
 
-/rihal:discuss-phase 1 — gather context and clarify approach
+/rihal-discuss-phase 1 — gather context and clarify approach
 
 <sub>/clear first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- /rihal:plan-phase 1 — skip discussion, plan directly
+- /rihal-plan-phase 1 — skip discussion, plan directly
 
 ───────────────────────────────────────────────────────────────
 ```
@@ -431,7 +431,7 @@ PHASE1_HAS_UI=$(echo "$PHASE1_SECTION" | grep -qi "UI hint.*yes" && echo "true"
 - [ ] STATE.md initialized
 - [ ] REQUIREMENTS.md traceability updated
 - [ ] CLAUDE.md generated with Rihal workflow guidance
-- [ ] User knows next step is `/rihal:discuss-phase 1`
+- [ ] User knows next step is `/rihal-discuss-phase 1`
 
 **Atomic commits:** Each phase commits its artifacts immediately. If context is lost, artifacts persist.
 

package/rihal/workflows/new-project.md

@@ -47,7 +47,7 @@ Existing {stack} code found in {path}. Mapping it first will save
 duplication during planning.
 ```
 
-Then AskUserQuestion to route to /rihal:map-codebase before proceeding.
+Then AskUserQuestion to route to /rihal-map-codebase before proceeding.
 
 **Exiting to map-codebase handoff:**
 ```
@@ -56,9 +56,9 @@ Then AskUserQuestion to route to /rihal:map-codebase before proceeding.
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Per the workflow, mapping runs first. After it finishes I'll re-enter
-/rihal:new-project automatically with the map in hand.
+/rihal-new-project automatically with the map in hand.
 
-Handing off to /rihal:map-codebase now.
+Handing off to /rihal-map-codebase now.
 ```
 </output_format>
 
@@ -68,14 +68,14 @@ Handing off to /rihal:map-codebase now.
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:new-project <argument-here>
+/rihal-new-project <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:new-project employee leave request tracker for an Omani government ministry
-/rihal:new-project car rental marketplace SEO site for Dubai
-/rihal:new-project tasbeeh app with Arabic RTL support for Android
+/rihal-new-project employee leave request tracker for an Omani government ministry
+/rihal-new-project car rental marketplace SEO site for Dubai
+/rihal-new-project tasbeeh app with Arabic RTL support for Android
 ```
 
 STOP — do not proceed.
@@ -100,9 +100,9 @@ If `$EXISTING` is non-empty (project already initialized):
 ```
 ⚠ A rihal project already exists here.
 
-To check current state: /rihal:status
-To find next action: /rihal:next
-To start a fresh phase instead: /rihal:add-phase
+To check current state: /rihal-status
+To find next action: /rihal-next
+To start a fresh phase instead: /rihal-add-phase
 ```
 
 Only proceed past this step if no project exists (`$EXISTING` is empty).
@@ -127,7 +127,7 @@ Check if `--auto` flag is present in $ARGUMENTS.
 **Document requirement:**
 Auto mode requires an idea document — either:
 
-- File reference: `/rihal:new-project --auto @prd.md`
+- File reference: `/rihal-new-project --auto @prd.md`
 - Pasted/written text in the prompt
 
 If no document content provided, error:
@@ -136,8 +136,8 @@ If no document content provided, error:
 Error: --auto requires an idea document.
 
 Usage:
-  /rihal:new-project --auto @your-idea.md
-  /rihal:new-project --auto [paste or write your idea here]
+  /rihal-new-project --auto @your-idea.md
+  /rihal-new-project --auto [paste or write your idea here]
 
 The document should describe what you want to build.
 ```
@@ -186,7 +186,7 @@ if [ "$RUNTIME" = "codex" ]; then INSTRUCTION_FILE="AGENTS.md"; else INSTRUCTION
 
 All subsequent references to the project instruction file use `$INSTRUCTION_FILE`.
 
-**If `project_exists` is true:** Error — project already initialized. Use `/rihal:progress`.
+**If `project_exists` is true:** Error — project already initialized. Use `/rihal-progress`.
 
 **If `has_git` is false:** Initialize git:
 
@@ -216,13 +216,13 @@ Use AskUserQuestion:
 - header: "Codebase"
 - question: "I detected existing code in this directory. Would you like to map the codebase first?"
 - options:
-  - "Map codebase first" — Run /rihal:map-codebase to understand existing architecture (Recommended)
+  - "Map codebase first" — Run /rihal-map-codebase to understand existing architecture (Recommended)
   - "Skip mapping" — Proceed with targeted discovery
 
 **If "Map codebase first":**
 
 ```
-Run `/rihal:map-codebase` first, then return to `/rihal:new-project`
+Run `/rihal-map-codebase` first, then return to `/rihal-new-project`
 ```
 
 Exit command.
@@ -585,14 +585,14 @@ Synthesize all context into `.planning/PROJECT.md`. If `.rihal/templates/project
 
 This document evolves at phase transitions and milestone boundaries.
 
-**After each phase transition** (via `/rihal:discuss-phase` + `/rihal:plan`):
+**After each phase transition** (via `/rihal-discuss-phase` + `/rihal-plan`):
 1. Requirements invalidated? → Move to Out of Scope with reason
 2. Requirements validated? → Move to Validated with phase reference
 3. New requirements emerged? → Add to Active
 4. Decisions to log? → Add to Key Decisions
 5. "What This Is" still accurate? → Update if drifted
 
-**After each milestone** (via `/rihal:complete-milestone`):
+**After each milestone** (via `/rihal-complete-milestone`):
 1. Full review of all sections
 2. Core Value check — still the right priority?
 3. Audit Out of Scope — reasons still valid?
@@ -761,7 +761,7 @@ cat > .planning/config.json <<EOF
 EOF
 ```
 
-**Note:** Run `/rihal:settings` anytime to update model profile, workflow agents, branching strategy, and other preferences.
+**Note:** Run `/rihal-settings` anytime to update model profile, workflow agents, branching strategy, and other preferences.
 
 **If commit_docs = No:**
 
@@ -1342,12 +1342,12 @@ The rihal-tools CLI does not expose a `generate-claude-md` subcommand. Instead,
 This project uses Rihal for planning and execution. See `.planning/PROJECT.md` for context and `.planning/ROADMAP.md` for phases.
 
 Common commands:
-- /rihal:progress — check status and next action
-- /rihal:discuss-phase N — gather context before planning phase N
-- /rihal:plan N — create a SPRINT.md for phase N
-- /rihal:execute N — execute a SPRINT.md
-- /rihal:verify-work — conversational UAT
-- /rihal:complete-milestone — archive milestone and reset
+- /rihal-progress — check status and next action
+- /rihal-discuss-phase N — gather context before planning phase N
+- /rihal-plan N — create a SPRINT.md for phase N
+- /rihal-execute N — execute a SPRINT.md
+- /rihal-verify-work — conversational UAT
+- /rihal-complete-milestone — archive milestone and reset
 
 Rules:
 - Never run `git push` without explicit user authorization.
@@ -1403,7 +1403,7 @@ Present completion summary:
 ╚══════════════════════════════════════════╝
 ```
 
-Exit skill and invoke `/rihal:discuss-phase 1 --auto`.
+Exit skill and invoke `/rihal-discuss-phase 1 --auto`.
 
 **If interactive mode:**
 
@@ -1425,13 +1425,13 @@ PHASE1_HAS_UI=$(echo "$PHASE1_SECTION" | grep -qiE "UI|interface|frontend|compon
 
 /clear then:
 
-/rihal:discuss-phase 1 — gather context and clarify approach
+/rihal-discuss-phase 1 — gather context and clarify approach
 
 ---
 
 **Also available:**
-- /rihal:ui-phase 1 — generate UI design contract (recommended for frontend phases)
-- /rihal:plan 1 — skip discussion, plan directly
+- /rihal-ui-phase 1 — generate UI design contract (recommended for frontend phases)
+- /rihal-plan 1 — skip discussion, plan directly
 
 ───────────────────────────────────────────────────────────────
 ```
@@ -1447,12 +1447,12 @@ PHASE1_HAS_UI=$(echo "$PHASE1_SECTION" | grep -qiE "UI|interface|frontend|compon
 
 /clear then:
 
-/rihal:discuss-phase 1 — gather context and clarify approach
+/rihal-discuss-phase 1 — gather context and clarify approach
 
 ---
 
 **Also available:**
-- /rihal:plan 1 — skip discussion, plan directly
+- /rihal-plan 1 — skip discussion, plan directly
 
 ───────────────────────────────────────────────────────────────
 ```
@@ -1495,7 +1495,7 @@ PHASE1_HAS_UI=$(echo "$PHASE1_SECTION" | grep -qiE "UI|interface|frontend|compon
 - [ ] STATE.md initialized
 - [ ] REQUIREMENTS.md traceability updated
 - [ ] `$INSTRUCTION_FILE` generated (if missing) with rihal workflow guidance
-- [ ] User knows next step is `/rihal:discuss-phase 1`
+- [ ] User knows next step is `/rihal-discuss-phase 1`
 - [ ] No `git push` issued by the workflow (per AGENTS.md)
 
 **Atomic commits:** Each phase commits its artifacts immediately. If context is lost, artifacts persist. When `.planning/` is gitignored, files are written but commit is skipped gracefully.

package/rihal/workflows/new-workspace.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:new-workspace
+# Workflow: rihal-new-workspace
 
 <purpose>
 Create an isolated workspace for parallel work. Workspaces are independent planning directories with their own ROADMAP, STATE, and phases. Use when multiple concurrent initiatives need to run without interfering (e.g., "Q2 Platform Work" + "Bug Fix Sprint" in parallel).
@@ -9,13 +9,13 @@ Create an isolated workspace for parallel work. Workspaces are independent plann
 If `$ARGUMENTS` is empty or only `--help` or `-h`:
 
 ```
-/rihal:new-workspace <workspace-name> [--from-current]
+/rihal-new-workspace <workspace-name> [--from-current]
 ```
 
 **Examples:**
 ```
-/rihal:new-workspace Bug Fix Sprint
-/rihal:new-workspace --from-current Emergency Hotfix
+/rihal-new-workspace Bug Fix Sprint
+/rihal-new-workspace --from-current Emergency Hotfix
 ```
 
 STOP — do not proceed.
@@ -136,10 +136,10 @@ Print:
   Location: {WORKSPACE_DIR}
   
 Start work:
-  /rihal:plan <task> --workspace={WORKSPACE_NAME}
+  /rihal-plan <task> --workspace={WORKSPACE_NAME}
   
 Switch context:
-  /rihal:workspace {WORKSPACE_NAME}
+  /rihal-workspace {WORKSPACE_NAME}
 ```
 
 ## Success Criteria
@@ -156,7 +156,7 @@ If workspace with that name already exists:
 
 ```
 ⚠ Workspace '{WORKSPACE_NAME}' already exists.
-  Use a different name or: /rihal:remove-workspace {WORKSPACE_NAME}
+  Use a different name or: /rihal-remove-workspace {WORKSPACE_NAME}
 ```
 
 If permissions prevent directory creation: