@hanzlaa/rcode 3.3.0 → 3.3.2

package/rihal/references/continuation-format.md

@@ -44,7 +44,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
 
-`/rihal:execute-phase 2`
+`/rihal-execute-phase 2`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -52,7 +52,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 **Also available:**
 - Review plan before executing
-- `/rihal:list-phase-assumptions 2` — check assumptions
+- `/rihal-list-phase-assumptions 2` — check assumptions
 
 ---
 ```
@@ -69,7 +69,7 @@ Add note that this is the last plan and what comes after:
 **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
 <sub>Final plan in Phase 2</sub>
 
-`/rihal:execute-phase 2`
+`/rihal-execute-phase 2`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -91,15 +91,15 @@ Add note that this is the last plan and what comes after:
 
 **Phase 2: Authentication** — JWT login flow with refresh tokens
 
-`/rihal:plan-phase 2`
+`/rihal-plan-phase 2`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- `/rihal:discuss-phase 2` — gather context first
-- `/rihal:research-phase 2` — investigate unknowns
+- `/rihal-discuss-phase 2` — gather context first
+- `/rihal-research-phase 2` — investigate unknowns
 - Review roadmap
 
 ---
@@ -120,15 +120,15 @@ Show completion status before next action:
 
 **Phase 3: Core Features** — User dashboard, settings, and data export
 
-`/rihal:plan-phase 3`
+`/rihal-plan-phase 3`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- `/rihal:discuss-phase 3` — gather context first
-- `/rihal:research-phase 3` — investigate unknowns
+- `/rihal-discuss-phase 3` — gather context first
+- `/rihal-research-phase 3` — investigate unknowns
 - Review what Phase 2 built
 
 ---
@@ -145,11 +145,11 @@ When there's no clear primary action:
 
 **Phase 3: Core Features** — User dashboard, settings, and data export
 
-**To plan directly:** `/rihal:plan-phase 3`
+**To plan directly:** `/rihal-plan-phase 3`
 
-**To discuss context first:** `/rihal:discuss-phase 3`
+**To discuss context first:** `/rihal-discuss-phase 3`
 
-**To research unknowns:** `/rihal:research-phase 3`
+**To research unknowns:** `/rihal-research-phase 3`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -169,7 +169,7 @@ All 4 phases shipped
 
 **Start v1.1** — questioning → research → requirements → roadmap
 
-`/rihal:new-milestone`
+`/rihal-new-milestone`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -214,7 +214,7 @@ Extract: `**02-03: Refresh Token Rotation** — Add /api/auth/refresh with slidi
 ## To Continue
 
 Run `/clear`, then paste:
-/rihal:execute-phase 2
+/rihal-execute-phase 2
 ```
 
 User has no idea what 02-03 is about.
@@ -222,7 +222,7 @@ User has no idea what 02-03 is about.
 ### Don't: Missing /clear explanation
 
 ```
-`/rihal:plan-phase 3`
+`/rihal-plan-phase 3`
 
 Run /clear first.
 ```
@@ -242,7 +242,7 @@ Sounds like an afterthought. Use "Also available:" instead.
 
 ```
 ```
-/rihal:plan-phase 3
+/rihal-plan-phase 3
 ```
 ```
 

package/rihal/references/dispatch-banner.md

@@ -130,7 +130,7 @@ Then print a fresh DISPATCH banner.
 
 ## Concurrency: parallel dispatches
 
-If a workflow spawns multiple agents in parallel (e.g. `/rihal:council` summons 4 specialists), print ONE combined banner:
+If a workflow spawns multiple agents in parallel (e.g. `/rihal-council` summons 4 specialists), print ONE combined banner:
 
 ```
 ╭─────────────────────────────────────────────────────────╮

package/rihal/references/execution-protocol.md

@@ -79,14 +79,14 @@ Type: {human-verify | decision}
 {For human-verify:}
 Please verify: {what to check}
 URL/path: {where to look}
