@hanzlaa/rcode 3.3.0 → 3.3.1

package/rihal/workflows/next.md

@@ -20,7 +20,7 @@ Print a routing banner when dispatching to the next command:
 Current: Phase {N} — {name} | Sprint {sprint_id}
 Status:  {status description}
 
-▶ Next: `/rihal:{command} {args}`
+▶ Next: `/rihal-{command} {args}`
   {One-line explanation}
 ```
 
@@ -50,7 +50,7 @@ Extract from state JSON:
 
 If no `.planning/` directory AND no `.rihal/state.json`:
 ```
-No Rihal project detected. Run `/rihal:new-project` to get started.
+No Rihal project detected. Run `/rihal-new-project` to get started.
 ```
 Exit.
 </step>
@@ -82,7 +82,7 @@ If found:
 ```
 Stop: Project in error state
 
-Resolve the error before advancing. Run `/rihal:health` to diagnose.
+Resolve the error before advancing. Run `/rihal-health` to diagnose.
 Use `--force` to bypass.
 ```
 Exit.
@@ -104,35 +104,35 @@ Apply routing rules based on state:
 
 **Route 1: No phases exist yet**
 ROADMAP.md exists but no phase directories on disk:
-Next: `/rihal:sprint-planning`
+Next: `/rihal-sprint-planning`
 
 **Route 2: Phase exists but no sprint**
 Current phase directory exists but has no SPRINT.md:
-Next: `/rihal:sprint-planning --phase {current_phase}`
+Next: `/rihal-sprint-planning --phase {current_phase}`
 
 **Route 3: Sprint exists, stories incomplete**
 SPRINT.md exists and has stories with status != done:
-Next: `/rihal:execute .planning/phases/{phase_dir}/SPRINT.md`
+Next: `/rihal-execute .planning/phases/{phase_dir}/SPRINT.md`
 
 **Route 4: All stories done, sprint not closed**
 All stories are done but sprint status is still "active":
-Next: complete the sprint via `rihal-tools.cjs state sprint complete`, then suggest `/rihal:sprint-planning` for next sprint
+Next: complete the sprint via `rihal-tools.cjs state sprint complete`, then suggest `/rihal-sprint-planning` for next sprint
 
 **Route 5: Sprint complete, next phase exists**
 Current phase is complete, next phase exists in ROADMAP:
-Next: `/rihal:sprint-planning --phase {next_phase}`
+Next: `/rihal-sprint-planning --phase {next_phase}`
 
 **Route 6: All phases complete**
 All phases in ROADMAP are complete:
-Next: `/rihal:complete-milestone`
+Next: `/rihal-complete-milestone`
 
 **Route 7: Paused**
 State shows paused_at is set:
-Next: `/rihal:resume-work`
+Next: `/rihal-resume-work`
 
 **Route 8: No sprint system, fallback**
 State has no sprints[] data — legacy or empty project:
-Next: `/rihal:sprint-planning`
+Next: `/rihal-sprint-planning`
 </step>
 
 <step name="show_and_execute">
@@ -144,12 +144,12 @@ Display the determination:
 **Current:** Phase {N} — {name} | Sprint {sprint_id}
 **Sprint:** {done}/{total} stories ({points_done}/{points_total} pts)
 
-Next: `/rihal:{command} {args}`
+Next: `/rihal-{command} {args}`
   {One-line explanation}
 ```
 
 Then immediately invoke the determined command.
-Do not ask for confirmation — `/rihal:next` is zero-friction advancement.
+Do not ask for confirmation — `/rihal-next` is zero-friction advancement.
 </step>
 
 </process>

package/rihal/workflows/note.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:note
+# Workflow: rihal-note
 
 <purpose>
 Capture inline notes instantly without friction. Appends text to a dated note file with YAML frontmatter. No subagents, no user questions, no bash chains — single Write operation.
@@ -10,13 +10,13 @@ Capture inline notes instantly without friction. Appends text to a dated note fi
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:note <argument-here>
+/rihal-note <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:note example 1
-/rihal:note example 2
+/rihal-note example 1
+/rihal-note example 2
 ```
 
 STOP — do not proceed.
@@ -38,8 +38,8 @@ fi
 
 If `NOTE_TEXT` is empty:
 ```
