@hanzlaa/rcode 3.2.1 → 3.3.1

package/rihal/workflows/remove-phase.md

@@ -11,15 +11,15 @@ Read all files referenced by the invoking prompt's execution_context before star
 <step name="parse_arguments">
 Parse the command arguments:
 - Argument is the phase number to remove (integer or decimal)
-- Example: `/rihal:remove-phase 17` → phase = 17
-- Example: `/rihal:remove-phase 16.1` → phase = 16.1
+- Example: `/rihal-remove-phase 17` → phase = 17
+- Example: `/rihal-remove-phase 16.1` → phase = 16.1
 
 If no argument provided:
 
 ```
 ERROR: Phase number required
-Usage: /rihal:remove-phase <phase-number>
-Example: /rihal:remove-phase 17
+Usage: /rihal-remove-phase <phase-number>
+Example: /rihal-remove-phase 17
 ```
 
 Exit.
@@ -53,7 +53,7 @@ Only future phases can be removed:
 - Current phase: {current}
 - Phase {target} is current or completed
 
-To abandon current work, use /rihal:pause-work instead.
+To abandon current work, use /rihal-pause-work instead.
 ```
 
 Exit.
@@ -126,7 +126,7 @@ Changes:
 ## What's Next
 
 Would you like to:
-- `/rihal:progress` — see updated roadmap status
+- `/rihal-progress` — see updated roadmap status
 - Continue with current phase
 - Review roadmap
 

package/rihal/workflows/remove-workspace.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:remove-workspace
+# Workflow: rihal-remove-workspace
 
 <purpose>
 Remove a workspace and clean up all its artifacts. This is destructive — deleted workspaces cannot be recovered unless `--archive` flag is used. Use when a parallel work stream is complete or abandoned.
@@ -9,14 +9,14 @@ Remove a workspace and clean up all its artifacts. This is destructive — delet
 If `$ARGUMENTS` is empty or only `--help` or `-h`:
 
 ```
-/rihal:remove-workspace <workspace-name> [--archive] [--force]
+/rihal-remove-workspace <workspace-name> [--archive] [--force]
 ```
 
 **Examples:**
 ```
-/rihal:remove-workspace Bug Fix Sprint
-/rihal:remove-workspace Emergency --force
-/rihal:remove-workspace Old Work --archive
+/rihal-remove-workspace Bug Fix Sprint
+/rihal-remove-workspace Emergency --force
+/rihal-remove-workspace Old Work --archive
 ```
 
 STOP — do not proceed.
@@ -33,7 +33,7 @@ If `$WORKSPACE_NAME` is empty, ask:
 ```
 AskUserQuestion(
   header: "Remove Workspace",
-  question: "Which workspace? (list: /rihal:list-workspaces)"
+  question: "Which workspace? (list: /rihal-list-workspaces)"
 )
 ```
 
@@ -47,7 +47,7 @@ If not found:
 
 ```
 ⚠ Workspace not found: {WORKSPACE_NAME}
-  List workspaces: /rihal:list-workspaces
+  List workspaces: /rihal-list-workspaces
 ```
 
 STOP.
@@ -126,7 +126,7 @@ Print:
   [Archive location: {ARCHIVE_PATH}] (if --archive)
   
 Remaining workspaces: {count}
-List: /rihal:list-workspaces
+List: /rihal-list-workspaces
 ```
 
 ## Success Criteria

package/rihal/workflows/replay.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:replay
+# Workflow: rihal-replay
 
 <purpose>
 Re-run a past council session with the same question for a fresh panel round. Useful when:
@@ -19,7 +19,7 @@ Open with banner:
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
-End with a single-line redirect (per `command-redirect-format.md`) so the user copy-pastes the resulting `/rihal:council` invocation.
+End with a single-line redirect (per `command-redirect-format.md`) so the user copy-pastes the resulting `/rihal-council` invocation.
 </output_format>
 
 <required_reading>