-Resume with: /rihal:execute {plan} --continue
+Resume with: /rihal-execute {plan} --continue
 
 {For decision:}
 Problem: {what the plan assumed that isn't true}
 Option A: {approach} — {trade-off}
 Option B: {approach} — {trade-off}
 Recommendation: {which one and why}
-Resume with: /rihal:execute {plan} --continue --option=A
+Resume with: /rihal-execute {plan} --continue --option=A
 ---
 ```
 

package/rihal/references/gates.md

@@ -18,7 +18,7 @@ Defines 4 gate types used in rihal workflows to control execution flow, validate
 **Example:** Phase execution gate
 ```
 Gate: Check phase.md exists and has required sections
-Block: "Phase {N} has no SPRINT.md. Create with /rihal:help"
+Block: "Phase {N} has no SPRINT.md. Create with /rihal-help"
 Warn: "Phase overdue by {days}. Review roadmap?"
 ```
 
@@ -77,14 +77,14 @@ Ask: "Pattern A is faster but less flexible. Pattern B is extensible but slower.
 - Exit cleanly without recovery attempt
 - Suggest manual recovery path
 
-**Recovery:** Manual repair via `/rihal:health` or `/rihal:forensics`
+**Recovery:** Manual repair via `/rihal-health` or `/rihal-forensics`
 
 **Example:** Corrupted state gate
 ```
 Gate: Validate state.json integrity
 Fail: "state.json corrupted (invalid JSON at line 42).
        Aborting to prevent further damage.
-       Recovery: /rihal:health --repair"
+       Recovery: /rihal-health --repair"
 ```
 
 ---

package/rihal/references/git-integration.md

@@ -132,7 +132,7 @@ git commit -m "feat(...): description"
 ### Worktree-Isolation Strategy
 ```bash
 # Workflow commands
-/rihal:do --worktree phase/2-auth
+/rihal-do --worktree phase/2-auth
 # Internally:
 git worktree add .claude/worktrees/phase-2-auth phase/2-auth
 cd .claude/worktrees/phase-2-auth

package/rihal/references/output-format.md

@@ -29,7 +29,7 @@ Use for major workflow transitions.
 
 ---
 
-## Routing Output (for /rihal:do, /rihal:next, /rihal:progress)
+## Routing Output (for /rihal-do, /rihal-next, /rihal-progress)
 
 Use this when a router command dispatches to another command:
 
@@ -42,7 +42,7 @@ Input: {user's question or intent}
 Scope: {one-line summary of detected scope}
 {optional: Blocker: {any blockers detected}}
 
-Routing to: /rihal:{target-command}
+Routing to: /rihal-{target-command}
 Reason: {one-line why this command fits}
 
 Handing off to the workflow now.
@@ -253,8 +253,8 @@ Always at end of major completions.
 ───────────────────────────────────────────────────────────────
 
 **Also available:**
-- `/rihal:alternative-1` — description
-- `/rihal:alternative-2` — description
+- `/rihal-alternative-1` — description
+- `/rihal-alternative-2` — description
 
 ───────────────────────────────────────────────────────────────
 ```

package/rihal/references/output-realism.md

@@ -43,7 +43,7 @@ Keep the whole response under ~300 words. Tone: colleague-honest, not apologetic
 - **rihal-planner:** If `## Scope` from orchestrator implies > 8 tasks of real work, return a PLANS.md with *multiple* SPRINT.md files (waves) instead of one overloaded plan.
 - **rihal-executor:** If a SPRINT.md would require > 1500 lines of new/changed code to execute, stop at Step 2 (load plan) and return a "plan too large — suggest wave split" checkpoint instead of executing.
 - **rihal-roadmapper:** Phase size cap: one phase = one coherent batch that a solo developer + AI can reasonably ship in 1-3 focused sessions.
-- **/rihal:autonomous** and **/rihal:do --auto:** Even in auto mode, pause at the first batch boundary that exceeds output budget. "Don't stop until done" authorizes local commits, not output-budget violations.
+- **/rihal-autonomous** and **/rihal-do --auto:** Even in auto mode, pause at the first batch boundary that exceeds output budget. "Don't stop until done" authorizes local commits, not output-budget violations.
 
 ## The Core Philosophy
 

package/rihal/references/revision-loop.md

@@ -1,6 +1,6 @@
 # Plan Revision Loop
 
-When `workflow.plan_checker` is enabled (`/rihal:settings`), `/rihal:plan`
+When `workflow.plan_checker` is enabled (`/rihal-settings`), `/rihal-plan`
 runs the rihal-plan-checker after the planner. Findings drive a bounded
 revision loop:
 

package/rihal/references/state-schema.md

@@ -34,7 +34,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `version`
 **Type:** string  
 **Example:** `"1"`  
-**Written by:** `/rihal:install` (initialization)  
+**Written by:** `/rihal-install` (initialization)  
 **Purpose:** Schema version for compatibility checks. Change if fields added/removed.
 
 ---
@@ -42,7 +42,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `project`
 **Type:** string  
 **Example:** `"Rihal v2"`  
-**Written by:** `/rihal:install` (reads from config.yaml)  
+**Written by:** `/rihal-install` (reads from config.yaml)  
 **Purpose:** Project name for context and reports.
 
 ---
@@ -50,7 +50,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `created`
 **Type:** ISO date string  
 **Example:** `"2026-04-01T10:30:00Z"`  
-**Written by:** `/rihal:install` (first session)  
+**Written by:** `/rihal-install` (first session)  
 **Purpose:** Timestamp of project creation, never changes.
 
 ---
@@ -66,7 +66,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `current_phase`
 **Type:** string or null  
 **Example:** `"Phase 2: Authentication"` or `null`  
-**Written by:** `/rihal:do`, `/rihal:next`, `/rihal:resume-work`  
+**Written by:** `/rihal-do`, `/rihal-next`, `/rihal-resume-work`  
 **Purpose:** Name of active phase, null if no phase active.
 
 ---
@@ -74,7 +74,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `current_plan`
 **Type:** number  
 **Example:** `2`  
-**Written by:** `/rihal:do --execute` (incremented after each phase completion)  
+**Written by:** `/rihal-do --execute` (incremented after each phase completion)  
 **Purpose:** Counter for plan versions. Increments 1→2→3 as phases complete.
 
 ---
@@ -120,7 +120,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:do --execute`, `/rihal:next`, sprint/story state tools  
+**Written by:** `/rihal-do --execute`, `/rihal-next`, sprint/story state tools  
 **Purpose:** Tracks phases with nested sprints and stories.
 
 **Sprint fields:**
@@ -176,7 +176,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:execute` (after each plan completes)  
+**Written by:** `/rihal-execute` (after each plan completes)  
 **Purpose:** Log of each plan execution. The `plan` field is the plan ID string (e.g., "01.02"), not a number.
 
 ---
@@ -194,7 +194,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:council`, `/rihal:discuss`  
+**Written by:** `/rihal-council`, `/rihal-discuss`  
 **Purpose:** Records architectural/strategic decisions for history.
 
 ---
@@ -213,7 +213,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:do`, `/rihal:health`  
+**Written by:** `/rihal-do`, `/rihal-health`  
 **Purpose:** Tracks blockers, when identified, which phase, and resolution time.
 
 ---
@@ -231,7 +231,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:council`  
+**Written by:** `/rihal-council`  
 **Purpose:** History of council deliberations, panelists, output artifacts.
 
 ---
@@ -249,7 +249,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:chain`  
+**Written by:** `/rihal-chain`  
 **Purpose:** History of multi-agent chains, participants, work artifacts.
 
 ---
@@ -258,7 +258,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 **Type:** ISO date string  
 **Example:** `"2026-04-12T15:45:30Z"`  
 **Written by:** Every subcommand that runs (updates at session end)  
-**Purpose:** Enables `/rihal:resume-work` to find context from last session.
+**Purpose:** Enables `/rihal-resume-work` to find context from last session.
 
 ---
 
@@ -283,7 +283,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:workstream --create`, `/rihal:do --execute`  
+**Written by:** `/rihal-workstream --create`, `/rihal-do --execute`  
 **Purpose:** Tracks parallel workstreams, which phases belong to each.
 
 ---
@@ -291,7 +291,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `active_workstream`
 **Type:** string or null  
 **Example:** `"Frontend"` or `null`  
-**Written by:** `/rihal:workstream --activate`, `/rihal:do`  
+**Written by:** `/rihal-workstream --activate`, `/rihal-do`  
 **Purpose:** Currently active workstream; null if no workstream focus.
 
 ---
@@ -299,7 +299,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `model_profile`
 **Type:** string  
 **Example:** `"balanced"` (options: `quality`, `balanced`, `budget`, `inherit`)  
-**Written by:** `/rihal:set-profile`  
+**Written by:** `/rihal-set-profile`  
 **Purpose:** Model selection for council agents. Affects token spend and quality.
 
 ---

package/rihal/references/ui-brand.md

@@ -1,6 +1,6 @@
 # UI/Brand Questions
 
-When exploring the UI design phase (/rihal:ui-phase), ask structured questions across these eight dimensions: **color palette**, **typography**, **voice/tone**, **accessibility**, **component inventory**, **responsive behavior**, **interaction patterns**, and **visual hierarchy**. These questions build the design contract.
+When exploring the UI design phase (/rihal-ui-phase), ask structured questions across these eight dimensions: **color palette**, **typography**, **voice/tone**, **accessibility**, **component inventory**, **responsive behavior**, **interaction patterns**, and **visual hierarchy**. These questions build the design contract.
 
 ---
 

package/rihal/references/verb-dictionary.md

@@ -76,19 +76,19 @@ These are matched alongside §Create / §Add / §Plan verbs to determine the dis
 
 | Scope noun | Aliases (English + Urdu) | Maps to (workflow) |
 |---|---|---|
-| milestone | `milestone`, `milestones`, `release`, `version`, `cycle` | `/rihal:new-milestone` |
-| phase | `phase`, `phases` (singular intent — "add a phase") | `/rihal:add-phase` |
-| story | `story`, `stories`, `user story`, `kahani` | `/rihal:create-story` |
-| epic | `epic`, `epics`, `epics and stories` | `/rihal:create-epics-and-stories` |
-| sprint | `sprint`, `iteration` | `/rihal:sprint-planning` |
-| PRD | `PRD`, `requirements doc`, `product requirements` | `/rihal:create-prd` |
-| roadmap | `roadmap`, `plan` (top-level) | `/rihal:create-milestone` |
-| council | `council`, `majlis`, `panel`, `mashwara`, `salah` | `/rihal:council` |
-| plan (verb form — "plan phase N") | `plan` | `/rihal:plan` |
-| story (impl) | `dev story`, `implement story`, `build story` | `/rihal:dev-story` |
-| brainstorm | `brainstorm`, `ideas`, `sochain`, `sochna` | `/rihal:brainstorm` |
-| review (code) | `code review`, `karpathy`, `check my diff` | `/rihal:code-review [--karpathy]` |
-| debug | `debug`, `fix`, `bug`, `error`, `crash`, `kharab`, `theek` | `/rihal:debug` |
+| milestone | `milestone`, `milestones`, `release`, `version`, `cycle` | `/rihal-new-milestone` |
+| phase | `phase`, `phases` (singular intent — "add a phase") | `/rihal-add-phase` |
+| story | `story`, `stories`, `user story`, `kahani` | `/rihal-create-story` |
+| epic | `epic`, `epics`, `epics and stories` | `/rihal-create-epics-and-stories` |
+| sprint | `sprint`, `iteration` | `/rihal-sprint-planning` |
+| PRD | `PRD`, `requirements doc`, `product requirements` | `/rihal-create-prd` |
+| roadmap | `roadmap`, `plan` (top-level) | `/rihal-create-milestone` |
+| council | `council`, `majlis`, `panel`, `mashwara`, `salah` | `/rihal-council` |
+| plan (verb form — "plan phase N") | `plan` | `/rihal-plan` |
+| story (impl) | `dev story`, `implement story`, `build story` | `/rihal-dev-story` |
+| brainstorm | `brainstorm`, `ideas`, `sochain`, `sochna` | `/rihal-brainstorm` |
+| review (code) | `code review`, `karpathy`, `check my diff` | `/rihal-code-review [--karpathy]` |
+| debug | `debug`, `fix`, `bug`, `error`, `crash`, `kharab`, `theek` | `/rihal-debug` |
 
 ---
 
@@ -106,8 +106,8 @@ table above, dispatch directly to the mapped workflow without an
 ambiguity prompt.
 
 Example: "milestone bnao" → §Create matches "bnao", scope matches
-"milestone" → /rihal:new-milestone (with state-aware redirect to
-/rihal:add-phase if a milestone is already active).
+"milestone" → /rihal-new-milestone (with state-aware redirect to
+/rihal-add-phase if a milestone is already active).
 ```
 
 **From an agent file (e.g. `rihal-codebase-mapper.md`) when interpreting the orchestrator prompt:**

package/rihal/references/workstream-flag.md

@@ -13,9 +13,9 @@ Use the standard planning pipeline (`.planning/phases/`) for:
 
 **Example:**
 ```
-/rihal:plan Build authentication system
-/rihal:plan Add user profile pages (depends on auth from Phase 1)
-/rihal:plan Write deployment guide (depends on both phases complete)
+/rihal-plan Build authentication system
+/rihal-plan Add user profile pages (depends on auth from Phase 1)
+/rihal-plan Write deployment guide (depends on both phases complete)
 ```
 
 These run sequentially, each depending on the previous phase's completion.
@@ -34,15 +34,15 @@ Use workspaces (`--workspace` flag) for:
 **Example:**
 ```
 # Main workspace (Q2 roadmap)
-/rihal:plan Build search feature
+/rihal-plan Build search feature
 
 # Parallel workspace (critical bug)
-/rihal:new-workspace Critical Hotfix
-/rihal:plan Fix data corruption --workspace=Critical Hotfix
+/rihal-new-workspace Critical Hotfix
+/rihal-plan Fix data corruption --workspace=Critical Hotfix
 
 # Both run independently
 # Query progress:
-/rihal:list-workspaces
+/rihal-list-workspaces
 ```
 
 ## Decision Matrix
@@ -78,29 +78,29 @@ Use workspaces (`--workspace` flag) for:
 
 ```bash
 # View current phase
-/rihal:status
+/rihal-status
 
 # Execute next phase
-/rihal:execute <phase>
+/rihal-execute <phase>
 
 # Switch to different task within same milestone
-/rihal:quick <small task>
+/rihal-quick <small task>
 ```
 
 ### Workspaces
 
 ```bash
 # List all workspaces
-/rihal:list-workspaces
+/rihal-list-workspaces
 
 # Work within a workspace
-/rihal:plan <task> --workspace=Hotfix
+/rihal-plan <task> --workspace=Hotfix
 
 # Switch to another workspace's context
-/rihal:workspace <name>
+/rihal-workspace <name>
 
 # Return to main planning
-/rihal:workspace main
+/rihal-workspace main
 ```
 
 ## Merging Workspaces Back
@@ -109,7 +109,7 @@ If you started a workspace but it should merge back into main planning:
 
 1. Complete the work in the workspace
 2. Create a phase in main planning that incorporates the workspace's findings
-3. Archive the workspace: `/rihal:remove-workspace <name> --archive`
+3. Archive the workspace: `/rihal-remove-workspace <name> --archive`
 4. Continue in main planning with unified context
 
 ## Common Patterns
@@ -118,27 +118,27 @@ If you started a workspace but it should merge back into main planning:
 
 ```bash
 # Main work (Q2 roadmap)
-/rihal:plan Implement real-time notifications
+/rihal-plan Implement real-time notifications
 
 # Critical bug emerges
-/rihal:new-workspace Critical
-/rihal:plan Fix payment processing --workspace=Critical
+/rihal-new-workspace Critical
+/rihal-plan Fix payment processing --workspace=Critical
 
 # Two parallel tracks
-/rihal:list-workspaces
+/rihal-list-workspaces
 
 # When bug is fixed
-/rihal:complete-workspace Critical
+/rihal-complete-workspace Critical
 # Resume main work
-/rihal:execute <Q2 phase>
+/rihal-execute <Q2 phase>
 ```
 
 ### Pattern: Research + implementation
 
 ```bash
 # Sequential phases (both parts of same feature)
-/rihal:plan Research WebSocket libraries and trade-offs
-/rihal:plan Implement chosen library with tests
+/rihal-plan Research WebSocket libraries and trade-offs
+/rihal-plan Implement chosen library with tests
 # Phase 2 reads Phase 1 findings
 ```
 
@@ -146,16 +146,16 @@ If you started a workspace but it should merge back into main planning:
 
 ```bash
 # Keep experiments separate
-/rihal:new-workspace Experiment: Dark Mode
-/rihal:plan Build dark mode UI --workspace=Experiment
-/rihal:plan Test across 10 browsers --workspace=Experiment
+/rihal-new-workspace Experiment: Dark Mode
+/rihal-plan Build dark mode UI --workspace=Experiment
+/rihal-plan Test across 10 browsers --workspace=Experiment
 
 # Main work continues unaffected
-/rihal:plan Improve search relevance
+/rihal-plan Improve search relevance
 
 # If experiment succeeds, merge into main
 # If it fails, just archive and delete
-/rihal:remove-workspace --archive Experiment
+/rihal-remove-workspace --archive Experiment
 ```
 
 ## Summary

package/rihal/skills/_shared/no-autonomous-bypass.md

@@ -13,7 +13,7 @@ Phrases like *"just write it autonomously"*, *"create the full thing ready to ex
 There are exactly two ways to legitimately run a skill without halting at menus:
 
 1. **Project-wide:** `.rihal/config.yaml` → `mode: yolo`. The config loader flags `yoloMode=true` in the runtime context; step files check this flag and may auto-advance.
-2. **Per-invocation:** `/rihal:do --auto <question>` on the router. The router sets `autoMode=true` and passes it to the dispatched skill.
+2. **Per-invocation:** `/rihal-do --auto <question>` on the router. The router sets `autoMode=true` and passes it to the dispatched skill.
 
 If **neither** flag is set, halt is mandatory regardless of what the user's prompt text says.
 
@@ -34,4 +34,4 @@ That response invents a mode that does not exist and violates the halt invariant
 
 ## Correct Response
 
-> ✅ Agent: *"I hear you want the PRD written end-to-end. The halt rule applies unless you set `mode: yolo` in `.rihal/config.yaml` or re-invoke via `/rihal:do --auto`. Here is the step-01 menu — pick Continue and I will drive each step concisely."*
+> ✅ Agent: *"I hear you want the PRD written end-to-end. The halt rule applies unless you set `mode: yolo` in `.rihal/config.yaml` or re-invoke via `/rihal-do --auto`. Here is the step-01 menu — pick Continue and I will drive each step concisely."*

package/rihal/skills/_shared/research-citation-rule.md

@@ -28,7 +28,7 @@ This pattern is forbidden. A citation block without `WebFetch` evidence is a lie
 
 ## If the User Is Running Autonomously
 
-`mode: yolo` and `/rihal:do --auto` bypass halt-at-menu, but they do **not** bypass this rule. A fully-autonomous run still has to fetch every cited URL before writing the claim.
+`mode: yolo` and `/rihal-do --auto` bypass halt-at-menu, but they do **not** bypass this rule. A fully-autonomous run still has to fetch every cited URL before writing the claim.
 
 ## Checklist Before Writing a Citation
 

package/rihal/skills/_shared/state-sync-rule.md

@@ -1,6 +1,6 @@
 # State Sync Rule
 
-Referenced by skills that write `ROADMAP.md`, `epics.md`, or sprint artifacts. These artifacts are not authoritative on their own — downstream workflows (`/rihal:status`, `/rihal:progress`, `/rihal:execute`) read `.rihal/state.json`. If you write a planning artifact and skip state sync, the project ends up with two divergent pictures.
+Referenced by skills that write `ROADMAP.md`, `epics.md`, or sprint artifacts. These artifacts are not authoritative on their own — downstream workflows (`/rihal-status`, `/rihal-progress`, `/rihal-execute`) read `.rihal/state.json`. If you write a planning artifact and skip state sync, the project ends up with two divergent pictures.
 
 ## The Rule
 
@@ -29,15 +29,15 @@ If `rihal-tools.cjs` does not yet expose the needed subcommand, fall back to `st
 ## Verification After Sync
 
 - `node .rihal/bin/rihal-tools.cjs state read` returns a phase count that matches the phase table in `ROADMAP.md`.
-- `/rihal:status` and `/rihal:progress`, run back-to-back, agree on the current milestone name and phase count.
+- `/rihal-status` and `/rihal-progress`, run back-to-back, agree on the current milestone name and phase count.
 
 ## Why This Matters
 
 Observed failure (rihal-code, social-poster-x install, Apr 2026):
 
-- User ran `/rihal:create-epics-and-stories`.
+- User ran `/rihal-create-epics-and-stories`.
 - `ROADMAP.md` gained 10 phases; `epics.md` gained 62 stories.
 - `.rihal/state.json` remained at the initial bootstrap with 1 phase.
-- `/rihal:status` showed 1 phase; `/rihal:progress` showed 10.
+- `/rihal-status` showed 1 phase; `/rihal-progress` showed 10.
 
 That divergence is what this rule exists to prevent.

package/rihal/skills/actions/1-analysis/rihal-prfaq/SKILL.md

@@ -124,7 +124,7 @@ When the user gets stuck, offer concrete suggestions based on what they've share
 **Expected:** Gauntlet mode questioning → press release → customer FAQ → internal FAQ → verdict + distillate. Saved to planning_artifacts/.
 
 ### Headless Mode
-**Input:** `/rihal:prfaq --headless --customer "{persona}" --problem "{problem}" --stakes "{why}" --solution "{concept}"`
+**Input:** `/rihal-prfaq --headless --customer "{persona}" --problem "{problem}" --stakes "{why}" --solution "{concept}"`
 **Expected:** First-draft PRFAQ generated autonomously via artifact-analyzer + web-researcher subagents.
 
 ### Negative Test

package/rihal/skills/actions/2-plan/rihal-create-epics-and-stories/workflow.md

@@ -36,7 +36,7 @@ This uses **step-file architecture** for disciplined execution:
 - 🎯 **ALWAYS** follow the exact instructions in the step file
 - ⏸️ **ALWAYS** halt at menus and wait for user input
 - 📋 **NEVER** create mental todo lists from future steps
-- 🚷 **NEVER** invent an "autonomous mode", "research mode", or any self-declared bypass. The only sanctioned bypass paths are `.rihal/config.yaml` → `mode: yolo` or `/rihal:do --auto`. See `../../_shared/no-autonomous-bypass.md` for the full rule and correct response pattern.
+- 🚷 **NEVER** invent an "autonomous mode", "research mode", or any self-declared bypass. The only sanctioned bypass paths are `.rihal/config.yaml` → `mode: yolo` or `/rihal-do --auto`. See `../../_shared/no-autonomous-bypass.md` for the full rule and correct response pattern.
 
 ---
 

package/rihal/skills/actions/2-plan/rihal-create-milestone/SKILL.md

@@ -48,7 +48,7 @@ Follow the instructions in ./workflow.md.
 
 ### Edge Case: No PRD Exists
 **Input:** "Create milestones for social-poster-x" (no prd.md)
-**Expected behavior:** DO NOT invent milestones. Respond: "I need an approved PRD first. Run `/rihal:create-prd` or point me at an existing brief."
+**Expected behavior:** DO NOT invent milestones. Respond: "I need an approved PRD first. Run `/rihal-create-prd` or point me at an existing brief."
 
 ### Edge Case: PRD Marked Draft
 **Input:** PRD exists but frontmatter shows `status: draft`
@@ -56,4 +56,4 @@ Follow the instructions in ./workflow.md.
 
 ### Negative Example: Request to Bypass the Interview
 **Input:** "just generate the full roadmap autonomously"
-**Expected behavior:** DO NOT invent an "autonomous mode". Point the user to the two sanctioned bypass paths (`.rihal/config.yaml` → `mode: yolo` or `/rihal:do --auto`) and present the step-01 menu. See `../../_shared/no-autonomous-bypass.md`.
+**Expected behavior:** DO NOT invent an "autonomous mode". Point the user to the two sanctioned bypass paths (`.rihal/config.yaml` → `mode: yolo` or `/rihal-do --auto`) and present the step-01 menu. See `../../_shared/no-autonomous-bypass.md`.

package/rihal/skills/actions/2-plan/rihal-create-milestone/steps/step-06-phase-stubs.md

@@ -4,12 +4,12 @@
 
 ## STEP GOAL
 
-For each milestone, list the phases it contains as **stubs** (number + name + one-line goal). No plan detail — phases get full plans via `/rihal:plan` later.
+For each milestone, list the phases it contains as **stubs** (number + name + one-line goal). No plan detail — phases get full plans via `/rihal-plan` later.
 
 ## MANDATORY RULES
 
 - 🛑 Phase numbers follow Rihal's NN convention (01, 02, ..., 99, then 999.x for parking lot).
-- 🛑 Do NOT generate plan content here. That's `/rihal:plan-phase`.
+- 🛑 Do NOT generate plan content here. That's `/rihal-plan-phase`.
 - 🛑 Each phase has one-sentence goal, max.
 - ⏸️ HALT at menu.