-❌ Usage: /rihal:note <text>
-   Example: /rihal:note refactor auth module to use async/await
+❌ Usage: /rihal-note <text>
+   Example: /rihal-note refactor auth module to use async/await
    
    Flags:
    --global  Save to ~/.rihal-notes/ instead of .rihal/notes/
@@ -111,7 +111,7 @@ promoted: false
 refactor auth module to use async/await
 ```
 
-## Step 5 — List subcommand: /rihal:note list
+## Step 5 — List subcommand: /rihal-note list
 
 If ARGUMENTS contains `list`:
 

package/rihal/workflows/notify-test.md

@@ -1,7 +1,7 @@
-# Workflow: rihal:notify-test
+# Workflow: rihal-notify-test
 
 <purpose>
-Verify a webhook URL is configured and reachable by posting a "test" message. Use this immediately after adding `slack_webhook_url`, `discord_webhook_url`, or `teams_webhook_url` to `.rihal/config.yaml` so you catch typos and permission errors before relying on notifications from `/rihal:execute`.
+Verify a webhook URL is configured and reachable by posting a "test" message. Use this immediately after adding `slack_webhook_url`, `discord_webhook_url`, or `teams_webhook_url` to `.rihal/config.yaml` so you catch typos and permission errors before relying on notifications from `/rihal-execute`.
 </purpose>
 
 <output_format>
@@ -26,7 +26,7 @@ End with a per-platform result table: sent / skipped / failed.
 If `$ARGUMENTS` contains `--help` / `-h`:
 
 ```
-/rihal:notify-test [--only slack|discord|teams] [--title "<t>"] [--body "<b>"]
+/rihal-notify-test [--only slack|discord|teams] [--title "<t>"] [--body "<b>"]
 
   --only <platform>   Limit the test to one platform
   --title "<t>"       Override test title (default: "Rihal notify test")
@@ -81,7 +81,7 @@ No webhooks configured. Add at least one to .rihal/config.yaml:
   discord_webhook_url: "https://discord.com/api/webhooks/..."
   teams_webhook_url: "https://outlook.office.com/webhook/..."
 
-Then re-run /rihal:notify-test.
+Then re-run /rihal-notify-test.
 ```
 
 If any platform `failed`, echo the failure detail and list common causes:
@@ -95,8 +95,8 @@ If any platform `sent`, print:
 ```
 ✓ Open your channel to confirm the test message appeared.
   Then configure where notifications fire:
-    - /rihal:execute runs post-phase notify automatically
-    - /rihal:council --notify to ping after a council session
+    - /rihal-execute runs post-phase notify automatically
+    - /rihal-council --notify to ping after a council session
 ```
 </process>
 

package/rihal/workflows/pause-work.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:pause-work
+# Workflow: rihal-pause-work
 
 <purpose>
 Capture full project context and blocking constraints before pausing work. Creates `.rihal/HANDOFF.json` (structured machine-readable handoff) and `.rihal/.continue-here.md` (human-readable summary) for seamless context restoration on resume.
@@ -10,13 +10,13 @@ Capture full project context and blocking constraints before pausing work. Creat
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:pause-work <argument-here>
+/rihal-pause-work <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:pause-work example 1
-/rihal:pause-work example 2
+/rihal-pause-work example 1
+/rihal-pause-work example 2
 ```
 
 STOP — do not proceed.
@@ -208,7 +208,7 @@ No uncommitted changes.
 
 To resume work, run:
 \`\`\`bash
-/rihal:resume-work
+/rihal-resume-work
 \`\`\`
 ```
 
@@ -230,7 +230,7 @@ Blocking constraints:
 
 To resume work, run:
 