@@ -33,7 +33,7 @@ End with a single-line redirect (per `command-redirect-format.md`) so the user c
 If `$ARGUMENTS` is empty or contains only `--help` / `-h`:
 
 ```
-/rihal:replay <session-path-or-slug> [--agents a,b,c]
+/rihal-replay <session-path-or-slug> [--agents a,b,c]
 
   <session-path-or-slug>   Full path to .planning/council-sessions/council-YYYY-MM-DD-<slug>.md
                            OR just the slug (e.g. "should-i-ship-v2") — the first matching
@@ -69,7 +69,7 @@ fi
 If no sessions directory exists at all:
 
 ```
-No council sessions on disk yet. Run /rihal:council "<question>" to create the first one.
+No council sessions on disk yet. Run /rihal-council "<question>" to create the first one.
 ```
 
 STOP.
@@ -87,7 +87,7 @@ If the extracted question is empty:
 ```
 Could not extract "## Question" heading from $SESSION_FILE. The artifact may be malformed. Open it and copy the question manually:
 
-/rihal:council <question>
+/rihal-council <question>
 ```
 
 STOP.
@@ -126,7 +126,7 @@ Re-running the council with a fresh panel on the original question.
 
 Copy-paste this:
 
-/rihal:council {QUESTION}{agents_suffix}
+/rihal-council {QUESTION}{agents_suffix}
 ```
 
 Where `{agents_suffix}` is `  --agents=a,b,c` if `--agents` was passed, else empty.
@@ -141,7 +141,7 @@ node .rihal/bin/rihal-tools.cjs state add-decision \
   2>/dev/null || true
 ```
 
-The subsequent `/rihal:council` run will attach its own artifact; pairing the two by date + slug lets `/rihal:decisions` and state readers show the replay chain.
+The subsequent `/rihal-council` run will attach its own artifact; pairing the two by date + slug lets `/rihal-decisions` and state readers show the replay chain.
 </process>
 
 ## Success Criteria
@@ -155,6 +155,6 @@ The subsequent `/rihal:council` run will attach its own artifact; pairing the tw
 
 ## On Error
 
-- Missing session directory → tell the user to run `/rihal:council` first
+- Missing session directory → tell the user to run `/rihal-council` first
 - Slug ambiguity → list the top 10 newest matches so the user can paste a fuller path
 - Extraction returns empty → print the path and ask the user to copy the question manually

package/rihal/workflows/rerun.md

@@ -4,13 +4,13 @@ Re-execute a previously completed phase or plan. Resets its state to pending and
 
 ## Step 0: Usage Check
 
-Verify argument: `/rihal:rerun <phase-id|plan-id>`
+Verify argument: `/rihal-rerun <phase-id|plan-id>`
 
 Examples:
-- `/rihal:rerun 03` — re-run all plans in phase 3
-- `/rihal:rerun 03-02` — re-run specific plan
+- `/rihal-rerun 03` — re-run all plans in phase 3
+- `/rihal-rerun 03-02` — re-run specific plan
 
-If empty: `Usage: /rihal:rerun <phase-id|plan-id> (e.g., /rihal:rerun 03 or /rihal:rerun 03-02)`
+If empty: `Usage: /rihal-rerun <phase-id|plan-id> (e.g., /rihal-rerun 03 or /rihal-rerun 03-02)`
 
 ## Step 0.5: Detect Target via Resolve
 
@@ -55,7 +55,7 @@ Write updated state.json back
 
 ## Step 3: Invoke Execute
 
-Route to `/rihal:execute-phase {target.id}`
+Route to `/rihal-execute-phase {target.id}`
 
 The executor will:
 - See status=pending in state.json

package/rihal/workflows/research-phase.md

@@ -1,7 +1,7 @@
 <purpose>
 Research how to implement a phase. Spawns rihal-phase-researcher with phase context.
 
-Standalone research command. For most workflows, use `/rihal:plan` which integrates research automatically.
+Standalone research command. For most workflows, use `/rihal-plan` which integrates research automatically.
 </purpose>
 
 <available_agent_types>
@@ -54,7 +54,7 @@ Research implementation approach for Phase {phase}: {name}
 </objective>
 
 <files_to_read>
-- {context_path} (USER DECISIONS from /rihal:discuss-phase)
+- {context_path} (USER DECISIONS from /rihal-discuss-phase)
 - {requirements_path} (Project requirements)
 - {state_path} (Project decisions and history)
 </files_to_read>

package/rihal/workflows/resume-work.md

@@ -28,7 +28,7 @@ Parse JSON for: `state_exists`, `roadmap_exists`, `project_exists`, `planning_ex
 
 **If `state_exists` is true:** Proceed to load_state
 **If `state_exists` is false but `roadmap_exists` or `project_exists` is true:** Offer to reconstruct STATE.md
-**If `planning_exists` is false:** This is a new project - route to /rihal:new-project
+**If `planning_exists` is false:** This is a new project - route to /rihal-new-project
 </step>
 
 <step name="load_state">
@@ -84,7 +84,7 @@ fi
 
 **If HANDOFF.json exists:**
 
-- This is the primary resumption source — structured data from `/rihal:pause-work`
+- This is the primary resumption source — structured data from `/rihal-pause-work`
 - Parse `status`, `phase`, `plan`, `task`, `total_tasks`, `next_action`
 - Check `blockers` and `human_actions_pending` — surface these immediately
 - Check `completed_tasks` for `in_progress` items — these need attention first
@@ -140,7 +140,7 @@ Present complete project status to user:
     Resume with: Task tool (resume parameter with agent ID)
 
 [If pending todos exist:]
-📋 [N] pending todos — /rihal:check-todos to review
+📋 [N] pending todos — /rihal-check-todos to review
 
 [If blockers exist:]
 ⚠️  Carried concerns:
@@ -200,11 +200,11 @@ What would you like to do?
 [Primary action based on state - e.g.:]
 1. Resume interrupted agent [if interrupted agent found]
    OR
-1. Execute phase (/rihal:execute-phase {phase} ${Rihal_WS})
+1. Execute phase (/rihal-execute-phase {phase} ${Rihal_WS})
    OR
-1. Discuss Phase 3 context (/rihal:discuss-phase 3 ${Rihal_WS}) [if CONTEXT.md missing]
+1. Discuss Phase 3 context (/rihal-discuss-phase 3 ${Rihal_WS}) [if CONTEXT.md missing]
    OR
-1. Plan Phase 3 (/rihal:plan 3 ${Rihal_WS}) [if CONTEXT.md exists or discuss option declined]
+1. Plan Phase 3 (/rihal-plan 3 ${Rihal_WS}) [if CONTEXT.md exists or discuss option declined]
 
 [Secondary options:]
 2. Review current phase status
@@ -237,7 +237,7 @@ Based on user selection, route to appropriate workflow:
 
   `/clear` then:
 
-  `/rihal:execute-phase {phase} ${Rihal_WS}`
+  `/rihal-execute-phase {phase} ${Rihal_WS}`
 
   ---
   ```
@@ -251,13 +251,13 @@ Based on user selection, route to appropriate workflow:
 
   `/clear` then:
 
-  `/rihal:plan [phase-number] ${Rihal_WS}`
+  `/rihal-plan [phase-number] ${Rihal_WS}`
 
   ---
 
   **Also available:**
-  - `/rihal:discuss-phase [N] ${Rihal_WS}` — gather context first
-  - `/rihal:research-phase [N] ${Rihal_WS}` — investigate unknowns
+  - `/rihal-discuss-phase [N] ${Rihal_WS}` — gather context first
+  - `/rihal-research-phase [N] ${Rihal_WS}` — investigate unknowns
 
   ---
   ```

package/rihal/workflows/review-adversarial.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:review-adversarial
+# Workflow: rihal-review-adversarial
 
 <purpose>
 Assume an adversarial/hostile perspective and audit code for weaknesses: SQL injection, XSS, race conditions, data loss scenarios, unauthorized access, abuse cases, denial of service vectors. Output attack/weakness report that feeds into story AC or subtasks.