-/rihal:resume-work
+/rihal-resume-work
 ```
 
 ## Success Criteria

package/rihal/workflows/plan-milestone-gaps.md

@@ -1,5 +1,5 @@
 <purpose>
-Create all phases necessary to close gaps identified by `/rihal:audit-milestone`. Reads MILESTONE-AUDIT.md, groups gaps into logical phases, creates phase entries in ROADMAP.md, and offers to plan each phase. One command creates all fix phases — no manual `/rihal:add-phase` per gap.
+Create all phases necessary to close gaps identified by `/rihal-audit-milestone`. Reads MILESTONE-AUDIT.md, groups gaps into logical phases, creates phase entries in ROADMAP.md, and offers to plan each phase. One command creates all fix phases — no manual `/rihal-add-phase` per gap.
 </purpose>
 
 <required_reading>
@@ -22,7 +22,7 @@ Parse YAML frontmatter to extract structured gaps:
 
 If no audit file exists or has no gaps, error:
 ```
-No audit gaps found. Run `/rihal:audit-milestone` first.
+No audit gaps found. Run `/rihal-audit-milestone` first.
 ```
 
 ## 2. Prioritize Gaps
@@ -165,20 +165,20 @@ node ".rihal/bin/rihal-tools.cjs" commit "docs(roadmap): add gap closure phases
 
 `/clear` then:
 
-`/rihal:plan {N}`
+`/rihal-plan {N}`
 
 ---
 
 **Also available:**
-- `/rihal:execute-phase {N}` — if plans already exist
+- `/rihal-execute-phase {N}` — if plans already exist
 - `cat .planning/ROADMAP.md` — see updated roadmap
 
 ---
 
 **After all gap phases complete:**
 
-`/rihal:audit-milestone` — re-audit to verify gaps closed
-`/rihal:complete-milestone {version}` — archive when audit passes
+`/rihal-audit-milestone` — re-audit to verify gaps closed
+`/rihal-complete-milestone {version}` — archive when audit passes
 ```
 
 </process>
@@ -269,5 +269,5 @@ becomes:
 - [ ] Coverage count updated in REQUIREMENTS.md
 - [ ] Phase directories created
 - [ ] Changes committed (includes REQUIREMENTS.md)
-- [ ] User knows to run `/rihal:plan` next
+- [ ] User knows to run `/rihal-plan` next
 </success_criteria>

package/rihal/workflows/plan.md

@@ -37,7 +37,7 @@ Closure:
  RIHAL ► PLAN READY ✓  ({N} stories, {M} points)
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
-End with Next Up routing to /rihal:execute.
+End with Next Up routing to /rihal-execute.
 </output_format>
 
 <required_reading>
@@ -81,7 +81,7 @@ Parse JSON for: `researcher_model`, `planner_model`, `checker_model`, `research_
 
 **File paths (for <files_to_read> blocks):** `state_path`, `roadmap_path`, `requirements_path`, `context_path`, `research_path`, `verification_path`, `uat_path`, `reviews_path`. These are null if files don't exist.
 
-**If `planning_exists` is false:** Error — run `/rihal:new-project` first.
+**If `planning_exists` is false:** Error — run `/rihal-new-project` first.
 
 ## 2. Parse and Normalize Arguments
 
@@ -111,7 +111,7 @@ mkdir -p ".planning/phases/${padded_phase}-${phase_slug}"
 
 **Existing artifacts from init:** `has_research`, `has_plans`, `plan_count`.
 
-**TASKS.md ingestion (#385 chain).** If the phase directory contains a `TASKS.md` file (typically auto-extracted by `/rihal:add-phase` from a bulk `/rihal:quick` or `/rihal:do` route), read it now:
+**TASKS.md ingestion (#385 chain).** If the phase directory contains a `TASKS.md` file (typically auto-extracted by `/rihal-add-phase` from a bulk `/rihal-quick` or `/rihal-do` route), read it now:
 
 ```bash
 TASKS_FILE=".planning/phases/${padded_phase}-${phase_slug}/TASKS.md"
@@ -121,7 +121,7 @@ HAS_TASKS=$([ -f "$TASKS_FILE" ] && echo true || echo false)
 When `HAS_TASKS=true`:
 - Pass the TASKS.md content to the planner agent as authoritative phase scope. The planner uses it as the input list — each entry becomes a candidate sprint task in SPRINT.md.
 - Surface this in the opening banner: *"Phase scope source: TASKS.md ({N} entries auto-extracted from bulk route on {date})"*.