@@ -10,13 +10,13 @@ Assume an adversarial/hostile perspective and audit code for weaknesses: SQL inj
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:review-adversarial <argument-here>
+/rihal-review-adversarial <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:review-adversarial example 1
-/rihal:review-adversarial example 2
+/rihal-review-adversarial example 1
+/rihal-review-adversarial example 2
 ```
 
 STOP — do not proceed.

package/rihal/workflows/review-edge-case-hunter.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:review-edge-case-hunter
+# Workflow: rihal-review-edge-case-hunter
 
 <purpose>
 Systematically enumerate edge cases by category (input, state, concurrency, network) with severity (critical/high/medium/low). Callable during code-review.md workflow. Output feeds into story AC or subtasks. Focuses on "what breaks?" rather than security.
@@ -10,13 +10,13 @@ Systematically enumerate edge cases by category (input, state, concurrency, netw
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:review-edge-case-hunter <argument-here>
+/rihal-review-edge-case-hunter <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:review-edge-case-hunter example 1
-/rihal:review-edge-case-hunter example 2
+/rihal-review-edge-case-hunter example 1
+/rihal-review-edge-case-hunter example 2
 ```
 
 STOP — do not proceed.
@@ -196,7 +196,7 @@ AskUserQuestion([
 
 If "Yes, find edge cases":
 ```
-/rihal:review-edge-case-hunter --phase {current_phase}
+/rihal-review-edge-case-hunter --phase {current_phase}
 ```
 
 ## Success Criteria

package/rihal/workflows/review.md

@@ -39,7 +39,7 @@ No external AI CLIs found. Install at least one:
 - claude: https://github.com/anthropics/claude-code
 - opencode: https://opencode.ai (leverages GitHub Copilot subscription models)
 
-Then run /rihal:review again.
+Then run /rihal-review again.
 ```
 Exit.
 
@@ -135,7 +135,7 @@ Focus on:
 Output your review in markdown format.
 ```
 
-Write to a temp file: `/tmp/rihal:review-prompt-{phase}.md`
+Write to a temp file: `/tmp/rihal-review-prompt-{phase}.md`
 </step>
 
 <step name="invoke_reviewers">
@@ -143,17 +143,17 @@ For each selected CLI, invoke in sequence (not parallel — avoid rate limits):
 
 **Gemini:**
 ```bash
-gemini -p "$(cat /tmp/rihal:review-prompt-{phase}.md)" 2>/dev/null > /tmp/rihal:review-gemini-{phase}.md
+gemini -p "$(cat /tmp/rihal-review-prompt-{phase}.md)" 2>/dev/null > /tmp/rihal-review-gemini-{phase}.md
 ```
 
 **Claude (separate session):**
 ```bash
-claude -p "$(cat /tmp/rihal:review-prompt-{phase}.md)" 2>/dev/null > /tmp/rihal:review-claude-{phase}.md
+claude -p "$(cat /tmp/rihal-review-prompt-{phase}.md)" 2>/dev/null > /tmp/rihal-review-claude-{phase}.md
 ```
 
 **Codex:**
 ```bash
-codex exec --skip-git-repo-check "$(cat /tmp/rihal:review-prompt-{phase}.md)" 2>/dev/null > /tmp/rihal:review-codex-{phase}.md
+codex exec --skip-git-repo-check "$(cat /tmp/rihal-review-prompt-{phase}.md)" 2>/dev/null > /tmp/rihal-review-codex-{phase}.md
 ```
 
 **CodeRabbit:**
@@ -161,14 +161,14 @@ codex exec --skip-git-repo-check "$(cat /tmp/rihal:review-prompt-{phase}.md)" 2>
 Note: CodeRabbit reviews the current git diff/working tree — it does not accept a prompt. It may take up to 5 minutes. Use `timeout: 360000` on the Bash tool call.
 
 ```bash
-coderabbit review --prompt-only 2>/dev/null > /tmp/rihal:review-coderabbit-{phase}.md
+coderabbit review --prompt-only 2>/dev/null > /tmp/rihal-review-coderabbit-{phase}.md
 ```
 
 **OpenCode (via GitHub Copilot):**
 ```bash
-cat /tmp/rihal:review-prompt-{phase}.md | opencode run - 2>/dev/null > /tmp/rihal:review-opencode-{phase}.md
-if [ ! -s /tmp/rihal:review-opencode-{phase}.md ]; then
-  echo "OpenCode review failed or returned empty output." > /tmp/rihal:review-opencode-{phase}.md
+cat /tmp/rihal-review-prompt-{phase}.md | opencode run - 2>/dev/null > /tmp/rihal-review-opencode-{phase}.md
+if [ ! -s /tmp/rihal-review-opencode-{phase}.md ]; then
+  echo "OpenCode review failed or returned empty output." > /tmp/rihal-review-opencode-{phase}.md
 fi
 ```
 
@@ -264,7 +264,7 @@ Consensus concerns:
 Full review: {padded_phase}-REVIEWS.md
 
 To incorporate feedback into planning:
-  /rihal:plan {N} --reviews
+  /rihal-plan {N} --reviews
 ```
 
 Clean up temp files.
@@ -277,5 +277,5 @@ Clean up temp files.
 - [ ] REVIEWS.md written with structured feedback
 - [ ] Consensus summary synthesized from multiple reviewers
 - [ ] Temp files cleaned up
-- [ ] User knows how to use feedback (/rihal:plan --reviews)
+- [ ] User knows how to use feedback (/rihal-plan --reviews)
 </success_criteria>

package/rihal/workflows/scan.md

@@ -20,16 +20,16 @@ If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 **Usage:**
 ```
-/rihal:scan [--focus tech|arch|quality|concerns|tech+arch] [--refresh] [--reset]
+/rihal-scan [--focus tech|arch|quality|concerns|tech+arch] [--refresh] [--reset]
 ```
 
 **Examples:**
 ```
-/rihal:scan --focus tech
-/rihal:scan --focus arch
-/rihal:scan --focus tech+arch
-/rihal:scan --refresh                 # auto-update stale docs, brief diff, log to CHANGELOG.md
-/rihal:scan --reset --focus tech+arch # silent overwrite (CI / autonomous)
+/rihal-scan --focus tech
+/rihal-scan --focus arch
+/rihal-scan --focus tech+arch
+/rihal-scan --refresh                 # auto-update stale docs, brief diff, log to CHANGELOG.md
+/rihal-scan --reset --focus tech+arch # silent overwrite (CI / autonomous)
 ```
 
 **Refresh flag — memory-bank pattern.** When `--refresh` is passed AND existing docs are present, the orchestrator:
@@ -327,21 +327,21 @@ Insert at the TOP of the file body (newest-first), under any pre-existing `# Cha
 ```markdown
 # Changelog — Codebase Memory Bank
 
-This file tracks structural changes between scans. Each entry is auto-written by `/rihal:scan --refresh`. Newest entries first.
+This file tracks structural changes between scans. Each entry is auto-written by `/rihal-scan --refresh`. Newest entries first.
 
 ---
 
 {first entry here}
 ```
 
-This file is **read by future `/rihal:scan --refresh` runs** as additional anchor context — the memory bank is self-improving across scans.
+This file is **read by future `/rihal-scan --refresh` runs** as additional anchor context — the memory bank is self-improving across scans.
 
 ## Step 7: Final cue (orchestrator-level, after RETURNED banner)
 
 The RETURNED banner above is Dalil's voice. After it, the orchestrator may add ONE neutral cue line if the user might want a deeper scan:
 
 ```
-Tip: `/rihal:map-codebase` runs a 4-area parallel scan if you want broader coverage.
+Tip: `/rihal-map-codebase` runs a 4-area parallel scan if you want broader coverage.
 ```
 
 Skip this cue if the user already asked for a focused scan — don't push an upsell.

package/rihal/workflows/secure-phase.md

@@ -19,13 +19,13 @@ If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 **Usage:**
 ```
-/rihal:secure-phase <phase>
+/rihal-secure-phase <phase>
 ```
 
 **Examples:**
 ```
-/rihal:secure-phase 01
-/rihal:secure-phase 02.1
+/rihal-secure-phase 01
+/rihal-secure-phase 02.1
 ```
 
 <process>
@@ -45,7 +45,7 @@ AUDITOR_MODEL=$(node ".rihal/bin/rihal-tools.cjs" resolve-model rihal-security-a
 SECURITY_CFG=$(node ".rihal/bin/rihal-tools.cjs" config-get workflow.security_enforcement --raw 2>/dev/null || echo "true")
 ```
 
-If `SECURITY_CFG` is `false`: exit with "Security enforcement disabled. Enable via /rihal:settings."
+If `SECURITY_CFG` is `false`: exit with "Security enforcement disabled. Enable via /rihal-settings."
 
 Display banner: `Rihal > SECURE PHASE {N}: {name}`
 
@@ -59,7 +59,7 @@ SUMMARY_FILES=$(ls "${PHASE_DIR}"/*-SUMMARY.md 2>/dev/null)
 
 - **State A** (`SECURITY_FILE` non-empty): Audit existing
 - **State B** (`SECURITY_FILE` empty, `PLAN_FILES` and `SUMMARY_FILES` non-empty): Run from artifacts
-- **State C** (`SUMMARY_FILES` empty): Exit — "Phase {N} not executed. Run /rihal:execute {N} first."
+- **State C** (`SUMMARY_FILES` empty): Exit — "Phase {N} not executed. Run /rihal-execute {N} first."
 
 ## 2. Discovery
 
@@ -140,7 +140,7 @@ Handle return:
 ```
 Rihal > PHASE {N} SECURITY BLOCKED
 {K} threats open — phase advancement blocked until threats_open: 0
-▶ Fix mitigations then re-run: /rihal:secure-phase {N}
+▶ Fix mitigations then re-run: /rihal-secure-phase {N}
 ▶ Or document accepted risks in SECURITY.md and re-run.
 ```
 
@@ -158,8 +158,8 @@ node ".rihal/bin/rihal-tools.cjs" commit "docs(phase-${PHASE}): add/update secur
 ```
 Rihal > PHASE {N} THREAT-SECURE
 threats_open: 0 — all threats have dispositions.
-▶ /rihal:validate {N}    validate test coverage
-▶ /rihal:verify-work {N}       run UAT
+▶ /rihal-validate {N}    validate test coverage
+▶ /rihal-verify-work {N}       run UAT
 ```
 
 Display `/clear` reminder.

package/rihal/workflows/session-report.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:session-report
+# Workflow: rihal-session-report
 
 <purpose>
 Generate a comprehensive session report covering work done, token usage estimation, commits, decisions, blockers, and council sessions. Writes SESSION-REPORT-{date}.md to .planning/ directory.
@@ -10,13 +10,13 @@ Generate a comprehensive session report covering work done, token usage estimati
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:session-report <argument-here>
+/rihal-session-report <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:session-report example 1
-/rihal:session-report example 2
+/rihal-session-report example 1
+/rihal-session-report example 2
 ```
 
 STOP — do not proceed.
@@ -32,7 +32,7 @@ test -f .rihal/state.json && echo "exists" || echo "missing"
 If missing, print and stop:
 
 ```
-No state found. Run /rihal:council or execute a plan to initialize state.
+No state found. Run /rihal-council or execute a plan to initialize state.
 ```
 
 ## Step 2 — Read state
@@ -153,7 +153,7 @@ Write `.planning/SESSION-REPORT-{YYYY-MM-DD-HHmmss}.md` with this structure:
 ## Next Steps
 
 - Address {count} open blocker(s) before proceeding
-- Plan next phase with `/rihal:plan-phase {next_phase}`
+- Plan next phase with `/rihal-plan-phase {next_phase}`
 ```
 
 ## Step 8 — Print confirmation

package/rihal/workflows/settings.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:settings
+# Workflow: rihal-settings
 
 <purpose>
 View and edit Rihal project settings stored in `.rihal/config.yaml`. Closes
@@ -16,18 +16,18 @@ wizard writes are settings that workflows actually honour.
 If `$ARGUMENTS` contains `--help` or `-h`:
 
 ```
-/rihal:settings              # show current + interactive edit
-/rihal:settings show         # show current only
-/rihal:settings get <key>    # read a single dotted key (e.g. workflow.discuss_mode)
-/rihal:settings set <key> <value>   # write a single dotted key
+/rihal-settings              # show current + interactive edit
+/rihal-settings show         # show current only
+/rihal-settings get <key>    # read a single dotted key (e.g. workflow.discuss_mode)
+/rihal-settings set <key> <value>   # write a single dotted key
 ```
 
 **Examples:**
 ```
-/rihal:settings show
-/rihal:settings get workflow.research_by_default
-/rihal:settings set workflow.research_by_default true
-/rihal:settings set git.branching_strategy feature-branch
+/rihal-settings show
+/rihal-settings get workflow.research_by_default
+/rihal-settings set workflow.research_by_default true
+/rihal-settings set git.branching_strategy feature-branch
 ```
 
 ## Step 1 — Resolve mode
@@ -88,7 +88,7 @@ Current Rihal Settings (.rihal/config.yaml)
     git.commit_docs                 : {value}    # true | false
 ```
 
-If invoked as `/rihal:settings show`, STOP here.
+If invoked as `/rihal-settings show`, STOP here.
 
 ## Step 1.7 — `get <key>`
 
@@ -165,20 +165,20 @@ Print:
 ```
 ✓ Settings saved to .rihal/config.yaml
 
-Tip: settings take effect on the next workflow run. Use /rihal:settings show
-to verify, or /rihal:resume-work to reload context.
+Tip: settings take effect on the next workflow run. Use /rihal-settings show
+to verify, or /rihal-resume-work to reload context.
 ```
 
 ## Success Criteria
 
-- [ ] `/rihal:settings show` prints all 11 keys (no `(unset)` for keys with defaults)
-- [ ] `/rihal:settings set workflow.discuss_mode discuss` round-trips: `config-get` returns `discuss`
+- [ ] `/rihal-settings show` prints all 11 keys (no `(unset)` for keys with defaults)
+- [ ] `/rihal-settings set workflow.discuss_mode discuss` round-trips: `config-get` returns `discuss`
 - [ ] After any save, sibling keys in `workflow:` and `git:` blocks are preserved (no nesting corruption)
 - [ ] Unknown keys are rejected with the allowed-keys table
 
 ## On Error
 
-- **`.rihal/config.yaml` missing:** print "No config found. Run /rihal:init first." and STOP.
+- **`.rihal/config.yaml` missing:** print "No config found. Run /rihal-init first." and STOP.
 - **Invalid key:** print the allowed keys from Step 1.5 and STOP.
 - **Invalid value:** print the allowed values for that key and STOP.
 - **`rihal-tools.cjs` missing:** print "Run: npx @hanzlaa/rcode install ." and STOP.

package/rihal/workflows/ship.md

@@ -12,8 +12,8 @@ the plan → execute → verify → **ship** loop.
 6. Updates STATE.md with shipping status
 
 **Preconditions (all must be true before running):**
-- `/rihal:execute <phase>` completed
-- `/rihal:verify-phase <phase>` passed (VERIFICATION.md exists with `status: passed`)
+- `/rihal-execute <phase>` completed
+- `/rihal-verify-phase <phase>` passed (VERIFICATION.md exists with `status: passed`)
 - You are on a feature branch (not main/develop directly)
 - `gh` CLI is authenticated (`gh auth status`)
 
@@ -25,10 +25,10 @@ the plan → execute → verify → **ship** loop.
 
 **Typical usage:**
 ```
-/rihal:plan 1          → plan the phase
-/rihal:execute 1       → build it
-/rihal:verify-phase 1  → prove it works
-/rihal:ship 1          → PR it ← you are here
+/rihal-plan 1          → plan the phase
+/rihal-execute 1       → build it
+/rihal-verify-phase 1  → prove it works
+/rihal-ship 1          → PR it ← you are here
 ```
 </purpose>
 
@@ -241,8 +241,8 @@ Requirements: {N} REQ-IDs addressed
 Next steps:
 - Review/approve PR
 - Merge when CI passes
-- /rihal:complete-milestone (if last phase in milestone)
-- /rihal:progress (to see what's next)
+- /rihal-complete-milestone (if last phase in milestone)
+- /rihal-progress (to see what's next)
 
 ───────────────────────────────────────────────────────────────
 ```
@@ -253,9 +253,9 @@ Next steps:
 <offer_next>
 After shipping:
 
-- /rihal:complete-milestone — if all phases in milestone are done
-- /rihal:progress — see overall project state
-- /rihal:execute-phase {next} — continue to next phase
+- /rihal-complete-milestone — if all phases in milestone are done
+- /rihal-progress — see overall project state
+- /rihal-execute-phase {next} — continue to next phase
 </offer_next>
 
 <success_criteria>