-- Do NOT re-prompt the user for scope when TASKS.md is present — they already provided the list once at the /rihal:quick or /rihal:do entry point. The whole point of the auto-route chain is that the user doesn't paste the same content multiple times.
+- Do NOT re-prompt the user for scope when TASKS.md is present — they already provided the list once at the /rihal-quick or /rihal-do entry point. The whole point of the auto-route chain is that the user doesn't paste the same content multiple times.
 
 ## 2.5. Validate `--reviews` Prerequisite
 
@@ -135,9 +135,9 @@ Error:
 ```
 No REVIEWS.md found for Phase {N}. Run reviews first:
 
-/rihal:review --phase {N}
+/rihal-review --phase {N}
 
-Then re-run /rihal:sprint-plan {N} --reviews
+Then re-run /rihal-sprint-plan {N} --reviews
 ```
 Exit workflow.
 
@@ -276,7 +276,7 @@ VERIFICATION_FILE=$(ls "${PHASE_DIR}"/*-VERIFICATION.md 2>/dev/null | head -1)
 Error: No VERIFICATION.md found for Phase {X}. Gap-closure planning requires the phase to have run through the verifier first.
 
 Try:
-  /rihal:execute {X} ${Rihal_WS}      # run or re-run execution + verification
+  /rihal-execute {X} ${Rihal_WS}      # run or re-run execution + verification
 ```
 Exit workflow.
 
@@ -384,9 +384,9 @@ If "Run discuss-phase first":
   does not work correctly in nested subcontexts (#1009). Instead, display the command
   and exit so the user runs it as a top-level command:
   ```
-  Run this command first, then re-run /rihal:sprint-plan {X} ${Rihal_WS}:
+  Run this command first, then re-run /rihal-sprint-plan {X} ${Rihal_WS}:
 
-  /rihal:discuss-phase {X} ${Rihal_WS}
+  /rihal-discuss-phase {X} ${Rihal_WS}
   ```
   **Exit the sprint-plan workflow. Do not continue.**
 
@@ -454,7 +454,7 @@ Answer: "What do I need to know to PLAN this phase well?"
 </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>
@@ -598,7 +598,7 @@ If `TEXT_MODE` is true, present as a plain-text numbered list:
 ```
 Phase {N} has frontend indicators but no UI-SPEC.md. Generate a design contract before planning?
 
-1. Generate UI-SPEC first — Run /rihal:ui-phase {N} then re-run /rihal:sprint-plan {N}
+1. Generate UI-SPEC first — Run /rihal-ui-phase {N} then re-run /rihal-sprint-plan {N}
 2. Continue without UI-SPEC
 3. Not a frontend phase
 
@@ -609,7 +609,7 @@ Otherwise use AskUserQuestion:
 - header: "UI Design Contract"
 - question: "Phase {N} has frontend indicators but no UI-SPEC.md. Generate a design contract before planning?"
 - options:
-  - "Generate UI-SPEC first" → Display: "Run `/rihal:ui-phase {N} ${Rihal_WS}` then re-run `/rihal:sprint-plan {N} ${Rihal_WS}`". Exit workflow.
+  - "Generate UI-SPEC first" → Display: "Run `/rihal-ui-phase {N} ${Rihal_WS}` then re-run `/rihal-sprint-plan {N} ${Rihal_WS}`". Exit workflow.
   - "Continue without UI-SPEC" → Continue to step 6.
   - "Not a frontend phase" → Continue to step 6.
 
@@ -719,7 +719,7 @@ VALIDATION_EXISTS=$(ls "${PHASE_DIR}"/*-VALIDATION.md 2>/dev/null | head -1)
 ```
 
 If missing and Nyquist is still enabled/applicable — ask user:
-1. Re-run: `/rihal:sprint-plan {PHASE} --research ${Rihal_WS}`
+1. Re-run: `/rihal-sprint-plan {PHASE} --research ${Rihal_WS}`
 2. Disable Nyquist with the exact command:
    `node ".rihal/bin/rihal-tools.cjs" config-set workflow.nyquist_validation false`
 3. Continue anyway (plans fail Dimension 8)
@@ -798,7 +798,7 @@ Planner prompt:
 - {state_path} (Project State)
 - {roadmap_path} (Roadmap)
 - {requirements_path} (Requirements)
-- {context_path} (USER DECISIONS from /rihal:discuss-phase)
+- {context_path} (USER DECISIONS from /rihal-discuss-phase)
 - {research_path} (Technical Research)
 - {verification_path} (Verification Gaps - if --gaps)
 - {uat_path} (UAT Gaps - if --gaps)
@@ -821,7 +821,7 @@ ${AGENT_SKILLS_PLANNER}
 </planning_context>
 
 <downstream_consumer>
-Output consumed by /rihal:execute-phase. Plans need:
+Output consumed by /rihal-execute-phase. Plans need:
 - Frontmatter (wave, depends_on, files_modified, autonomous)
 - Tasks in XML format with read_first and acceptance_criteria fields (MANDATORY on every task)
 - Verification criteria
@@ -914,7 +914,7 @@ rest become a follow-up phase
 
 Use AskUserQuestion with these 3 options.
 
-**If "Split":** Use `/rihal:insert-phase` to create the sub-phases, then replan each.
+**If "Split":** Use `/rihal-insert-phase` to create the sub-phases, then replan each.
 **If "Proceed":** Return to planner with instruction to attempt all decisions at full fidelity, accepting more plans/tasks.
 **If "Prioritize":** Use AskUserQuestion (multiSelect) to let user pick which D-XX are "now" vs "later". Create CONTEXT.md for each sub-phase with the selected decisions.
 
@@ -940,7 +940,7 @@ Checker prompt:
 - {PHASE_DIR}/*-SPRINT.md (Plans to verify)
 - {roadmap_path} (Roadmap)
 - {requirements_path} (Requirements)
-- {context_path} (USER DECISIONS from /rihal:discuss-phase)
+- {context_path} (USER DECISIONS from /rihal-discuss-phase)
 - {research_path} (Technical Research — includes Validation Architecture)
 </files_to_read>
 
@@ -1013,7 +1013,7 @@ If NONE of these evidence markers are present, the checker malfunctioned (return
 ```
 Display: "Sprint-checker returned without evidence of tool use — likely
          malfunctioned (cf. issue #440). Refusing to advance the plan
-         on unverified output. Re-run /rihal:plan or inspect the agent."
+         on unverified output. Re-run /rihal-plan or inspect the agent."
 Halt the workflow with a non-zero exit signal.
 ```
 
@@ -1036,7 +1036,7 @@ Display: `Revision iteration {N}/3 -- {blocker_count} blockers, {warning_count}
   **If `stall_reentry_count >= 2`:**
     Display: `Stall persists after 2 re-planning attempts. The following issues could not be resolved automatically:`
     List the remaining issues from the checker.
-    Suggest: "Consider resolving these issues manually or running `/rihal:debug` to investigate root causes."
+    Suggest: "Consider resolving these issues manually or running `/rihal-debug` to investigate root causes."
     Options: "Proceed anyway" | "Abandon"
     If "Proceed anyway": accept current plans and continue to step 13.
     If "Abandon": stop workflow.
@@ -1052,7 +1052,7 @@ Revision prompt:
 
 <files_to_read>
 - {PHASE_DIR}/*-SPRINT.md (Existing plans)
-- {context_path} (USER DECISIONS from /rihal:discuss-phase)
+- {context_path} (USER DECISIONS from /rihal-discuss-phase)
 </files_to_read>
 
 ${AGENT_SKILLS_PLANNER}
@@ -1245,14 +1245,14 @@ The `--no-transition` flag tells execute-phase to return status after verificati
 
   Auto-advance pipeline finished.
 
-  Next: /rihal:discuss-phase ${NEXT_PHASE} --auto ${Rihal_WS}
+  Next: /rihal-discuss-phase ${NEXT_PHASE} --auto ${Rihal_WS}
   ```
 - **GAPS FOUND / VERIFICATION FAILED** → Display result, stop chain:
   ```
   Auto-advance stopped: Execution needs review.
 
   Review the output above and continue manually:
-  /rihal:execute-phase ${PHASE} ${Rihal_WS}
+  /rihal-execute-phase ${PHASE} ${Rihal_WS}
   ```
 
 **If neither `--auto` nor config enabled:**
@@ -1285,15 +1285,15 @@ Verification: {Passed | Passed with override | Skipped}
 
 /clear then:
 
-/rihal:execute-phase {X} ${Rihal_WS}
+/rihal-execute-phase {X} ${Rihal_WS}
 
 ───────────────────────────────────────────────────────────────
 
 **Also available:**
 - cat .planning/phases/{phase-dir}/*-SPRINT.md — review plans
-- /rihal:sprint-plan {X} --research — re-research first
-- /rihal:review --phase {X} --all — peer review plans with external AIs
-- /rihal:sprint-plan {X} --reviews — replan incorporating review feedback
+- /rihal-sprint-plan {X} --research — re-research first
+- /rihal-review --phase {X} --all — peer review plans with external AIs
+- /rihal-sprint-plan {X} --reviews — replan incorporating review feedback
 
 ───────────────────────────────────────────────────────────────
 </offer_next>
@@ -1314,11 +1314,11 @@ stdio deadlocks with MCP servers — see Claude Code issue anthropics/claude-cod
    Remove-Item -Recurse -Force "$env:USERPROFILE\.claude\tasks\*" -ErrorAction SilentlyContinue
    ```
 4. **Reduce MCP server count:** Temporarily disable non-essential MCP servers in settings.json
-5. **Retry:** Restart Claude Code and run `/rihal:sprint-plan` again
+5. **Retry:** Restart Claude Code and run `/rihal-sprint-plan` again
 
 If freezes persist, try `--skip-research` to reduce the agent chain from 3 to 2 agents:
 ```
-/rihal:sprint-plan N --skip-research
+/rihal-sprint-plan N --skip-research
 ```
 </windows_troubleshooting>
 

package/rihal/workflows/plant-seed.md

@@ -1,6 +1,6 @@
 <purpose>
 Capture a forward-looking idea as a structured seed file with trigger conditions.
-Seeds auto-surface during /rihal:new-milestone when trigger conditions match the
+Seeds auto-surface during /rihal-new-milestone when trigger conditions match the
 new milestone's scope.
 
 Seeds beat deferred items because they:
@@ -117,7 +117,7 @@ scope: {$SCOPE}
 
 **Trigger:** {$TRIGGER}
 
-This seed should be presented during `/rihal:new-milestone` when the milestone
+This seed should be presented during `/rihal-new-milestone` when the milestone
 scope matches any of these conditions:
 - {trigger condition 1}
 - {trigger condition 2}
@@ -153,7 +153,7 @@ Trigger: {$TRIGGER}
 Scope: {$SCOPE}
 File: .planning/seeds/SEED-{PADDED}-{slug}.md
 
-This seed will surface automatically when you run /rihal:new-milestone
+This seed will surface automatically when you run /rihal-new-milestone
 and the milestone scope matches the trigger condition.
 ```
 </step>

package/rihal/workflows/pr-branch.md

@@ -114,7 +114,7 @@ Next steps:
   git push origin {PR_BRANCH}
   gh pr create --base {TARGET} --head {PR_BRANCH}
 
-Or use /rihal:ship to create the PR automatically.
+Or use /rihal-ship to create the PR automatically.
 ```
 </step>
 

package/rihal/workflows/prfaq.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:prfaq
+# Workflow: rihal-prfaq
 
 <purpose>
 Working Backwards PRFAQ challenge. Stress-test a product concept by writing the press release before building it. Produces a battle-hardened PRFAQ document + PRD distillate. Delegates to the rihal-prfaq skill for the full interview and generation protocol.

package/rihal/workflows/profile-user.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:profile-user
+# Workflow: rihal-profile-user
 
 <purpose>
 Classify developer on 4 dimensions: communication style, autonomy preference, domain depth, and iteration speed. Spawn a profiler subagent to ask questions and produce a USER-PROFILE.md artifact with YAML frontmatter + structured classification.
@@ -10,13 +10,13 @@ Classify developer on 4 dimensions: communication style, autonomy preference, do
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:profile-user <argument-here>
+/rihal-profile-user <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:profile-user
-/rihal:profile-user --json '{"communication":"Direct & dense","autonomy":"Autonomous","domain_depth":"Advanced","iteration_speed":"Fast"}'
+/rihal-profile-user
+/rihal-profile-user --json '{"communication":"Direct & dense","autonomy":"Autonomous","domain_depth":"Advanced","iteration_speed":"Fast"}'
 ```
 
 STOP — do not proceed.
@@ -145,7 +145,7 @@ Dimensions:
   • Domain Depth: {domain_depth}
   • Iteration Speed: {iteration_speed}
 
-This profile will personalize future /rihal:council and /rihal:execute responses.
+This profile will personalize future /rihal-council and /rihal-execute responses.
 ```
 
 ## Success Criteria

package/rihal/workflows/progress.md

@@ -1,9 +1,9 @@
-# Workflow: rihal:progress
+# Workflow: rihal-progress
 
 <purpose>
-**`/rihal:progress` is an alias of `/rihal:status --verbose`.**
+**`/rihal-progress` is an alias of `/rihal-status --verbose`.**
 
-Historically this was a separate workflow with overlapping data and a heavier render. They both read the same source of truth (`rihal-tools progress init`), so we collapsed them: `/rihal:status` is the canonical renderer with built-in slim/verbose modes, and `/rihal:progress` is a thin alias that always runs in verbose mode.
+Historically this was a separate workflow with overlapping data and a heavier render. They both read the same source of truth (`rihal-tools progress init`), so we collapsed them: `/rihal-status` is the canonical renderer with built-in slim/verbose modes, and `/rihal-progress` is a thin alias that always runs in verbose mode.
 
 Use whichever name you prefer — they produce the same output.
 </purpose>
@@ -14,12 +14,12 @@ Use whichever name you prefer — they produce the same output.
 
 <process>
 
-## Step 1 — Delegate to /rihal:status in verbose mode
+## Step 1 — Delegate to /rihal-status in verbose mode
 
 Execute the workflow defined in `.rihal/workflows/status.md` end-to-end, with one override:
 
 - Always render in **verbose mode** (full Steps 2–6 output: banner + phases + insights + decisions + blockers + Next Up route tree).
-- Treat `$ARGUMENTS` exactly as `/rihal:status --verbose $ARGUMENTS` would.
+- Treat `$ARGUMENTS` exactly as `/rihal-status --verbose $ARGUMENTS` would.
 
 Do not parse ROADMAP.md, walk SUMMARY.md files, or grep state.json directly. If the underlying CLI reports a drift insight, surface it — do not silently compensate.
 
@@ -28,7 +28,7 @@ Do not parse ROADMAP.md, walk SUMMARY.md files, or grep state.json directly. If
 After the verbose status output, append a single grey line:
 
 ```
-(/rihal:progress is an alias of /rihal:status --verbose — same data, same source.)
+(/rihal-progress is an alias of /rihal-status --verbose — same data, same source.)
 ```
 
 Skip this footer if `$ARGUMENTS` already contains `--no-alias-hint`.

package/rihal/workflows/quick.md

@@ -2,9 +2,9 @@
 Execute small ad-hoc tasks with guarantees. Two real modes the workflow auto-detects:
 
 - **Trivial inline** — single ≤ 3-file change, finishes in 1-2 minutes, no planning needed.
-- **Bulk-task auto-route** — when the input contains many tasks (numbered list with 5+ items, or several distinct bugs/asks), automatically route to /rihal:add-phase with the task list pre-extracted, so the user doesn't have to copy-paste their list a second time.
+- **Bulk-task auto-route** — when the input contains many tasks (numbered list with 5+ items, or several distinct bugs/asks), automatically route to /rihal-add-phase with the task list pre-extracted, so the user doesn't have to copy-paste their list a second time.
 
-Closes the gap where /rihal:quick used to refuse + show a 4-option menu when given many tasks (forcing the user to re-enter the same list into another command).
+Closes the gap where /rihal-quick used to refuse + show a 4-option menu when given many tasks (forcing the user to re-enter the same list into another command).
 </purpose>
 
 <required_reading>
@@ -35,7 +35,7 @@ Match if `$TASK` contains ANY of:
 - > 60 lines total
 - Contains the phrase "buht zada bugs" / "many bugs" / "list of bugs" / "bug list" / "saare bugs" / "all these bugs"
 
-If matched, **AUTO-ROUTE to `/rihal:add-phase`** without asking. Do not refuse, do not show a menu, do not ask the user to repaste.
+If matched, **AUTO-ROUTE to `/rihal-add-phase`** without asking. Do not refuse, do not show a menu, do not ask the user to repaste.
 
 Procedure:
 
@@ -50,16 +50,16 @@ Procedure:
 3. Print the auto-route banner:
    ```
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-    /rihal:quick — AUTO-ROUTING
+    /rihal-quick — AUTO-ROUTING
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
    Detected: {N} tasks in input — too many for inline.
    Active milestone: {ACTIVE_MILESTONE or "none"}
-   Routing to: /rihal:add-phase {phase-slug}
+   Routing to: /rihal-add-phase {phase-slug}
    Reason: bulk-detection threshold ({matched signal}) — auto-route avoids
            refusing and forcing you to re-paste the list.
    ```
-4. Dispatch `/rihal:add-phase {phase-slug}` and pass `$TASK` verbatim. The add-phase workflow uses the pre-extracted task list as the phase task list — no user re-entry needed.
+4. Dispatch `/rihal-add-phase {phase-slug}` and pass `$TASK` verbatim. The add-phase workflow uses the pre-extracted task list as the phase task list — no user re-entry needed.
 5. STOP this workflow — add-phase takes over from here.
 
 If the bulk detection does NOT match, continue to scope_check.
@@ -76,8 +76,8 @@ If the task seems non-trivial but did NOT trigger bulk_detection above (e.g., a
 
 ```
 This is a single task but looks non-trivial. Recommended:
-  /rihal:add-phase — for multi-file refactor / new feature / structural change
-  /rihal:plan      — when scope is clear, jump straight to a SPRINT.md plan
+  /rihal-add-phase — for multi-file refactor / new feature / structural change
+  /rihal-plan      — when scope is clear, jump straight to a SPRINT.md plan
 
 Or paste --force-inline at the end of your input to override and try inline anyway.
 ```
@@ -136,7 +136,7 @@ Common blocker types:
 
 **Stop the loop only when:**
 - All tasks in the list are processed (done / skipped / blocked)
-- A task touches `> 5` files (escalate the rest of the list to /rihal:add-phase)
+- A task touches `> 5` files (escalate the rest of the list to /rihal-add-phase)
 - The user types stop / cancel / pause
 
 At the end of the loop, summarise:
@@ -191,12 +191,12 @@ No next-step suggestions. No workflow routing. Just done.
 - NEVER create SPRINT.md or SUMMARY.md files directly (add-phase will, when bulk-routed)
 - NEVER run research or plan-checking inline
 - If bulk_detection matches, auto-route silently — do not stop and ask
-- If a single non-bulk task exceeds 3 file edits and the user did NOT pass `--force-inline`, redirect to /rihal:add-phase or /rihal:plan
+- If a single non-bulk task exceeds 3 file edits and the user did NOT pass `--force-inline`, redirect to /rihal-add-phase or /rihal-plan
 </guardrails>
 
 <success_criteria>
-- [ ] Bulk inputs are auto-routed to /rihal:add-phase without forcing the user to re-paste
+- [ ] Bulk inputs are auto-routed to /rihal-add-phase without forcing the user to re-paste
 - [ ] Trivial inputs are completed inline (single context, ≤3 files, conventional commit)
 - [ ] STATE.md updated if it exists
-- [ ] No self-referential redirects (the old quick.md redirected to /rihal:quick — that infinite loop is closed)
+- [ ] No self-referential redirects (the old quick.md redirected to /rihal-quick — that infinite loop is closed)
 </success_criteria>